RPC Server is Unavailable
hi
plz go through attached screenshot. I am getting RPC server unavailable in my exchange server whenever trying to create new user, trying to open any user properties, trying to open exchange tasks.
rpc-error.JPG
plz go through attached screenshot. I am getting RPC server unavailable in my exchange server whenever trying to create new user, trying to open any user properties, trying to open exchange tasks.
rpc-error.JPG
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Hi. I had the same problem. And I've finally found a solution. It all comes down to a name resolution problem that occurs when you're trying to setup the RUS for the subdomain.
It seems that the Exchange server tries to resolve the subdomains DC hostname using only the NetBIOS name (that would be SUBDC instead of subdc.sub.domain.local) and thus fails to connect to the subdomain's DC when trying to issue the RPC calls.
For me it helped to add an entry in my c:\windows\system32\driver
SUBDC 192.168.1.1
(of course with appropriate hostname and IP)
But you could also use a WINS server to enable correct name resolution.
After that was done, I had no problems setting up the RUS for the subdomain. And after that was done, my Exchange server was also a member of the "Exchange Enterprise Servers" group in the subdomain automatically.
I really hope that this will help you. Good luck.
It seems that the Exchange server tries to resolve the subdomains DC hostname using only the NetBIOS name (that would be SUBDC instead of subdc.sub.domain.local) and thus fails to connect to the subdomain's DC when trying to issue the RPC calls.
For me it helped to add an entry in my c:\windows\system32\driver
SUBDC 192.168.1.1
(of course with appropriate hostname and IP)
But you could also use a WINS server to enable correct name resolution.
After that was done, I had no problems setting up the RUS for the subdomain. And after that was done, my Exchange server was also a member of the "Exchange Enterprise Servers" group in the subdomain automatically.
I really hope that this will help you. Good luck.
Is that server (on which Exchange is installed) a DC?
If not, or if there are other DC's the server is using, i'D first check the firewall on those. It should allow for everything from exchange server. If you can, disable it at all, even just to test (and disable even the Exchange server's firewall, if u can.).
Are there DC Orphan records in your domain? Did you demote a DC in the past, when EX was working?
Did it demote successfully?
If not you should look for removing that orphan DC record BEFORE going on with that exchange case. Results in a domain with such problems are unpredictable.
HTH.
If not, or if there are other DC's the server is using, i'D first check the firewall on those. It should allow for everything from exchange server. If you can, disable it at all, even just to test (and disable even the Exchange server's firewall, if u can.).
Are there DC Orphan records in your domain? Did you demote a DC in the past, when EX was working?
Did it demote successfully?
If not you should look for removing that orphan DC record BEFORE going on with that exchange case. Results in a domain with such problems are unpredictable.
HTH.
Premium Content
You need an Expert Office subscription to comment.Start Free Trial