RPC over HTTP Outlook 2003 & Exchange 2007
I am working on a SBS 2008 Standard (Exch07) environment which is working great EXCEPT for the RPC over HTTP/HTTPS connection for Outlook 2003.
THE GOOD:
I am able to login to OWA without error.
I am able to login to remote.domain.com/rpc without error.
I am able to ping the domain without error.
remote.domain.com is setup as an A record at Network Solutions to point to the single public IP of the network which is guarded by a Symantec Gateway Security 360.
HTTP, HTTPS, RPC, RDC, and other are enabled for inbound and outbound connections on the firewall.
Outlook is able to connect locally using TCP/IP.
Outlook is able to connect via a pre-established VPN tunnel using TCP/IP.
Running /RPCDIAG on the client all connections show ESTABLISHED when connected locally.
THE BAD:
When selecting to use http/https on slow connections an authentication dialog box pops up and will not allow the user to authenticate when remote.
When selecting to use http/https on fast connections an authentication dialog box pops up and will not allow the user to authenticate when remote OR local.
Running /RPCDIAG on the client all connections show CONNECTING or OFFLINE when connected remotely.
THE UGLY:
This issue occurs with HTTP and HTTPS.
For clarification when I describe the client being remote the client is physically removed from the network (Cable unplugged & no WLAN) and a connection is established with a Verizon Wireless data card using the VZAccess utility.
THE GOOD:
I am able to login to OWA without error.
I am able to login to remote.domain.com/rpc without error.
I am able to ping the domain without error.
remote.domain.com is setup as an A record at Network Solutions to point to the single public IP of the network which is guarded by a Symantec Gateway Security 360.
HTTP, HTTPS, RPC, RDC, and other are enabled for inbound and outbound connections on the firewall.
Outlook is able to connect locally using TCP/IP.
Outlook is able to connect via a pre-established VPN tunnel using TCP/IP.
Running /RPCDIAG on the client all connections show ESTABLISHED when connected locally.
THE BAD:
When selecting to use http/https on slow connections an authentication dialog box pops up and will not allow the user to authenticate when remote.
When selecting to use http/https on fast connections an authentication dialog box pops up and will not allow the user to authenticate when remote OR local.
Running /RPCDIAG on the client all connections show CONNECTING or OFFLINE when connected remotely.
THE UGLY:
This issue occurs with HTTP and HTTPS.
For clarification when I describe the client being remote the client is physically removed from the network (Cable unplugged & no WLAN) and a connection is established with a Verizon Wireless data card using the VZAccess utility.
Premium Content
You need an Expert Office subscription to comment.Start Free Trial