Hi
did you check your DNS? is the IP configuration manualy assigned or by DHCP?
dan
Main Topics
Browse All Topicsdomain network, Win2003 server, Win XP pro clients
Different users are occasionally unable to log on and are getting the following 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."
It can happen either when the start up the computer in the morning or when they try to log on after having logged off (but not shut off the computer) the night before. Sometimes if they restart, they are able to log on, sometimes not.
The computers all exist in AD. The user accounts are all valid.
This is not an issue where the computers replaced others with the same name (seems to be the commonly referred to potential cause online). From what I understand, removing the computer and rejoining may resolve this. If so, is that a long-term or temporary solution? ie. does it remove the root cause?
Failing that, what is the next step in troubleshooting this?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
"make sure you client machines TCP/IP settings are correct."
They are. Everything as you outlined.
"is the IP configuration manualy assigned or by DHCP?"
Manual. DHCP is running, but is only used for occasional laptop connections.
"Are all computers current with Windows Update?"
Yes, everything up to date on all computers.
When this has happened in the past, the listed events were quite general. However, I will check again as soon as I can.
I used a workaround to get the computer connected - unplugged the network cable, logged on using local cached credentials, plugged in the network cable. The user's now rabidly checking email and such, so it will be a little bit before I can get near the keyboard without losing a finger.
though most things seem to be killed by DNS, i do not beleive that to be the case here. a timeout is really a DNS issue when it comes to this sort of problem, especially when the problem is intermittent
Could you please run a dcdiag or more important in this one a netdiag and letus know of any errors
anything in the logs would be appreciated also as well as any other info on group policies, such as encryption on the network etc (if applicable)
"Do you have multiple domain controllers? If so, have you verified that replication is happening without errors."
Yes, there are two DCs. I will check this in the morning.
"a timeout is really a DNS issue when it comes to this sort of problem"
The connections aren't timing out. The failed logon error is returned immediately.
"Could you please run a dcdiag or more important in this one a netdiag and letus know of any errors"
I will do so and post in the morning.
Thanks for the good suggestions, all.
Sorry for the slow feedback. I've been afk for most of the day.
Update:
I have resolved the problem for now as outlined in the question - removing the computer from the domain, renaming, and adding it again. My concern is that this addresses the symptom rather than the problem and that it might return.
As you have likely gathered, networking isn't my area. I would feel better if there were reason to believe this was the end of it. Any thoughts on this?
"How's about your event viewer:system... anything being logged in there regarding "Netlogon" errors?"
Yes. The initial system event for each instance is Event ID 3210 - "This computer could not authenticate with \\server.domain.etc, a Windows domain controller for domain DOMAIN, and therefore this computer may deny logon requests ..." (etc)
This was soon followed by Event ID 5719 - "No Domain Controller is available for domain DOMAIN due to the following: There are currently no logon servers available to service the logon request. Make sure that the computer is connected to the network ..." (etc)
"Do you have multiple domain controllers? If so, have you verified that replication is happening without errors."
Replication appears to be working fine.
"Could you please run a dcdiag or more important in this one a netdiag and letus know of any errors"
Netdiag wouldn't run due to a missing dll. I haven't had a chance to look into that further yet.
"anything in the logs would be appreciated also as well as any other info on group policies"
Nothing other that what is above. No gp or encryption issues that I can see.
CORRECTION
"Do you have multiple domain controllers? If so, have you verified that replication is happening without errors."
There is a warning in the File Replication Service log on the secondary DC - Event ID 13508 - "The File Replication Service is having trouble enabling replication from PrimaryDC to SecondaryDC for c:\windows\sysvol\domain using the DNS name server.domain.etc. FRS will keep retrying."
That is the last log entry and it is from around the time the problem started. It appears this is the root cause.
What is the next step in resolving this?
You have probably found this by now, but here is an article about troubleshooting FRS:
http://www.microsoft.com/t
There is mention of a Res Kit util called ntfrsutl .
fs
Something comes to mind as a quick check. Make sure that each Domain Controller has it's SYSVOL shared and that each of them can access the SYSVOL share on each other. There should also be a folder inside each SYSVOL share for your domain.
Also, make sure your DNS zone for the domain is still Active Directory Integrated.
Just checking the basics here.
fs
Business Accounts
Answer for Membership
by: NJComputerNetworksPosted on 2007-02-12 at 08:12:47ID: 18515766
make sure you client machines TCP/IP settings are correct. They need to use the internal DNS server of your domain. in TCP\IP make sure that the DNS tab points to IP addresses of valid internal Windows DNS servers ONLY... and not ISP DNS servers or router DNS servers...