Re: "Trying to connect" problem with RPC-HTTP
From: Grant (gpsnett_at_hotmail.com)
Date: 02/21/05
- Next message: Heartland: "New Server Requirement"
- Previous message: CJ: "Books on Exchange 2003 migration"
- In reply to: neo [mvp outlook]: "Re: "Trying to connect" problem with RPC-HTTP"
- Next in thread: Grant: "Re: "Trying to connect" problem with RPC-HTTP"
- Reply: Grant: "Re: "Trying to connect" problem with RPC-HTTP"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 21 Feb 2005 21:34:22 -0000
Thats interesting, when I connect using 'outlook /rpcdiag' I get an
'Exchange server connection status' box with no servers listed. It appears
to connect fine but '
netstat -n' shows that it is connecting directly to the main exchange server
and doesnt appear to be going over RPC and using the proxy server.
I used a thawte certificate (21 day trial cert) which at first was showing
as untrusted in IIS. When I used the 'certificate trust wizard' to import
Thawte's root certificate, IIS is seemed to then like it as there are no
errors anymore.
Another interesting thing - as I was checking the basic auth in IIS I
noticed that basic auth was not enabled. Integrated windows authentication
was only enabled, so I 've no enabled basic auth but still not working.
Were using a SOHO sonicwall firewall.
"neo [mvp outlook]" <neo@online.mvps.org> wrote in message
news:O4F96%23EGFHA.2180@TK2MSFTNGP10.phx.gbl...
> 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
>>
>
>
- Next message: Heartland: "New Server Requirement"
- Previous message: CJ: "Books on Exchange 2003 migration"
- In reply to: neo [mvp outlook]: "Re: "Trying to connect" problem with RPC-HTTP"
- Next in thread: Grant: "Re: "Trying to connect" problem with RPC-HTTP"
- Reply: Grant: "Re: "Trying to connect" problem with RPC-HTTP"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
