RPC Server unavailable at new site
Posted on 2014-01-09
This is an odd one, although I think it's a WAN connectivity, or firewall issue, while the Network Team looks at it I thought I'd ask....
We set up a new site with an Server 2012 AD controller, File Server, and SCCM server. All of the servers are virtual guests running on a VMware 5.1 server on an "Office in a Box" Cisco UCS system. We can connect to the site via http, telnet, etc. from any of our other sites. We can connect to this new remote site similarly. We can use UNC, Event Viewer, etc. (other RPC apps) from the other sites to the new remote site. However, at the remote site anything using RPC, notably port 135, outward to another site will not work. I get RPC 1722 "RPC server unavailable" errors for various things like replication, directory services, cannot access remote file shares out from the remote site.
Anything RPC I try in the internal remote site will work. Anything RPC related outside the remote site will not work.
Cisco and the WAN provider say everything is going through. If I use TraceTCP from the remote site out on port 135 it stops at the gateway at the remote site. If I use TraceTCP to test other ports (53, 80, etc.) it will route out of the remote site network. Of course, the WAN provider and Cisco say they don't see an issue.