Question Locked

Outlook 2003 RPC over HTTP

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Sorry but this looks a mess.

We recently had a AD (PDC) and Exchange Server 2003 go belly up. We rebuilt the server on new hardware calling it the same name and IP. We have just managed to clear out all the old DNS records all of which were pointing to the old server (even though the new server is called the same). We have now managed to get the Exchange box (2003 Sp2) back up and running, BUT none of our clients can connect using Cache mode unless we Exmerge the mailbox, delete and then add a new mailbox then reconnect. This is not a problem on the LAN, but we have over 50 client who use RPC over HTTP and although the Certificate has been recreated and downloaded, the IIS security is correct only new user can use the system all existing users open RPC/HTTP outlook are asked for the user name and password and then the system takes forever to try and connect (about 3-5 minutes) then comes back with error "The connection to the Microsoft Exchange Server is unavailable. Outlook must be online or connected to complete this action" Outlook then asks for the Exchange login detials which are correct (exactly the same as the new user connected one,s, different name) when you click ok outlook then closes.

I'm sure the Certificate is correct as a new user created after the crash uses the same RPC and Certificates connections (albeit for a different users).
Any help on this one would be greatly appreciated.

3 replies

by bart777

This sounds like a nasty one.

I would start by taking a step backward and looking at AD. You say that your PDC emulator went tango uniform and you rebuilt it using the same name and IP. This may be your root problem. I'm assuming that you had a secondary DC at the time. Verify that the FSMO roles are properly set. If you look at them you should just see the name of the server. If you see the server name followed by a SID you have a problem. You will want to go to NTDSUTIL and sieze the roles from the old server. I've seen a similar problem at another client when they had the magic smoke got loose from their DC.

Here is a helpful link.
http://support.microsoft.com/kb/255504

Let us know if this helps.

by richard.lonergan

Everything seems to be working now EXCEPT...!
We have over 50 client who connect outlook via RPC over HTTP and NEVER connect to the LAN, becaue their OST files appear to be orphaned we now need to reset them up externally.I have read just about every post (maybe not) about this but still cannot connect a external client using RPC over HTTP, if the client is setup on the network and then goes external it works, but setup purely external nope "no Go". HELP.......!!!

This discussion is closed to new replies.