Quantcast
Channel: File Services and Storage forum
Viewing all articles
Browse latest Browse all 10672

Windows 2012 R2 DC in Windows 2003 domain, users cannot access any shares

$
0
0

I had a 2008 DC die in a domain that it is functioning at 2003.  We were in the process of starting to roll out new hardware for all 9 sites, starting with the head office which is where we have 2 x 2003 DCs.  The decision was made to replace the failed DC instead of try to repair it.  I was successfully able to build out a 2012 R2 server, add it to the domain and promote it as a DC/GC.  It is currently the only DC in that site.

After adding the appropriate roles, for file and printer sharing I created the first share user's home folder.  While testing the folder I was unable to access it from an XP as well as W7 client, logged in as the domain admin.  I confirmed the local system authenticated with the new server as well as tested the UNC share locally on the server, all Share and file NTFS permissions are correct and confirmed.  I then tested the sysvol and it too is inaccessible.  I cannot access any share for that matter, including the printers.  On an XP machine I see the server in network neighbourhood but when I click it I get "\\server is not accessible.  You might not have permission to use this network resource.  Contact the administrator of this server to find out if you have access permissions.  The specified network name is no longer available."  On a W7 client the error is different but essentially the same "Windows cannot access \\server  Check the spelling of the name.  Otherwise, there might be a problem with your network. Try to identify and resolve network problems, click to Diagnose"


I have also done the following:

- pinged the server using it's IP, NetBIOS and FQDN

- able to telnet over 445 using it's IP, NetBIOS and FQDN

- confirmed the firewall is set to the Domain zone

- confirmed file sharing is enabled on the firewall

- adjusted the inbound firewall rule to allow from deny

- confirmed the sysvol has replicated and correctly shared (still using FRS)

- confirmed all appropriate services are running on the server for discovery and file sharing

Other information, I used a different name for the new DC, the original ended in 01 the new 02, the DNS has been cleaned up and all references to the old DC were removed manually.  I used the MS best practice to remove a failed DC which is no longer available.

WHAT AM I MISSING?





Viewing all articles
Browse latest Browse all 10672

Trending Articles



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