Sysvol / Element not found when trying to access share.

Experts,

Recently, two of our MANY servers recently started reporting problems processing group policy.

When looking at them further, they both have the same symptoms:

Event log reports that a certain GPO.ini file isn't accessible, so group policy processing stops.

When attempting to access \\domain\sysvol it comes with the error pictured below.  I can access \\domain with no problems, but accessing the sysvol share gives the error.

DNS checks fine, and I can nslookup the domain with no issues.

Anybody with any ideas - it would be very appreciated if you could chime in. 22Sep11-SYSVOL-Share.png 2Sep11-SYSVOL-ElementNotFound.png
LVL 5
usslindstromAsked:
Who is Participating?
 
Krzysztof PytkoConnect With a Mentor Senior Active Directory EngineerCommented:
%logonserver% viarable points to DC where clients is authentcated. Wjen you tryt o open share \\domain\sysvol it's requesting access ton and of DCs, so it looks like there is a problem on some DC(s)?

Please make simple test.  Open command-line and do

ipconfig /flushdns
ping domain.local (your DNS-Domain-Name)

try to access share \\domain\sysvol

repeat this action as many times as many DCs in your environment is available. DNS round robin mechanism will switch you to another DC in a list :)

Krzysztof
0
 
Krzysztof PytkoSenior Active Directory EngineerCommented:
Please try to follow this MS article to fix it up at
http://support.microsoft.com/kb/315457

Might be a problem with replication. Please try to run on a DC

dcdiag /c /e /v
and
repadmin /showrepl /all /intersite /verbose

and check if there is no problem.

Regards,
Krzysztof
0
 
usslindstromAuthor Commented:
Thank you for the assistance.

I ran the tests as you suggested.  (Also ran dcdiag previously) - and thankfully nothing errors.

This error is happening on two member servers.  I've already dejoined them from the domain, and re-added them, but they come back with the same error.

Other member servers or clients that connect to the same DCs are fine, and can access the SYSVOL share at the root domain level with no problems.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
usslindstromAuthor Commented:
On note,

From the two servers having the issue, accessing their %logonserver%\sysvol works fine and I'm not given any errors.

Accessing \\domain\sysvol on those same two servers is where the error stems.
0
 
usslindstromAuthor Commented:
You were exactly right.

I missed it.  We had one DC that was booted in "Safe Mode" for some strange reason.  It was the cause of our headaches here.

Thank you very much for the assistance!
0
 
Krzysztof PytkoSenior Active Directory EngineerCommented:
You're welcome :)

Krzysztof
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.