2003 server not staying joined to AD properly to the Domain, affecting other applications that rely on the established credentials from being part of AD, deleting device and rejoining does not work, sid tool does not help either
Software/Hardware used:
ASKED:
July 29, 2009 2:49 PM
UPDATED:
August 28, 2009 4:52 PM
I am having a problem that is a variation on this theme. I have a Windows 2003 server that is a virtual host running Microsoft Virtual Server 2205 R2. The guest server is a windows 2000 server that runs Exchange 2005. For the last 2 days, the guest server has been losing the connection to the domain intermittantly. I can ping both of the domain servers from the guest server. I have to reboot the guest server to re-establish the connection to the domain. Without the domain connection, Exchange does not work.
Until recently, Microsoft would not support Exchange running on a virtual server. Check you IO activity on the host, but your best bet is to put exchange on a physical server.
Sorry, I typed my input in the wrong place and appended it to Minman66′s answer.
As I noted earlier, I have a similar problem. It is very intermittent. I can go for 2 weeks with no problem and then lose the domain every couple of hours for 2 or 3 days.
Here is what I have discovered so far.
1. If you to a cmd prompt on the Exchange Virtual Machine and give the command “ipconfig /flushdns” followed by “ipconfig /registerdns”. That usually restore the connection.
2. If that doesn’t work I go to the DCs (I have 2 of them) and run dcdiag /fix and netdiag /fix. Usually the combination of these commands reconnects everything without rebooting servers.
The errors I get from dcdiag are that all all domain controllers are in use or not responding and LDAP Bind was unsuccessful on directory server.domain.com for distinguished name”
The errors from netdiag are LDAP test failed to query SPN registration on DC,
Can anyone tell me what to do to fix this?