Tuesday, March 15, 2016

No logon servers available even when ping works on one

I recently did some troubleshooting in an Active Directory environment. A power outage had just occurred, and suddenly some workstations were unable to find a logon server even though I could ping a properly-functioning server from them.

The clue appeared in the IP configuration: the DNS suffix and the DNS servers were gone. The router responsible for DHCP had somehow lost those items; it was using a blank DNS suffix and Google's DNS servers. That explained why only some machines were affected - laptops (not affected by short power outages) didn't get a new DHCP lease because they didn't reboot.

When I restored those settings and ran ipconfig /renew and ipconfig /flushdns on the affected machines, everything started working again.

No comments:

Post a Comment