|
bjblackmore -> RE: RPC over HTTPS Troubles - Tried Everything! (27.Mar.2008 6:06:10 AM)
|
Well I installed the RPC over HTTP component onto the other DC/GC and it had no effect. I've also removed our certificate from IIS, which was created using an internal CA, and used a wildcard (so we could use it for all published sites), and replaced it with a Thawte test SSL certificate, just in case that was causing a problem. But this made no difference.
The error messages I'm constantly getting are:
Failed Connection Attempt
Log type: Web Proxy (Reverse)
Status: 1460 This operation returned because the timeout period expired.
Rule: OWA & Outlook Anywhere
Source: External (194.xxx.xxx.25)
Destination: (exchange.domain.com 192.168.1.3:443)
Request: RPC_OUT_DATA http://owa.domain.com/rpc/rpcproxy.dll?EXCHANGE:6004
Filter information: Req ID: 09051610; Compression: client=No, server=No, compress rate=0% decompress rate=0% ; FBA cookie: exists=no, valid=no, updated=yes, logged off=no, client type=unknown, user activity=yes
Protocol: https
Failed Connection Attempt
Log type: Web Proxy (Reverse)
Status: 64 The specified network name is no longer available.
Rule: OWA & Outlook Anywhere
Source: External (194.xxx.xxx.25)
Destination: (exchange.domain.com 192.168.1.3:443)
Request: RPC_IN_DATA http://owa.domain.com/rpc/rpcproxy.dll?EXCHANGE:6004
Filter information: Req ID: 0905160e; Compression: client=No, server=No, compress rate=0% decompress rate=0% ; FBA cookie: exists=no, valid=no, updated=yes, logged off=no, client type=unknown, user activity=yes
Protocol: https
Our valid ports entry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\RpcProxy is set to:
exchange:6001-6002;
exchange.domain.com:6001-6002;
owa.domain.com:6001-6002;
exchange:6004;
exchange.domain.com:6004;
owa.domain.com:6004
Does this look correct? Should it be in a certain order? I read 1 post that said it started to work after someone re-ordered their valid ports.
Using RpcPing (RpcPing -t ncacn_http -s exchange.domain.com -o RpcProxy=owa.domain.com -P "user,domain.com,password" -I "user,domain.com,password" -H 1 -F 3 -a connect -u 10 -v 3 -e 6001) internally completes 1 call in 100.000ms/T, so internally everything seems OK. But if I run the same Rpcping test externally, but add "-B msstd:owa.domain.com” for mutual authentication, there is a long delay, then it fails with Exception 1722.
If I try to connect to https://owa.domain.com/rpc/rpcproxy.dll from the exchange server itself and from the ISA server an authentication popup opens, after entering my domain username & password I get a blank page, which is apparently correct according to the kbs I've read. I've jsut removed RPC over HTTP from the exchange server, rebooted, then re-installed RPC over HTTP and re-set the valid ports, as I read somewhere that was a possible fix, but it hasn't helped.
I'm now at a loss, I've done everything I can think of, read every forum article and kb, but can't think of where to go next!? Any more suggestions would be most welcome!
Ben
P.S. When I put the client on the internal network and connect, it seems to work with RPC over HTTPS fine, if I run Outlook.exe /RPCDIAG the following screen is shown, with all HTTPS connections established.
[image]http://i155.photobucket.com/albums/s317/bjblackmore/outlook-rpcdiag.jpg[/image]
|
|
|
|