UKVoIPTalk.com

Scope wrote:[color=blue]
> I would strongly recommend anything that runs as a server (ftp, web,
> etc) to have a static IP address. It stops you having to look for the ip
> every time new ip addresses are issued (and they get a different IP
> address), and also would stop any port forwarding being messed up
> whenever they change.[/color]

DHCP and static IP addressing are not exclusive.

In article <ejcdki$2pc8$2@custnews.inweb.co.uk>,
Paul Cupis <paul@cupis.co.uk> writes:[color=blue]
> Scope wrote:[color=green]
>> I would strongly recommend anything that runs as a server (ftp, web,
>> etc) to have a static IP address. It stops you having to look for the ip
>> every time new ip addresses are issued (and they get a different IP
>> address), and also would stop any port forwarding being messed up
>> whenever they change.[/color]
>
> DHCP and static IP addressing are not exclusive.[/color]

Yep -- my SPA3000's are DHCP'ed with static IP addresses.

An interesting observation...
If the DHCP server isn't up when the SPA3000 powers up (which
happens after a power outage as the DHCP server takes longer
to boot), the SPA3000 seems to just continue using the same IP
address it had prior to power down, until it gets a DHCP lease.

--
Andrew Gabriel