I have a Windows 2008 R2 domain controller that has been up and running since last June (10 months). Clients are all Windows 7. Recently (2 months or so) I started getting errors fairly regularly that state that there are no logon servers available. Another symptom, is that often when a computer does log in, it has limited access to the network. (I am assuming it is getting an APIPA address, but don't remember if I checked this or not.) Typically both of these errors resolve themselves if I reboot the computer that is having the problem. Lately it is taking multiple times to reboot before the problem resolves itself. If I log in locally and set a static IP address it always immediately resolves both problems. This is what makes me believe it is a problem with DHCP. My thought is that if the client doesn't get the proper DNS settings, then it won't be able to find the network server. I have checked the DHCP settings and don't see anything unusual here.
Other Info
- I did recently add another member server to the domain. It's roles include Terminal Services (Remote Desktop) and WSUS. The problem seems to have increased when this server is running, but I cannot say this with absolute certainty.
- Both Servers are running using Hyper-V on a Windows Server 2008 R2 box
- On my campus I do have a second network (using the same switches) that uses a different subnet. (about 10 client computers) This network all uses static IP addresses and the DHCP server on the other Domain Controller (2003) is turned off and disabled.
Any insight or ideas would be appreciated.
Scottrie