I'm working on an Exchange 2003 server for a customer. It has a problem with the rpc over http configuration. I have double checked all the registry entries and the IIS settings and permissions. I logged into a working 2003 Exchange server and went through all the settings one by one and checked everything and they both appear to be setup the same but it still doesn't work. The problem appears to be with the RPC Proxy or IIS. When testing with the Exchange Connectivity Analyzer it fails at the RPC Ping. If I go to IIS and open up the RPC virtual directory and right click on rpcproxy.dll and click on browse, I get the username and password prompt and then get "HTTP Error 404 - File or Directory not found." I have posted results from the Exchange Connectivity analyzer and RPCping below. Since I can't get the standard blank page to open when browsing to rpcproxy.dll it appears that it has to be an issue on the server not with the firewall etc. I have tried deleting all the Exchange web services from IIS and restarted the Exchange System attendant to restore the web services to a clean default config. Also tried removing the RPC and RpcWithCert virtual directories, Uninstalled the RPC over HTTP proxy, then reinstalled the proxy. Any help is appreciated. Testing RPC/HTTP connectivity. The RPC/HTTP test failed. Test Steps Attempting to resolve the host name mail.servername.com in DNS. The host name resolved successfully. Additional Details Testing TCP port 443 on host mail.servername.com to ensure it's listening and open. The port was opened successfully. Testing the SSL certificate to make sure it's valid. The certificate passed all validation requirements. Test Steps Checking the IIS configuration for client certificate authentication. Client certificate authentication wasn't detected. Additional Details Testing HTTP Authentication Methods for URL https://mail.servername.com/rpc/rpcproxy.dll. The HTTP authentication methods are correct. Additional Details ExRCA found all expected authentication methods and no disallowed methods. Methods found: Basic Testing SSL mutual authentication with the RPC proxy server. Mutual authentication was verified successfully. Additional Details Attempting to ping RPC proxy mail.servername.com. RPC Proxy can't be pinged. Additional Details A Web exception occurred because an HTTP 404 - NotFound response was received from IIS6. C:\Program Files\Support Tools>rpcping -t ncacn_http -s mail.servername.com -o m ail.servername.com -P "USERNAME,DOMAIN,*" -H 1 -u 10 -a connect -F 3 Enter password for RPC/HTTP proxy: Exception 1724 (0x000006BC)

Run through this 1st =- http://www.petri.co.il/forums/showthread.php?t=45402Sukh

I already went through that article and tried the suggestions. Thanks though.

You do haver SSL enabled? Do you use SSL offloading? Maybe terminate at the firewall? Do you use a FE/BE topology? WHat happens if you go to https://mail.xxxxx.com/rpc<o:p></o:p>Sukh

I've been testing from inside the network to eliminate the firewall as a problem. When I go to https://mail.myserver.com/rpc locally on the server, I get the login prompt, then after the domain\username and password are entered I get the http 404 error. It should bring up a blank page. It is a single server and its a domain controller/global catalog. I used the following instructions as a quide to check everything http://technet.microsoft.com/en-us/library/bb125001(v=exchg.65).aspx.

Does that dll exist here? c:\windows\system32\rpcproxy\rpcproxy.dll Also try and follow this - -http://support.microsoft.com/?kbid=248033Sukh

I did check and the file does exist in the correct location. The Virtual Directory also points to the correct location. I also verified the web extentions by comparing the settings for the virtual directory on the broken Exchange 2003 server to a working Exchang 2003 server with RPC over HTTPS enabled. Thanks.

Can you check the event logs for any errors?Sukh

Hello, [Check the RpcProxy ValidPorts] ======================= 1. On the RPC proxy server, start Registry Editor (Regedit). 2. In the console tree, locate the following registry key: HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc\RpcProxy 3. In the details pane, right-click the ValidPorts subkey, and then click Modify. 4. In Edit String, in the Value data box, type the following information: ExchangeServer :6001-6002; ExchangeServerFQDN :6001-6002; ExchangeServer :6004; ExchangeServerFQDN :6004 Note: ExchangeServer is the NetBIOS name of your Exchange server. ExchangeServerFQDN is the fully qualified domain name (FQDN) of your Exchange server. If the FQDN that is used to access the server from the Internet differs from the internal FQDN, you must use the internal FQDN. [Check the 6004 port settings in registry] ============================== HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeSA\Parameters Value name: HTTP Port Value type: REG_DWORD Value data: 0x1772 (Decimal 6002) HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeSA\Parameters Value name: Rpc/HTTP NSPI Port Value type: REG_DWORD Value data: 0x1774 (Decimal 6004) [Check NSPI interface protocol sequences] ============================== HKLM\System\CurrentControlSet\Services\NTDS\Parameters Type: REG_MULTI_SZ Name: NSPI interface protocol sequences Value: ncacn_http:6004 Thanks, Simon

Hello, [Check the RpcProxy ValidPorts] ======================= 1. On the RPC proxy server, start Registry Editor (Regedit). 2. In the console tree, locate the following registry key: HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc\RpcProxy 3. In the details pane, right-click the ValidPorts subkey, and then click Modify. 4. In Edit String, in the Value data box, type the following information: ExchangeServer :6001-6002; ExchangeServerFQDN :6001-6002; ExchangeServer :6004; ExchangeServerFQDN :6004 Note: ExchangeServer is the NetBIOS name of your Exchange server. ExchangeServerFQDN is the fully qualified domain name (FQDN) of your Exchange server. If the FQDN that is used to access the server from the Internet differs from the internal FQDN, you must use the internal FQDN. [Check the 6004 port settings in registry] ============================== HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeSA\Parameters Value name: HTTP Port Value type: REG_DWORD Value data: 0x1772 (Decimal 6002) HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeSA\Parameters Value name: Rpc/HTTP NSPI Port Value type: REG_DWORD Value data: 0x1774 (Decimal 6004) [Check NSPI interface protocol sequences] ============================== HKLM\System\CurrentControlSet\Services\NTDS\Parameters Type: REG_MULTI_SZ Name: NSPI interface protocol sequences Value: ncacn_http:6004 Thanks, Simon