Outlook 2003 with RPC over HTTP issues (Full Version)

All Forums >> [Microsoft Exchange 2007] >> Mobility



Message


neil.potter -> Outlook 2003 with RPC over HTTP issues (29.Aug.2007 6:08:55 PM)

We are having problems trying to use our Outlook 2003 clients out of the building using the RPC over HTTP setup. When you try to open outlook, it sits for a whil ethen asks for a user log on. If I put in my full username i.e. user@domain.com with teh password, it will work but takes a while to kick in. If however I kick the VPN in first, it works without asking to authenticate, as you would expect. I would like to get it working without the VPN in case my clients are in areas where the VPN is not allowed.
We have a single Exchange 2007 server sat behind a Nat firewall. Ports 135 and 6001-6004 are being forwarded to the exchange server. On the server, in IIS under RPC, the authentication is set to Integrated Windows and also Basic. SSL is set to 128bit. We have our own SSL cert setup rather than the built in one. The client (Outlook 2003) is setup for connecting over HTTP by using Basic Authentication and using SSL. If I don't use these settings, it doesn't connect at all.
Any ideas what I'm doing wrong? Can it be setup to work without having to authenticate and also load up much faster?
Thanks




John Weber -> RE: Outlook 2003 with RPC over HTTP issues (30.Aug.2007 2:45:20 PM)

I am a bit confused on your description of the setup.
E2k7 does not need to have anything other than 443 for Outlook Anywhere (rpc/http) to work.
If you have a single server, and it works internally, or via VPN, then open 443 on the firewall, point it at the Client Access Server, and it will work.
Certs must match, but other than that, it is straightforward.

quote:

ORIGINAL: neil.potter

We are having problems trying to use our Outlook 2003 clients out of the building using the RPC over HTTP setup. When you try to open outlook, it sits for a whil ethen asks for a user log on. If I put in my full username i.e. user@domain.com with teh password, it will work but takes a while to kick in. If however I kick the VPN in first, it works without asking to authenticate, as you would expect. I would like to get it working without the VPN in case my clients are in areas where the VPN is not allowed.
We have a single Exchange 2007 server sat behind a Nat firewall. Ports 135 and 6001-6004 are being forwarded to the exchange server. On the server, in IIS under RPC, the authentication is set to Integrated Windows and also Basic. SSL is set to 128bit. We have our own SSL cert setup rather than the built in one. The client (Outlook 2003) is setup for connecting over HTTP by using Basic Authentication and using SSL. If I don't use these settings, it doesn't connect at all.
Any ideas what I'm doing wrong? Can it be setup to work without having to authenticate and also load up much faster?
Thanks




neil.potter -> RE: Outlook 2003 with RPC over HTTP issues (31.Aug.2007 4:36:56 AM)

Thanks for that. Just one query, being quite new to this, you say that Certs must match. I am using a cert from RapidSSL on the server which resolves the right names. My internal DNS name is the same as teh external DNS name to stop any confusion. Do I also have to download a cert to the client?




Page: [1]