"Windows cannot connect to the domain, either the Domain Controller is down or because the computer account was not found"

"Windows cannot connect to the domain, either the Domain Controller is down or because the computer account was not found"  I deleted DNS entries and re-added to domain.  These were are few remaining 2000 machines and a couple servers.  Everything works after the re-add. I upgraded backup exec to 11d on a domain controller.  After that is when the issues started.  Any ideas.  Just want to understand what happened here.  Could it be anything to do with sql upgraded?

Thanks
LVL 2
mkurtzhalsAsked:
Who is Participating?
 
Brian PiercePhotographerCommented:
Also make sure that the computer account is valid on the domain. On the workstation right click on "My Computer" and select properties, Use the Network ID button on the Computer Name tab to put the computer back into a workgroup and then repeat the process but add the computer back to the domain.
0
 
SysExpertCommented:
None of that should have affected the AD and DC connectivity.

Did you do any AD or DNS checks using the Windows resource kit tools ?

Anything in the server event logs ?

I hope this helps !
0
 
Brian PiercePhotographerCommented:
Make sure that all machines point to the Windows DNS server (normally the Domain controller) as the preferred DNS server. The alternate DNS server should be blank unless you have two or more Windows DNS servers, in wihcn case another Windows server can be specified.

Stop and restart the NetLogon Service to re-register the SRV records.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
mkurtzhalsAuthor Commented:
KCTS-  
My post states that I have already did the re-add to the domain with success.  I just want to know what could have caused this issue.

Thanks
0
 
mkurtzhalsAuthor Commented:
Any ideas?
0
 
MMA_itCommented:
I had this happen because there was a duplicate pc name on the network.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.