Re: "Trying to connect" problem with RPC-HTTP

From: neo [mvp outlook] (neo_at_online.mvps.org)
Date: 02/21/05


Date: Mon, 21 Feb 2005 11:58:35 -0800

443 is the only port that needs to be opened.

what kind of firewall are you using and/or are you only allowing basic auth
on the RPC Proxy under IIS?

is the site using an internal certificate or one by verisign/thawte/.etc to
secure IIS? The reason that I ask is that with an internal certificate, you
need to ensure that the client workstation has a copy of the signing
Certificate Authority in the Trusted Root certificate store. Outlook 2003
will throw no error or warnings if it can't verify the certificate back to
the signing certificate authority. It just fails the connection and falls
back to RPC.

Also double check that you are getting a RPC/HTTP connection internally.
Start Outlook with the /rpcdiag switch to ensure that it isn't falling back
to RPC while on the corporate LAN

"Grant" <gpsnett@hotmail.com> wrote in message
news:OxO653EGFHA.1396@tk2msftngp13.phx.gbl...
> Ive setup an exchange proxy front end server but I cannot get clients to
> connect through the firewall. I can sucesfully connect using RPC-HTTP when
> Im on the LAN, but when I fire up Outlook from home, I get a username and
> password prompt but then it just sits there saying "Trying to connect" and
> never actually connects.
>
> I read MS article 833401 and have all the updates I need but theres
> something Im missing here. As soon as I connect over a VPN connection,
> Outlook connects fine!
>
> Ive opened up firewall port 443 for SSL traffic to the proxy server, and
> port 80 to the proxy server. Is there anything else that needs to be
> opened?
>
> Can anyone offer any help on this?
>
> Much appreciated,
> Grant
>



Relevant Pages

  • Re: "Trying to connect" problem with RPC-HTTP
    ... 443 is the only port that needs to be opened. ... on the RPC Proxy under IIS? ... The reason that I ask is that with an internal certificate, ... > connect through the firewall. ...
    (microsoft.public.exchange.misc)
  • Re: "Trying to connect" problem with RPC-HTTP
    ... 443 is the only port that needs to be opened. ... on the RPC Proxy under IIS? ... The reason that I ask is that with an internal certificate, ... > connect through the firewall. ...
    (microsoft.public.exchange.connectivity)
  • Re: "Trying to connect" problem with RPC-HTTP
    ... 443 is the only port that needs to be opened. ... on the RPC Proxy under IIS? ... The reason that I ask is that with an internal certificate, ... > connect through the firewall. ...
    (microsoft.public.exchange.setup)
  • Re: SBS 2003 and Outlook RPC over HTTP issues
    ... Did you create a new certificate? ... "Gregg Hill" wrote: ... Look in IIS at your Exchweb, Exadmin, exchange-oma, and RPC sites' ... As pointed out by others, port 80 does NOT need to be open, and yes, ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 and Outlook RPC over HTTP issues
    ... You may have to re-install your SSL certificate. ... Port 80 IS NOT NEEDED. ... Something else is still wrong with your server. ... that port 443 and port 80 must be open to use RPC over HTTP. ...
    (microsoft.public.windows.server.sbs)