Quantcast
Channel: File Services and Storage Forum
Viewing all articles
Browse latest Browse all 1766

Unable to access Sysvol DFS Shares on 2008 DC "Not Accessible"

$
0
0

Hi Everyone, I recently inherited a server that is having problems with group policy and possibly DFS.  It is a simple environment--one Windows 2008 Server running DC, file sharing, hyper-v (unused) (DC only has one NIC but used to have two until I removed the virtual NIC), IIS.

It started with group policy not working.  I get error 1058:
The processing of Group Policy failed. Windows attempted to read the file \\DOMAINNAME.loc\sysvol\DOMAINNAME.loc\Policies\{31C6F340-016J-11D2-945F-00C06FB984F9}\gpt.ini from a domain controller and was not successful.

So I log into our only domain controller as Administrator.  I go into explorer and try to browse to \\DOMAINNAME.LOC.  When I browse to the location, I get a list of all of the shares on my domain controller (5 Shares Total).  When I try to double click them, I get an error that it is "not accessible".  "You might not have permissions...contact the administrator".

I get the permission errors when I click on all of the shares while logged into the DC as Administrator.  None of the shares work.

So then I open up a new explorer window and browse to \\DCNAME\.  I see all 5 of the shares again.  I can access all 5 of the shares with no problems.

When I ping DCNAME, I get replies from the server's IP6 address.  When I ping DOMAINNAME.LOC, I get the same server's IP4 address.

I'm not very familiar with DFS, but from another website's advice, I ran dfsutil /pktinfo on the problematic DC.  0 entries.  Not sure if that is normal.

In terms of server roles, I have "File Server" installed, but none of the role services such as DFS namespaces, BranchCache, etc.

Any thoughts on this as I'm rather stumped.  Any advice would be greatly appreciated.  Thanks.



Viewing all articles
Browse latest Browse all 1766

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>