dnack
asked on
RPC over HTTP can only work with Outlook 2003 on exchange 2003 server but not other client computers
I have a single exchange 2003 server (DC and GC). I successfully managed to get rpc over http to work on the outlook 2003 that was installed on the exchange server itself.
In the LAN on another PC, i tried to configure the rpc over http on outlook 2003 on another PC with the same outlook settings the resulted connection was TCP/IP. i am using MS Windows CA and exported the cert to the other PC. OWA using SSL is also working fine. Can anyone tell me ehat went wrong?
I will get it up in the LAN before testing on the WAN, Can i confirm only port 80/443 need to open & NAT for it to work across wan
In the LAN on another PC, i tried to configure the rpc over http on outlook 2003 on another PC with the same outlook settings the resulted connection was TCP/IP. i am using MS Windows CA and exported the cert to the other PC. OWA using SSL is also working fine. Can anyone tell me ehat went wrong?
I will get it up in the LAN before testing on the WAN, Can i confirm only port 80/443 need to open & NAT for it to work across wan
ASKER
Nope. the outlook installed on the exchange server was working perfectly arlight with https. With the exactly outlook setting on another client PC, it only connect tcp/ip.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
So far outlook in exchange does not have any problem. Only on the client have problem. What should be the normal respond on the broswer for https://server.domain.com/rpc ?
>>So far outlook in exchange does not have any problem.
Start counting down.
That aside, the normal response for /rpc would be that it prompts you for a username and password (of which none will work). The real point of it is to see if you have a certificate prompt - if you do not get a certificate prompt, then move onto the next step, which is, reconfigure outlook; http://www.amset.info/exchange/rpc-http-client.asp
Kieran
Start counting down.
That aside, the normal response for /rpc would be that it prompts you for a username and password (of which none will work). The real point of it is to see if you have a certificate prompt - if you do not get a certificate prompt, then move onto the next step, which is, reconfigure outlook; http://www.amset.info/exchange/rpc-http-client.asp
Kieran
ASKER
Yup it was the SSL certifiacte which i configured wrongly.. thanks
ASKER
good
Check these articles.
http://www.msexchange.org/tutorials/Troubleshooting-RPC-over-HTTPS-Part2.html
http://www.msexchange.org/tutorials/Implementing-RPC-over-HTTPS-single-Exchange-Server-2003-environment.html
thanks,
consultkhan