• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 447
  • Last Modified:

Rpc server unavailable

Originally our network only had one domain controller. It is running server 2003. Last week I added a secondary domain controller to the network on a fresh install of server 2008.

The only thing that seems to be effected negatively on the network by the addition of the new DC is our exchange server that is running exchange 2003 on top of server 2003. One or two times a day, all of our employees that use imap to connect to the mail server are disconnected. When they try to recconnect is says that it can't resolve their username or password. This problem doesn't effect people who are using outlook. Restarting all the exchange and DNS services doesn't fix the problem. The only thing I can to to resolve the issue is to reboot the server.

Also, when this problem occurs, I can no longer remote into the mail server on a domain account. I have to remote in and log in as a local administrator or else it gives the message saying that it cannot log me on because the RPC server is unavailable.

Any ideas?

0
David11011
Asked:
David11011
  • 3
  • 3
1 Solution
 
MegaNuk3Commented:
Did you rerun
Setup /domainprep
After adding the new DC so exchange can use it?
0
 
MegaNuk3Commented:
Also confirm that AD replication is happening between the 2 DCs. Add a test user to DC1, add a test user to DC2 and then confirm both users appear on both DCs
0
 
David11011Author Commented:
Yes, I've run domainprep.
I have confirmed that the DCs are replicating. I created a test user in AD from both DCs and they both showed up on both DCs
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
MegaNuk3Commented:
If you run policytest.exe from the Exchange files does it show both DCs as having the SACl right? The exchange server should be logging an event every 15 minutes about the AD topology. 2080 event ID I think. Look in that event and ensure the DCs have the same values. E.g. 77710011 or something similar
0
 
David11011Author Commented:
I ended up loading a new exchange 2003 box and migrating all my mailsboxes over to that one. I'm not have anymore problems with this. Thanks for all your guy's help
0
 
David11011Author Commented:
I took the cheater's way out and didn't fix the problem
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now