RPC over HTTPS front end/back end

[BBGCORP]

I'm having trouble connecting through RPC over HTTPS with the following configuration:
Frontend server - RPC over HTTPS proxy enabled
Backend server - RPC over HTTPS enabled back end server

The front end server has a valid SSL certificate, and is currently used as the OWA server. There is a Win2K3 GC that is on a third server.

I've tried all MS support articles and nothing seems to work. I did notice that the VaildPorts registry entry on the front end server doesn't have a reference to the GC, but only to the backend Exchange server. Any ideas?

 

[ShackDaddy]

What happens when you run RPCDIAG? Does your FE server have different internal and external FQDNs? It's ok if it does, but it's easier to slip up if it does.

There are a lot of different things that can go wrong.

They are often in the IIS config. Check the RPC virtual web directory on the FE and see where its home directory is. Should point to RPCPROXY or something like that. And check authentication settings on both front and back ends against the documentation. One helpful thing for me when troubleshooting RPC-over-HTTP is comparing the settings on a working FE/BE pair with the nonworking pair.

ShackDaddy

 

[BBGCORP]

I checked the directory for RPC and everything looked good, right where it was supposed to be (C:\windows\system32\rpcproxy). Maybe I should clarify a bit, I'm trying to set this up for individuals that are outside my LAN, and are connecting via the internet. when I ran the RPCDIAG switch in outlook, I saw the connections being made to my backend Exchange server, and the internal FQDN was resolved, but it would time out trying to authenticate the user.

 

[jimthecanadian]

Are all DC's and GC's W2K3?

When setting up the users from outside your LAN, are you using hte netbios name (I suppose the internal FQDN would work too) of the exchange mailbox server in the "Exchange Server Settings" and the FQDN of your FE (the same one as on the cert) only in the RPC over HTTP proxy config. (I did this and it took me forever to find the mistake)

My FE also only has valid port entries for the BE server and is working fine.

Have you run the various connection tests on the FE:

https://www.microsoft.com/technet/p...070-c01a-4fe7-9ad2-e05c1cb07c2d.mspx?mfr=true