RE: RPC Over HTTP

From: Frank Brown [MSFT] (fbrown_at_online.microsoft.com)
Date: 10/15/04 

Date: Fri, 15 Oct 2004 19:33:59 GMT

Normally running the CEICW (configure e-mail and internet connection
wizard) and allowing RPC over HTTP (outlook via the internet) option on the
Web services configuration page should configur your server to allow RPC
over HTTP.

Here are some additional troubleshooting steps you can take:

NOTE: If during troubleshooting the RPCProxy.dll has been unregistered or
RPCProxy
has been removed and reinstalled you will see these symptoms.

When the rpcproxy is unregisted and re-registered or the RPCProxy service
has been
uninstalled and reinstalled it resets the Valid Ports key in
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\RpcProxy to 100-5000. The
MSExchange
keys do not get altered in any way. but you will need to manually enter the
correct
values for Valid Ports which are listed below.

Troubleshooting Steps:

1. Verify that the patch from KB article 331320 has been applied to the
client
machine.
2. Verify that the certificate is installed by going to
https://mydomain.com/remote or /owa. You should not be prompted for the
certificate.

3. Verify the following settings in the Outlook profile properties:

a. The Exchange server name. This should be the internal FQDN of the
exchange
server, example: Server.mydomain.local

b. On the connection tab:
"Connect to my Exchange mailbox using HTTP" should be checked.

c. In Exchange proxy settings:

The URL should be the same one as the FQDN of the certificate. Example:
http://mydomain.com
The "Connect Using SSL only" box should be checked.
The "Mutually authenticate the session when connecting with SSL" box should
be
checked.
The Principal name for the proxy server should be the same as the FQDN on
the
certificate. Example: msstd:mydomain.com.
The "On slow networks, connect using HTTP first, then connect using TCP/IP"
box
should be checked.

d. Under Proxy Authentication the setting should be Basic Authentication.

Verify that the following registry keys exist with these settings:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\RpcProxy]
"Enabled"=dword:00000001
"ValidPorts"="<netbios name of server>:593;<netbios name of
server>6001-6002;<netbios name of server>:6004;f<Internal FQDN of
server>:593;<internal FQDN of server>:6001-6002;<internal FQDN of
server>:6004"

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\Parameters
System

Value: Rpc/HTTP Port
Type: REG_DWORD
Data: 0x00001771 (6001)

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeSA\Parameters
Value: HTTP Port
Type: REG_DWORD
Data: 0x00001772 (6002)

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeSA\Parameters
Value: Rpc/HTTP NSPI Port
Type: REG_DWORD
Data: 0x00001774 (6004)

Verify the settings for the RPC Virtual Directory in IIS, the defaults are
as
follows:

Local Path: C:\Windows\System32\RPC Proxy
The following boxes are checked: Log Visits, Index this resource
Application Name: Default Application
Starting Point: Default Website
Execute Permissions: Scripts and Executables
Application Pool: Default AppPool

Directory Security:

Authentication Methods: Basic
Secure Communications: Require Secure Channel is checked. Require 128 bit
Encryption is checked. Ignore Client Certificates is cehcked.

Verify that the RPCProxy.dll is present in the %systemroot%\System32\RPC
Proxy

If all the settings are correct you can use the RPCPing2 utility to assist
with the
troubleshooting proccess. This tool can help verify that the connection
type is
good enough for RPC over HTTP.

If the completion time values are from, say 200 to 600 ms, then the
connection type
is good. If they are higher it could cause connection problems.

Regards,

Frank Brown
Microsoft Small Business Server Support

This posting is provided "AS IS" with no warranties, and confers no rights.

Relevant Pages

  • RE: Outlook indefinitely "trying to connect ..." to Exchange 2003 using RPC/HTTP
    ... I understand that your issue is that the outlook ... sometime does not work when using RPC over HTTP. ... If you use the RPC over HTTP when using the WLAN for the connection, ...
    (microsoft.public.windows.server.sbs)
  • RPC over HTTP Problem
    ... A few weeks ago I successfully configured Outlook to connect to Exchange ... over the Internet using RPC over HTTP. ... Everything was working fine until I setup a new connection on our server to ... After installing this new connection I could no longer connect using RPC ...
    (microsoft.public.exchange.admin)
  • RPC over HTTP Problem
    ... A few weeks ago I successfully configured Outlook to connect to Exchange ... over the Internet using RPC over HTTP. ... Everything was working fine until I setup a new connection on our server to ... After installing this new connection I could no longer connect using RPC ...
    (microsoft.public.exchange.misc)
  • RPC over HTTP Problem
    ... A few weeks ago I successfully configured Outlook to connect to Exchange ... over the Internet using RPC over HTTP. ... Everything was working fine until I setup a new connection on our server to ... After installing this new connection I could no longer connect using RPC ...
    (microsoft.public.exchange.clients)
  • RE: Connection Settings for RPC over HTTP
    ... I wanted to know on a fast connection the best ... How to Create an Outlook Profile for Users to Use with RPC over HTTP ...
    (microsoft.public.exchange.admin)