I have a domain member that could not logon today. When I got in I simply turned off her network adapter and turned it back on (to flush the ip, ect). I probably could have used ipconfig /release and renew but this seemed faster.
Our gateway is 192.168.2.2 and her ip address was automatically assigned to 169.254.254.208. Why/How could have this have happened? Her computer worked fine yesterday and she turned it off last night. However, when she got in this morning she could not logon to the domain because the ip address was outside the gateway.
Any ideas,
JOe K.
Windows Server 2003Windows XPDHCP
Last Comment
Will Szymkowski
8/22/2022 - Mon
Will Szymkowski
When you get a 169.x.x.x address this is the APIPA address which windows provides when a machine cannot contact the DHCP server. Check the device manager and see if the Network adapter has been disabled or uninstalled.
If this is not the case what you might want to do is check the cable to make sure that it is working properly. Check the patch panel and the port/switch where this user is connected to.
Will Szymkowski
I would also recommend checking the event viewer to see if there are any errors in there that also might help with this issue. Another thing make sure that the link lights are lit-up and flashing on the back of the NIC. Try uninstalling the NIC from the device manager and reinstalling the card by right clicking on the computer at the top of device manager and click "Scan for hardware changes". This will reinstall the network adapter, then try again.
ClaudeWalker
ASKER
So if the computer has an IP designation within the gateway and DHCP range of the server but loses connection, it will abandon the DHCP IP and reassign a APIPA address?
If this is not the case what you might want to do is check the cable to make sure that it is working properly. Check the patch panel and the port/switch where this user is connected to.