RPC OVER HTTP WORKS INTERNALLY BUT NOT EXTERNALLY

Depending on whether your using HTTP or HTTPS, you will need to forward port 80 or 443.

Those ports don't need to be forwarded on your firewall - they are ports that Exchange uses internally.

You need to have SSL forwarded with a certificate installed in IIS, and configure RPC over HTTPS to point to your external DNS.

Follow this link for more info:

http://www.amset.info/exchange/rpc-http-server.asp

Jay

i deleted those other post and forwarded port 80 to my exchange server and I get the login prompt but then it never connects

Have a look under the Tutorials section of this link:
http://www.msexchange.org/pages/search.asp?query=rpc
There are lots of RPC/HTTPS articles there.

Come to think of it, do you have a computer (say a laptop) that can be connected to the server either directly via the LAN, and also from the Internet?  Since you said that it works internally, it would be good if you could use a computer that is known to work internally, and then try to get it to connect externally.  That way, you can be sure that all your settings are right, and that you need to look at the firewall.

yea I do that is what I am using.  A laptop.  

Is there any way you can get the laptop connected externally, get the IP address, and then temporarily allow all traffic from that IP to the server - just to see if there is a firewall problem?  As far as I know, this doesn't require any other ports beside the HTTP/S ones, but it's possible that a sophisticated firewall might need to be told more about the kind of traffic going through it.

You have to have an SSL certificate in order for it to work externally.  It is a misnomer to call it RPC over HTTP, when it is in reality RPC over HTTPS.  If you try to connect just over HTTP, you'll be banging your head against a wall for days.

no right now im just doing rpc/http  im still not getting anywhere

i tried the firewall portion as well. Im allowed access.  Does the global catalog server have to be windows 2003 in order for this to work?

On the computer that you say works internall, go to Start/Run and type in outlook.exe /rpcdiag.

Under the Conn heading if it is working properly it will say HTTPS.  If it is not working properly it will say TCP/IP.

when i type that in Outlook just pops up.  I dont get anything else.

Make sure that you don't already have OL running.  The /rpcdiag switch will open OL as normal, but there should be another window appearing on the screen somewhere.

it says tcp/ip