climberboy
asked on
Exchange RCP over HTTP not able to connect.
I am trying to get RPC over HTTP working with Microsoft Exchange 2003. When I connect from the LAN (using the Exchange Server's public address) it works fine. As soon as I leave the public network, I get the following error:
"The Exchange server is unavailable."
I am running my own Certificate Authority, and requiring SSL to the server. I have installed the certificate in the "Trusted Certificate Authorities" store, and no longer get the certificate warning when browsing to OWA.
Any help greatly appreciated.
"The Exchange server is unavailable."
I am running my own Certificate Authority, and requiring SSL to the server. I have installed the certificate in the "Trusted Certificate Authorities" store, and no longer get the certificate warning when browsing to OWA.
Any help greatly appreciated.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Oh yea... I tried the registry entries on your site, to no avail. Something else is at work. I'm at a loss as to what.
Growing pains...
Growing pains...
Using tools outside of the site is not allowed under the rules.
I would suggest that you reset the process.
Remove the RPC Proxy element from add/remove programs and then delete the /rpc and /rpc-with-cert virtual directories from iis manager.
Then drop in to a command prompt and type
iisreset
Then put it back in again and do the registry settings.
If you want to try with the commercial certificate then get a trial certificate from RapidSSL before paying out for the full certificate.
Simon.
I would suggest that you reset the process.
Remove the RPC Proxy element from add/remove programs and then delete the /rpc and /rpc-with-cert virtual directories from iis manager.
Then drop in to a command prompt and type
iisreset
Then put it back in again and do the registry settings.
If you want to try with the commercial certificate then get a trial certificate from RapidSSL before paying out for the full certificate.
Simon.
ASKER
Still working on this as other items took priority. I will keep you posted...
ASKER
This is a tough nut to crack. I may have to take your advice on the certificate. First and foremost, yes, it is failing back over to the TCP/IP connection, per the /rpcgiag startup switch mentioned on your site (thanks!). So it isn't working, period.
However, the rpcping utility shows a good connection with no errors.
The certificate is installed and trusted on the test client machine. If I browse to OWA on the server, I no longer get a certificate warning, so my gut says that isn't the problem, but then that may be why I am stuck.
Can I provide you a Remote Desktop login to an email address and let you peek around on the two exchange servers? I see how helpful you have been to everyone, and feel comfortable that you are not going to destroy anything.
Thanks,
Eric.