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
LVL 1
dnackAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

dnackAuthor Commented:
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.
0
kieran_bCommented:
You have outlook installed on the exchange server?  That is unsupported, and guaranteed to screw something up.

>>Can i confirm only port 80/443 need to open & NAT for it to work across wan

You only need TCP443 for RPC/HTTP

If you have a problem from the workstations, test the certificate first - from a workstation browse to the name you are typing in in outlook -> https://server.domain.com/rpc

If it comes up with a certificate error, fix it.  Outlook cannot deal with cert errors
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Redefining Cyber Security w/ AI & Machine Learning

The implications of AI and machine learning in cyber security are massive and constantly growing, creating both efficiencies and new challenges across the board. Join our webinar on Sept. 21st to learn more about leveraging AI and machine learning to protect your business.

dnackAuthor Commented:
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 ?
0
kieran_bCommented:
>>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
0
dnackAuthor Commented:
Yup it was the SSL certifiacte which i configured wrongly.. thanks
0
dnackAuthor Commented:
good
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.