vpn fails to resolve remote DNS

I have a Windows 2003 server behind a linksys WRVS4400N firewall.  I have the latest firmware update and it allows GRE packets through on port 1723.  I can create a VPN connection just fine to the 2003 server.

However when I try to get any mapped drives, or resolve any hosts, it fails using the remote DNS.
example, to get to the NAS machine, internal users go to \\nas and in this case the only way to get to it is by IP \\192.168.4.20

DNS resolves internally properly, but NSLookup fails when used from the outside.  This is happening on all of the VPN clients I have.  I have setup more than 30 VPN sites and it is only in the last few weeks that this has started happening.  Using LMHosts is not a viable answer.
AJRenckAsked:
Who is Participating?
 
bhnmiConnect With a Mentor Commented:
Are you using domain\username syntax?
0
 
bhnmiCommented:
how bout if you use the FQDN of the server when doing the lookup? Also, why is editing the host file not an option?
0
 
AJRenckAuthor Commented:
too many machines will be using these machines.  In total over 20 sites it is over 1000 computers that will be VPN'ing in.

Yes, if I use the FQDN it would work for the most part I believe.  I will have to double check.
0
Protect Your Employees from Wi-Fi Threats

As Wi-Fi growth and popularity continues to climb, not everyone understands the risks that come with connecting to public Wi-Fi or even offering Wi-Fi to employees, visitors and guests. Download the resource kit to make sure your safe wherever business takes you!

 
Michael WorshamInfrastructure / Solutions ArchitectCommented:
Please post your ipconfig /all configuration when you are connected to the remote site via VPN. Perhaps its not picking up the remote DNS server when the IP address is assigned.
0
 
dpk_walCommented:
Have you tried adding DNS suffic in the VPN adapter TCP/IP settings; if you are able to ping the remote resources when using FQDN I think with the dns suffix added the things should start rolling.

Thank you.
0
 
AJRenckAuthor Commented:
PPP adapter neoptx3:

        Connection-specific DNS Suffix  . : vsi.com
        Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
        Physical Address. . . . . . . . . : 00-53-45-00-00-00
        Dhcp Enabled. . . . . . . . . . . : No
        IP Address. . . . . . . . . . . . : 192.1.1.160
        Subnet Mask . . . . . . . . . . . : 255.255.255.255
        Default Gateway . . . . . . . . . : 192.1.1.160
        DNS Servers . . . . . . . . . . . : 192.1.1.64
                                            192.1.1.64
        Primary WINS Server . . . . . . . : 192.1.1.64
        Secondary WINS Server . . . . . . : 192.1.1.64

Now I can get to the machine via DNS, but it will not accept a valid user/pass for getting to machines.
0
 
Michael WorshamInfrastructure / Solutions ArchitectCommented:
What is the error that you are getting now -- i.e. what does it say, in detail?
0
 
AJRenckAuthor Commented:
Poor management of the disk array:
They were trying to connect as "administrator" instead of as their own usernames.  I have logged in using the correct usernames now.  BTW, when using nslookup it fails on the lookup but pinging it (with or without FQDN) lets it work.
0
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.