Problems with RPC over HTTP
Hi Everybody,
Our company have only one exchange server 2003 which runs RPC over HTTP.The problem started when our SSL certificate expired and had to install new one.After installing new certificate some of our outlook client can connect to exchnage using RPC over HTTP but some of the client couldn`t connect including my home PC which is configured in same way as others.I completely removed exchange server from outlook and installed it again but it cannot resolve the mailbox name or FQDN.I am confused cause some of the clients can connect but takes longer than before to connect.When I looked at exchange connection status directory and referal are in disconnected status whilst other are connected.I then checked DNS but it seems to be working fine.SO please help me ........bis
August 4th, 2009 5:00pm
Probably your home machine is still pointing to old expired certificate. Launch OWA and check for SSL certificate in the IE address Bar and see if it reflects to new certificates.
Vinod
|CCNA|MCSE 2003 +Messaging|MCTS|ITIL V3|
Free Windows Admin Tool Kit Click here and download it now
August 4th, 2009 6:53pm
In addition to Vinod's comments, check the output using https://www.testexchangeconnectivity.com/and paste it over here.Harpreet Singh Khandiyal (http://support.microsoft.com/kb/555375)
August 5th, 2009 4:25am
Hi Vinod,
There is no problem connecting with OWA.The certificate is ok and it connects through OWA but nt with outlook.bis
Free Windows Admin Tool Kit Click here and download it now
August 5th, 2009 11:08am
Hi Harpeet,
Thank you very much for link which is of great help to me for testing connectivity.Most of the connection were sucessfully tested and are working fine except Endpoint 6001.It comes up with error "
Attempting to ping RPC Endpoint 6001 (Exchange Information Store) on server email.example.co.ukFailed to ping EndpointSo do I need to check registry and edit the srting value?I went through all the microsoft support websited linked to it and it says there may be a problem with DNS but some of my clients are connected to exchange sucessfully and working.Thank you
bis
August 5th, 2009 12:36pm
Hi,You can find the full list of troubleshooting steps here:Troubleshooting RPC over HTTP Communications:http://technet.microsoft.com/en-us/library/bb124649(EXCHG.65).aspxRegards,Tariq
Free Windows Admin Tool Kit Click here and download it now
August 5th, 2009 4:02pm
Also try out this tool RPCPingCheck the ValidPorts key on the Exchange Server, under HKLM\Software\Microsoft\Rpc\RpcProxy. It should be in the following format<MBX Server NetBIOS>:6001-6002;<MBX Server FQDN>:6004;<MBX Server NetBIOS>:6004;<MBX Server FQDN>:6004;Try to follow commands on the exchange servertelnet localhost 6001telnet localhost 6002telnet localhost 6004 (run this command only if DC is on the Exchange Server, else instead of localhost type gc's name)All these ports should not beblocked as RPC over HTTPS use these ports to communicate.Harpreet Singh Khandiyal (http://support.microsoft.com/kb/555375)
August 5th, 2009 8:01pm
Hi Everybody,Thank you very much for your help guys which solved my problem with outlook but I still have problem with outlook mobile access(OMA).When I try to connect my palm with exchange server it gives an error sychronising.I then tested my connection with exchange using https://www.testexchangeconnectivity.com/and came up with the following errorTesting Http Authentication Methods for URL https://.email.example.co.uk/Microsoft-Server-Activesync/ Http Authentication Test failed Additional Details An HTTP 403 forbidden response was received. The response appears to have come from Unknown. Body is: <body><h2>HTTP/1.1 403 Forbidden</h2></body> After gettingthis errorI checked SSL configuration and form based authentication which seem to be correct.Form based authentication is unchecked and SSL configuration in exchange virtual directory is also unchecked.We run RPC over HTTP in single server
bis
Free Windows Admin Tool Kit Click here and download it now
August 6th, 2009 2:25pm
Glad to know that your RPC over HTTPS is working fine now.For ActiveSync, try the followingUnder IIS Manager, check if there is any IP restriction on Microsoft-Server-ActiveSync v-dir?Try to browse https://OWAURL/Microsoft-Server-ActiveSync and check if you get a blank page after entering credentials. try this on the client and also on the exchange server.Also check the authentication on the same v-dir it should be set to only Basic Authentication
Harpreet Singh Khandiyal (http://support.microsoft.com/kb/555375)
August 6th, 2009 9:31pm
Hi Everybody,
Thank you very much to you all for helping me out of this situation which was indeed nightmare to me.The problem was I forgot to open port 6004 which is for directory and that created the problem and with OMA it was the authentication method was wrong.Once agin thank you very much all the genius guys out there.Feels great after solving problem.
Thank you bis
Free Windows Admin Tool Kit Click here and download it now
August 10th, 2009 4:52pm
This topic is archived. No further replies will be accepted.
Other recent topics
