Exchange Server Name Does Not Resolve Externally
Posted on 2012-08-24
Our Exchange server does not resolve externally when setting up a new client.
When a client is setup internally, the name resolves and all external functions, RPC, OWA, etc works fine, even when accessing remotely over the internet.
So the problem comes in when a new client is initially configured EXTERNALLY.
We ran several connectivity tests, including the REMOTE CONNECTIVITY ANALYZER, and all tests passed apart from the following:
Testing the NSPI failed.
An error occurred while testing the NSPI RPC end point.
Attempting to ping RPC endpoing 6004 (NSPI proxy interface) CIEX.CIPSZA.LOCAL
Error (0x6ba) was thrown by the RPC runtime process
I gathered that RPC uses some ports for DNS translation, 6001, 6002, 6004
These are not currently part of our router's NAT rules, and not sure if these ports are required?
We have an internal name for our Exchange server, EXCHANGE.DOMAIN.LOCAL
Which will obviously not resolve externally.
All the TMG rules have been added for Exchange OWA, ACTIVE-SYNC, RPC, etc.
All works, but I realised that RPC works over port 443 and I don't see any provision for ports 6001, 6002 and 6004 in TMG.
Any help in the right direction will be appreciated;