My Domain Controller cannot access itself

Weird title I know but that's basically what's happening. I have 2 domain controllers in my environment, both Windows Server 2008 R2. The DC with the FSMO roles is exhibiting some strange behavior. I cannot access any network shares and I cannot edit any group policies from the GPO manager on that server. If I log in to the other DC I can edit GPs just fine (even successfully connect remotely to the other DC).

I'm suspecting the issue with the server being unable to access network shares and being unable to edit GPs are related but I don't know for sure. Anyone have any ideas?
LVL 22
Russ SuterSenior Software DeveloperAsked:
Who is Participating?

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

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.

Peter HutchisonSenior Network Systems SpecialistCommented:
1. Run DCDIAG on the server
2. Make sure Windows Firewall is turned off.
3. Make sure User Access Control is turned off.
4. Make sure TCP/IP are set to static and its own IP is in the DNS list.
5. Run Net Share to view available shares (Sysvol and Netlogon should be included).
Russ SuterSenior Software DeveloperAuthor Commented:
Steps 2 thru 5 check out. Step 1 revealed some issues.

DCDIAG revealed several issues starting with this one:

      Starting test: SysVolCheck

         [SERVER] An net use or LsaPolicy operation failed with error 53,

         The network path was not found..

         ......................... SERVER failed test SysVolCheck

Open in new window

Dirk MareSystems Engineer (Acting IT Manager)Commented:
Looks like a DNS issue run
dcdiag /test:dns

Can you resolve the server name via ping..
Ping servername

From another workstation and the server with the problem?

Russ SuterSenior Software DeveloperAuthor Commented:
Actually it was a NetBIOS issue. It was completely disabled. The fix was to run the following commands the reboot.

sc config lmhosts start= auto
sc config netbt start= auto

It's working again!

Thanks for your assistance though.

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
Russ SuterSenior Software DeveloperAuthor Commented:
Ultimately, the fix was as I described. However the suggestions provided helped greatly.
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
Active Directory

From novice to tech pro — start learning today.