Naming Information Cannot be Locaqted for the Following resaon, DC 2008 R2

Yesterday one of my domain controllers in my domain which is a single domain, with two domain controllers throw up the error when opening Active Directory Users and Computers 'Naming Information Cannot be Located for the following Reason'.

I am not sure what is causing this error but the other DC is running normally.

If anyone has any ideas your thoughts are appreciated.
carlocAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Will SzymkowskiSenior Solution ArchitectCommented:
I would start by making sure that the following services are started on that server.

- NetLogon
- Active Directory Domain Services
- Active Directory Web Services

Check the Directory Services Logs on that domain controller

Run the following commands as well on that troubled DC.

repadmin /replsum
repadmin /showrepl
repadmin /bridgeheads
dcdiag /v
netlogon query dc
netlogon query fsmo
net share

Will.
carlocAuthor Commented:
Hi,
Could this be related to this error, on the same machine I ran windows power shell, but it can back with this message;

"Insufficient winsock resources available to complete socket connection initiation".

Thanks
Will SzymkowskiSenior Solution ArchitectCommented:
It is quite possible. Did you run the other commands that I have listed in my first post?

Will.
Darius GhassemCommented:
A few quick things to try:

1. Make sure your firewall or antivirus software isn't blocking access.

2. Go thru the below link
https://support.microsoft.com/en-us/kb/323542

3. Reboot your DC see if it's just a network hiccup that needs to be cleared.

4. Reset your Winsock but make sure to copy down TCP\IP settings before proceeding.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.