Can't resolve Exchange server via VPN

When I VPN to our server and run Outlook, I cannot connect to the Exchange Server UNLESS I put a route in my local Host file:


With this information in my Hosts file, it connects first time every time but without it fails.  Not really a biggie as it works by making this amendment, but I'm sure a simple DNS tweak would 'resolve' this issue?
Who is Participating?
-Juddy-Connect With a Mentor Author Commented:
Our domain controller (which also controls DNS and VPN) ALSO has the Exchnage Server software on it, they are the same machine.
When you connect to the VPN, the VPN connection provides you with an IP address and likely also gives you an IP of a DNS server to resolve DNS requests on that network. Is it giving you the IP of a valid DNS server in the domain the Exchange server is in?
-Juddy-Author Commented:
The Exchange Server software is on the same Server that I VPN in on.  The DHCP Relay Agent (on Routing and Remote Access) does indeed point to our DNS Server.
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

OK, so after making the VPN connection open a command prompt on your PC and type this:
nslookup exchangeservername

(obviously replace exchangeservername with the name of your Exchange server)

Does that yield the appropriate IP address for the Exchange server? I would guess not given the issue you are having but might tell you something.

Also from the PC and in the command prompt, when you do a "ipconfig /all", does it show the IP of the correct DNS server in the list of DNS servers?

And just to be sure, the DNS server in question, this is a domain controller on your network that is the same domain the Exchange server is in, yes?
you need to specify the DNS in the DHCP for the VPN client.

or just manually enter the DNS address in the TCPIP settings under the VPN NIC on your PC
-Juddy-Author Commented:
Ok, to test this I used a remote PC, removed the information I had added into the local Hosts file and then connected the VPN.  When I start Outlook, I cannot connect to the Exchange Server (shows as disconnected) and I cannot browse our corporate network by using server names (\\myserver\my files etc) but if I use the IP address, it does work.  

When I run nslookup myservername I get:

server: (my ISP)
Address (Tiscali's name server, I think)

Non Autoritative answer:

Address: AND (No idea, and they are not and our our IP addresses)

Ipconfig /all shows the correct DNS information for our internal network but for some reason, three entries:

192.***.***.11 (Our Dns Server and Domain Controller)
192.***.***.15 (A file server and backup Domain Controller)
192.***.***.11 (Our Domain controller, again!)

Re-adding the record to the local hosts file means that I can use Outlook, connect to Exchange and browse by network names.
-Juddy-Author Commented:
As an added note, when I ping the Exchnage Server (once connected to the VPN, Host File has entry removed) it fails to reply, but does elude to the fact that's it's trying to resolve:

So it's kind of looking in the right direction, as it adds the domain name after the hostname.  Not sure if that helps!?
try pining the excahnge.domain.local rather than just exchange
-Juddy-Author Commented:
Sorry mate, you have lost me there! Could you explain that last post?
when you ping exchange it will append the domain.local which is the fuly qualified domain name.

what happens if you yupe:

ping exchange.domain.local? does it resolve

rather than just ping exchange which is not resolving?
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.