VPN from home DNS resolution issues

  • Thread starter Thread starter Travis Krampy
  • Start date Start date
T

Travis Krampy

Hi

I am having problems accessing my work mail from home. We recently are
upgrading from NT4 Exchange 5.5 to Windows 2003 Server Exchange 2003. We
have DNS set up correctly internally.

We have a VPN tunnel set up through the firewall.

I think the problem I am having is a DNS problem, but not sure how to fix
it.

What happens is when I connect through VPN to get my mail in Outlook 2003, I
started with setting up exchange account, then I put in the server name then
my name clicked "Check Name" and Outlook said that it could not resolve the
server name. I removed the server name and put the IP Address of the server
in the "Microsoft Exchange server" and my name resolved.

Now that sparked something in my head thinking that it was a DNS issue.

I opened a command prompt and tried to ping the server name. No replies. I
pinged IP address and got replies.

I added the servers in my DNS of my TCP/IP settings. Still couldn't get
ping servername.

I added the server and IP address in the hosts file and that finally worked.

I know that using a host file is a quick fix, but I would like to get this
permanently fixed.

Does anyone know what could be wrong with the DNS setup?

Thank you

Travis Krampy
 
In
Travis Krampy said:
Hi

I am having problems accessing my work mail from home. We recently
are upgrading from NT4 Exchange 5.5 to Windows 2003 Server Exchange
2003. We have DNS set up correctly internally.

We have a VPN tunnel set up through the firewall.

I think the problem I am having is a DNS problem, but not sure how to
fix it.

What happens is when I connect through VPN to get my mail in Outlook
2003, I started with setting up exchange account, then I put in the
server name then my name clicked "Check Name" and Outlook said that
it could not resolve the server name. I removed the server name and
put the IP Address of the server in the "Microsoft Exchange server"
and my name resolved.

Now that sparked something in my head thinking that it was a DNS
issue.

I opened a command prompt and tried to ping the server name. No
replies. I pinged IP address and got replies.

I added the servers in my DNS of my TCP/IP settings. Still couldn't
get ping servername.

I added the server and IP address in the hosts file and that finally
worked.

I know that using a host file is a quick fix, but I would like to get
this permanently fixed.

Does anyone know what could be wrong with the DNS setup?

Thank you

Travis Krampy
Click to expand...

This hosts file is the general fix, this tends to happen if the AD Domain
name is the same as the public name.

Check the properties of the VPN connection on the Networking tab, TCP/IP
properties that you have the correct DNS server listed. Then click the
Advanced button, DNS tab and put in the correct DNS suffix for the domain
Exchange is in.
 
Yes the AD domain IS the same as the public name. So you are saying that
the hosts file is a fix? Are there any other fixes that we could use or be
aware of?

Thanks

Travis
 
In
Travis Krampy said:
Yes the AD domain IS the same as the public name. So you are saying
that the hosts file is a fix?
Click to expand...
The host file is the only way you can reliably resolve the DC. It is because
it has a view of both internal and public namespaces and the VPN client has
no way of knowing which is which.
Are there any other fixes that we
could use or be aware of?
Click to expand...

That's about it.
 
Thanks for your help!

Travis


Kevin D. Goodknecht said:
In
The host file is the only way you can reliably resolve the DC. It is because
it has a view of both internal and public namespaces and the VPN client has
no way of knowing which is which.


That's about it.
Click to expand...
 
Back
Top