Re: RPCoHTTP always has 4 failures
- From: "Kiran Otter" <kiranotter@xxxxxxxxx>
- Date: Tue, 11 Jul 2006 16:56:24 -0400
Ah, I only had the 2nd option checked. Turning both on allows it to work.
It connects much faster, thank you. It shows 2 failures instead of 4, but
the difference in speed connecting is much better.
Thanks,
Kiran
"Ward Flowers (MSFT)" <wardf@xxxxxxxxxxxxxxxxxxx> wrote in message
news:%23TH3bCQpGHA.2292@xxxxxxxxxxxxxxxxxxxxxxx
In the RPC proxy setting of outlook do you also have the following
selected?
In the RPC-HTTP settings on the client select the two options:
ON fast networks, connect using HTTP first, then connect using TCP/IP
ON slow networks, connect using HTTP first, then connect using TCP/IP
--
Ward Flowers (MSFT)
Microsoft Exchange Support Engineer
This posting is provided "AS IS" with no warranties, and confers no
rights.
"Kiran Otter" <kiranotter@xxxxxxxxx> wrote in message
news:O2saeuOpGHA.3936@xxxxxxxxxxxxxxxxxxxxxxx
Thanks for replying, Ward.
This sounded like a great idea, but when I add this registry entry,
Outlook doesn't even prompt me to log in, it just says the server is
unavailable, and asks if I want to retry, work offline, or cancel.
Kiran
"Ward Flowers (MSFT)" <wardf@xxxxxxxxxxxxxxxxxxx> wrote in message
news:O5sJJ6DpGHA.504@xxxxxxxxxxxxxxxxxxxxxxx
Outlook will try to resolve locally to the exchange server before going
through the internet path that way if the user is on the network they
will get direct TCP connection to the home server.
You can try this Regkey:
Disclaimer: Warning If you use Registry Editor incorrectly, you may
cause serious problems that may require you to reinstall your operating
system. Microsoft cannot guarantee that you can solve problems that
result from using Registry Editor incorrectly. Use Registry Editor at
your own risk.
On the Client Box ONLY
HKEY_Current_User\Software\Microsoft\Office\11.0\Outlook\Rpc
Type: DWORD
Name: DisableRpcTcpFallback
Value: 1
Note: with this key in place you will not resolve locally even if you
are on the local network with the Exchange server.
--
Ward Flowers (MSFT)
Microsoft Exchange Support Engineer
This posting is provided "AS IS" with no warranties, and confers no
rights.
"Kiran Otter" <kiranotter@xxxxxxxxx> wrote in message
news:OEnQrmDpGHA.2444@xxxxxxxxxxxxxxxxxxxxxxx
I've set up RPC over HTTP using SSL on a new server.. (a GoDaddy
dedicated 2003 server.)
I'm not new to RPCoHTTP.. it was pretty easy to set up.. but every time
I connect to it, under any account, there is a bit of a delay as it
connects. It always shows HTTPS as the protocol in the connection
status window.. but nothing under the req/fail column.. until it
connects, then shows 4 failures every time.
I've tried this from two different internet connections, disabled
firewalls, etc.. no difference. I am running Routing and Remote Access
on the 2003 server as a firewall, and to allow VPN connections, though
will eventually do away with the VPNs since it's only for migration
purposes from our existing Exchange box.
It almost seems as if Outlook doesn't know to start with HTTPS.. and
fails trying HTTP the first 4 times. Is there somewhere to tell
Outlook to always use SSL?
Thanks,
Kiran
.
- References:
- RPCoHTTP always has 4 failures
- From: Kiran Otter
- Re: RPCoHTTP always has 4 failures
- From: Ward Flowers \(MSFT\)
- Re: RPCoHTTP always has 4 failures
- From: Kiran Otter
- Re: RPCoHTTP always has 4 failures
- From: Ward Flowers \(MSFT\)
- RPCoHTTP always has 4 failures
- Prev by Date: Re: Single Instance Ratio
- Next by Date: Re: Can i restrict the number of messages sent by a user in exch 0
- Previous by thread: Re: RPCoHTTP always has 4 failures
- Next by thread: Re: Where is this message coming from?
- Index(es):
Relevant Pages
|