Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm in quite a pickle. I'm trying to log in to one of our Windows Server 2003 servers but I keep getting the error message:

Windows cannot connect to the domain, either because the domain controller is down or otherwise unavailable, or because your computer account was not found. Please try again later. If this message continues to appear, contact your system administrator for assistance.

This server hosts our production SQL server. The domain controller is running and my account has not been disabled or deleted. The server is hosted in a nearby data center so I can travel if need be.

Any advise on what I should do next?

share|improve this question
up vote 2 down vote accepted

If this is just a member server you should be able to click the drop down on the login screen and change it to "Login to "This Computer". As long as you've got the local administrator or another account account enabled and set with a password you should be able to login.

share|improve this answer
I was able to log in locally. Now what can I do? – Bryan Roth Jun 13 '12 at 18:04
I would start with checking DNS and making sure it is correctly configured to point to the DC's as the DNS servers. Beyond that, you can check the event logs to see if there are any errors. – Rex Jun 13 '12 at 18:16
Like Rex said, check the DNS first. Try to ping between the servers and see what responses you get. Try to ping both the IP address and the names of the servers. Post the results here. – ErnieTheGeek Jun 13 '12 at 19:10
@ErnieTheGeek I was able to ping both the IP address and names of the domain controllers. – Bryan Roth Jun 14 '12 at 2:34
I'd try leaving and rejoining the domain. You'll want to do this during off hours as it will require a restart which will take your SQL database offline. – ErnieTheGeek Jun 14 '12 at 13:45

You may need to reset the computer account to resolve the issue. You can do this by dis-joining and re-joining the server to the domain or through AD Users & Computers -> find the computer account -> right-click -> Choose reset.

share|improve this answer
Will this result in having to restart the computer that was reset? – Bryan Roth Jun 14 '12 at 2:05
Re-joining will for sure. Not sure about the account reset though – Paul Ackerman Jun 14 '12 at 23:44

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.