RPC over HTTPS on a Single Server
Posted on 2006-07-05
Running on a windows 2003 machine with Exchange 2003. Have read almost every question/answer on this site and the links that they go to. When running outlook /rpcdiag on my LAN I am immediately connected via TCP/IP. From outside the LAN we are getting a prompt for our credentials which when providing the wrong credentials pops up again, so there is communication with the server, but with proper credentials we get no connection.
In Exchange Server Manager under the RPC-HTTP tab we have not set it to RPC-HTTP back-end server yet because we don't know what changes it is making to the firewall incase we need to revert, and also because it wasn't mentioned in all of the articles so we are not 100% sure.
Does anybody know what changes occur when you switch to back-end server? And are there any other ideas as to why we can't even connect via HTTPS on the LAN?