RPC over HTTP Problem
From: Fred Bloggs (fred_at_bloggs.com)
Date: 03/13/04
- Next message: Stefan Plizga: "Re: RPC over HTTP Problem"
- Previous message: Chris Scharff [MVP]: "Re: Default Username"
- Next in thread: Stefan Plizga: "Re: RPC over HTTP Problem"
- Reply: Stefan Plizga: "Re: RPC over HTTP Problem"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 13 Mar 2004 07:47:11 GMT
A few weeks ago I successfully configured Outlook to connect to Exchange
over the Internet using RPC over HTTP.
Everything was working fine until I setup a new connection on our server to
allow incoming VPN connections.
The VPN connection is native Windows networking connection and the native
Windows Internet Connection Firewall (ICF) was enabled before and after this
setup.
Routing and remote access was not configured as this requires switching off
ICF.
After installing this new connection I could no longer connect using RPC
over HTTP. To clarify, I could not connect to the server without disabling
the ICF firewall.
After a little investigation I discovered that Outlook was requesting access
to the following ports:
1025
1080
1306
135
1985 (UDP)
3240
Opening these ports in the ICF configuration allows me to connect to
Exchange Server, however, I can no longer connect using RPC over HTTP (port
443).
Does anyone know why I can't connect using the new protocol? I made no
changes on the client and this problem has been plaguing me for days. It's a
real pain as I am switching from SBC to Comcast and they block port 135.
Please let me know if you know of any way to force Outlook to connect using
RPC over HTTP or if you have any troubleshooting ideas.
Thank you for your help in advance. Best regards,
Fred
- Next message: Stefan Plizga: "Re: RPC over HTTP Problem"
- Previous message: Chris Scharff [MVP]: "Re: Default Username"
- Next in thread: Stefan Plizga: "Re: RPC over HTTP Problem"
- Reply: Stefan Plizga: "Re: RPC over HTTP Problem"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|