Re: RPCoHTTP always has 4 failures

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

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





.

Relevant Pages