On rare occasions, I get an IP address conflict after waking up from standby or hibernation.
On our network with three computers (set to DHCP), we have a printer at 192.168.1.20 (static) and an ADSL/wireless router at 192.168.1.254 and the DHCP server starts from 192.168.1.1
It is highly unlikely that there is a conflict with the printer.
To say simply (taking note that both PCs are set to DHCP), PC "A" has an IP address of 192.168.1.2 and PC "B" is off. PC "A" hibernates and PC "B" is turned on and receives an IP address of 192.168.1.2.
When PC "B" still has this IP address, PC "A" resumes from hibernation and tries to use IP address 192.168.1.2 , resulting in an IP address conflict.
Why can't network clients configured for DHCP renew its IP address after standby or hibernation (even though some renew the IP address when there is a conflict)?
On our network with three computers (set to DHCP), we have a printer at 192.168.1.20 (static) and an ADSL/wireless router at 192.168.1.254 and the DHCP server starts from 192.168.1.1
It is highly unlikely that there is a conflict with the printer.
To say simply (taking note that both PCs are set to DHCP), PC "A" has an IP address of 192.168.1.2 and PC "B" is off. PC "A" hibernates and PC "B" is turned on and receives an IP address of 192.168.1.2.
When PC "B" still has this IP address, PC "A" resumes from hibernation and tries to use IP address 192.168.1.2 , resulting in an IP address conflict.
Why can't network clients configured for DHCP renew its IP address after standby or hibernation (even though some renew the IP address when there is a conflict)?
Comment