D
David D.
I have been researching postings about IP conflicts using DHCP. Although
there are tons of such postings, most have to do with mixing DHCP with
static IPs, or with split-second timing problems, or with clearing IP
conflicts after they have occurred.
I suspect that my IP conflicts are related to leases expiring and IP
addresses being reassigned while the original lessee is hibernating.
This is a home network with a cable-modem and a router that serves as my
DHCP server. There are no static IP addresses in the DHCP IP pool range.
Computers in my house are typically hibernated rather than shut down, so
that work in progress can be left open, and so that the computers power on
faster.
I have had intermittent IP conflicts with my old, wired Linksys router. I
eliminated that problem by setting the IP lease length to three years.
My new router is a wireless Netgear, with both wired ports and wireless
connections. This may complicate things a little for two reasons: (1) the
Netgear router does not have a setting to allow one to change the IP lease
length, and the lease length is pretty short, and (2) the same computer
might have one wireless connection and one wired connection. I prefer to
keep wireless disabled for increased security and higher bandwidth, but it
is often convenient to use wireless.
However, the problem still occurred with the old, wired-only router.
My network is a mix of Windows XP, Windows 2000, and Linux-based appliances
(a pocket print-server appliance and a TiVo).
Will an expired IP lease be discovered on waking from hibernation? Could
hibernation be the problem? Or is there some other issue that I should be
looking at?
- David
there are tons of such postings, most have to do with mixing DHCP with
static IPs, or with split-second timing problems, or with clearing IP
conflicts after they have occurred.
I suspect that my IP conflicts are related to leases expiring and IP
addresses being reassigned while the original lessee is hibernating.
This is a home network with a cable-modem and a router that serves as my
DHCP server. There are no static IP addresses in the DHCP IP pool range.
Computers in my house are typically hibernated rather than shut down, so
that work in progress can be left open, and so that the computers power on
faster.
I have had intermittent IP conflicts with my old, wired Linksys router. I
eliminated that problem by setting the IP lease length to three years.
My new router is a wireless Netgear, with both wired ports and wireless
connections. This may complicate things a little for two reasons: (1) the
Netgear router does not have a setting to allow one to change the IP lease
length, and the lease length is pretty short, and (2) the same computer
might have one wireless connection and one wired connection. I prefer to
keep wireless disabled for increased security and higher bandwidth, but it
is often convenient to use wireless.
However, the problem still occurred with the old, wired-only router.
My network is a mix of Windows XP, Windows 2000, and Linux-based appliances
(a pocket print-server appliance and a TiVo).
Will an expired IP lease be discovered on waking from hibernation? Could
hibernation be the problem? Or is there some other issue that I should be
looking at?
- David