G
Guest
Frequently when I resume my laptop from suspend and/or switch to a different
wired Ethernet LAN, the Ethernet interface fails to obtain an IP address via
DHCP, instead using an automatic 169.* address.
An error message appears in the event log:
"Your computer was not assigned an address from the network (by the DHCP
Server) for the Network Card with network address XXXXXXXXXXXX. The
following error occurred: The object already exists.. Your computer will
continue to try and obtain an address on its own from the network address
(DHCP) server."
Disabling and re-enabling the interface, running the Diagnose process, and
releasing/renewing the IP address do not correct the problem. I have also
tried the resolution in KB928233 to no avail. The only resolution I've found
is to reboot the machine.
I would like to find a resolution that does not require rebooting (or
handing 250 bucks to Microsoft for useful support). Is there some way to
trace the operation of the DHCP client service, similar to ptrace on L*nux?
wired Ethernet LAN, the Ethernet interface fails to obtain an IP address via
DHCP, instead using an automatic 169.* address.
An error message appears in the event log:
"Your computer was not assigned an address from the network (by the DHCP
Server) for the Network Card with network address XXXXXXXXXXXX. The
following error occurred: The object already exists.. Your computer will
continue to try and obtain an address on its own from the network address
(DHCP) server."
Disabling and re-enabling the interface, running the Diagnose process, and
releasing/renewing the IP address do not correct the problem. I have also
tried the resolution in KB928233 to no avail. The only resolution I've found
is to reboot the machine.
I would like to find a resolution that does not require rebooting (or
handing 250 bucks to Microsoft for useful support). Is there some way to
trace the operation of the DHCP client service, similar to ptrace on L*nux?