Windows server 2012 naming information cannot be located because the rpc server is unavailable

Good Day,

We have installed another Windows Server 2012 DC at a new building and are receiving the following error when attempting to open AD Sites & Services and AD Users & Computers:

"naming information cannot be located because the rpc server is unavailable"

Both servers are Windows 2012.

We have verified the server can ping the dc with the FSMO roles at the main location and vice-versa. We can even access each from one another.

Have verified DFS & RPC services are running on both servers.

We have also verified the Site-to-Site VPN is stable between the two locations.

Any assistance with helping us resolve the issue will be greatly appreciated.

Thanks,

Dave
BrockstedtAsked:
Who is Participating?
 
Mike KlineConnect With a Mentor Commented:
For repadmin, you can use repadmin /showreps  (/showrepl is also a good one).   Post that tool

Do you know if you have any port blockages between the FWs.  More on the ports here   http://technet.microsoft.com/en-us/library/bb727063.aspx

Thanks

Mike
0
 
Mike KlineCommented:
Are  the DCs replicating ok? How do repadmin and dcdiag look ok?   Any firewalls between the DCs

Thanks

Mike
0
 
BrockstedtAuthor Commented:
Good Day Mike,

DCs are not replicating properly.

There are two Cisco ASAs that build the site-to-site vpn between the locations.

I have attached the output for the DCDIAG on the remote server.

I am unfamiliar with repadmin, which switches should I use with it?
DCDIAG-Remote-Server.txt
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.

 
Hari Babu BalarajuTech LeadCommented:
Please check the NIC card settings and see if “Client for Microsoft Networks” is checked.

 Run dcdiag and netdom and check if they still fail.  bounce it and test.
0
 
MaheshArchitectCommented:
check if sysvol and netlogon is getting shared on both DCs
Download portqueryUI (GUI version) from Microsft and check if all AD ports are opened between both DCs
Also run dfs management console on DC and run propogation test to identify if sysvol is reachable..
Also run dignostics report.

You can try authoritative restore of sysvol as shown in below article on PDC
http://support.microsoft.com/kb/2218556
http://social.technet.microsoft.com/Forums/windowsserver/en-US/1ac2719f-fa77-4d97-95d2-518b2fea142a/dfsradmin-set-sysvol-as-primary-authoritative-failed?forum=winserverDS

Thanks
Mahesh
0
 
BrockstedtAuthor Commented:
Mike,

Thanks for the assistance in fixing our issue.

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