Hi,
I'm hoping someone can help me out here. I have a server 2008 R2 domain controller that seems to stop communicating with itself and refusing new connections every 24 hours, the server also stops resolving DNS queries. This all started after the previous domain controller was turned off and we had to remove it from AD without using dcpromo. This is now the only server in the environment.
The server has multiple other roles installed on it such as RDS, IIS and Print Server (Yes, this is less than ideal, but it is something that I have had dumped on my lap, it does not have RRAS).
I have performed a meta-data clean up of the old system and as far as I can tell there aren't any other references in DNS or the AD Schema referring to the old server. Initially we thought it could be port exhaustion, but we have allowed a larger number of ports and the issue still persists.
The server has a 4 port NIC, all are disabled except a single port. I've read that teaming them would be a good idea, regardless of whether they're all enabled or not, does this seem plausible?
The active NIC is the highest on the connection list. We have tried disabling IPV6 completelyas well as setting IPV4 as the preferred method. We have enabled it again since then.
Restarting the DNS and Netlogon services don't help resolve the situation. I have tried restarting these services and using ipconfig /registerdns.
Once the sever reboots it finds itself as the Domain Controller/GC and continues on it's merry way.
I've tried everything under the sun to fix this, and I'm fast running out of ideas. Has anyone run into a similar situation or have any idea on how to resolve this?
The error messages we see in the event log are:
ADWS: Active Directory Web Services was unable to determine if the computer is a global catalog server.
Group Policy: The processing of Group Policy failed. Windows could not obtain the name of a domain controller. This could be caused by a name resolution failure. Verify your Domain Name System (DNS) is configured and working correctly.
The network configuration of the server is:
Ethernet adapter Local Area Connection 4:
DHCP Enabled: No
Autoconfiguration Enabled: Yes
Link-local IPv6 Address: fe80::b4bc:70cf:8986:6db%14(Preferred)
IPv4 Address: 192.168.0.2(Preferred)
Subnet Mask: 255.255.255.0
Default Gateway : 192.168.0.240
DNS Servers: 192.168.0.2
NetBIOS over Tcpip: Enabled
Tunnel adapter Teredo Tunneling Pseudo-Interface:
Media State: Media disconnected
Connection-specific DNS Suffix:
Description: Teredo Tunneling Pseudo-Interface
Physical Address: 00-00-00-00-00-00-00-E0
DHCP Enabled: No
Autoconfiguration Enabled: Yes
Tunnel adapter isatap.{56B74FD5-3714-4962-B8B3-667702D69964}:
Media State: Media disconnected
Connection-specific DNS Suffix:
Description: Microsoft ISATAP Adapter #3
Physical Address: 00-00-00-00-00-00-00-E0
DHCP Enabled: No
Autoconfiguration Enabled: Yes