RPC over HTTPS Almost Working!!!
Posted on 2006-06-06
1 Windows 2003 Server SP1, MS Exchange 2003 SP1, this machine has active directory installed and is a global catalog.
I have installed “Rpc over http” and I have installed CA. I have edited the registry options, Valid ports and NSPI interface protocol sequences as instructed. I then shutdown MSExchangeSA as instructed and rebooted my server.
I am using a client that is directly connected to the same subnet. (No firewall!)
IIS – Default website – rpc – has been configured for https/ssl only and basic authentication.
I installed a server certificate on the server and also connected the client to the server and installed a client certificate and tested successfully by using IE to connect to the RPC virtual directory and getting access denied. But then adding rpcproxy.dll and getting a blank page. If I click on the lock it shows the proper certificate and shows status as internet.
My outlook client is configured to use HTTPS only, 128bit encryption and basic authentication. And fast and slow networks using http first are checked.
If I connect using outlook.exe /rcpdiag… I get the connection status page showing mail as https but directory as tcpip!?!?
I had a test network setup almost identical to my production one above and I had the same problem. It was port 6004 wasn’t listening. I fixed that by editing the registry under NSPI and rebooted and it worked fine… Now I have the same issue with my production network but cannot get it to work. Port 6004 is listening!
Any help would be greatly appreciated.