Name Resolution fails over Netgear Firewall Point to Point VPN


So we have two netgear firewalls that are running a hardware VPN per the instructions here:,10,19&

I realize this is very similar to teh question we had recently asked, please bear with me.

The central location is where the domain\DNS(Win 2003 server) server is bieng hosted, and i know the tunnel is working because i can ping the servers IP address, and even access shared resources via \\<serverIP>, however when i try to access resources via \\<serverName>, everything falls apart.

I have configured the Dns servers on the satellite firewall to be the servers IP address.  When i do a nslookup from a remote machine i get no response from the server.  However dns is running and processes requests locally no problem.

I have enabled netBios on a remote test machine

The other weird thing is that i can browse the web from this remote machine, with the only DNS entry bieng the server, so it seems certain DNS requests are bieng responded to.

Some other info that might be helpfull:
central office lan IP: 192.168.1.
satellite office Lan IP: 192.168.2.x

Id be happy to answer any questions
Who is Participating?
Rob WilliamsCommented:
DotFoil, NetBIOS names do not broadcast over a VPN so you are correct in trying to resolve via DNS. You can resolve NetBIOS names if you have a WINS server, or as per # 2 below you can make use of the LMHosts file. Have a look at items 4-7 below for DNS options in my "name resolution list for VPN's" :-) See if any of those option help.
Connecting to remote devices over a VPN:
1) Use the IP address (of the computer you are connecting to) when connecting to devices such as;   \\\ShareName   or map a drive at a  command prompt using  
 Net  Use  U:  \\\ShareName
2) An option is to use the LMHosts file which creates a table of IP's and computer names. LMHosts is located in the Windows directory under c:\Windows (or WINNT)\System32\Drivers\Etc\LMHosts.sam , instructions are included within the file. Any line starting with # is just a comment and is ignored. Open the file with Notepad and add entries for your computers as below;      CompName       #PRE
Hit enter when each line is complete (important), then save the file without a file extension. To be sure there is no extension ,when saving enclose in quotations like "LMHosts". Now when you try to connect to a computer name it should find it as it will search the LMHosts file for the record before connecting.
More details regarding LMHosts file:
The drawback of the LMHosts file is you have to maintain a static list of computernames and IP addresses. Also if the remote end uses DHCP assigned IP's it is not a feasible option. Thus in order to be able to use computer names dynamically try to enable with some of the following options:
3) if you have a WINS server add that to the network cards configuration
4) also under the WINS configuration on the network adapter make sure NetBIOS over TCP/IP is selected
5) try adding the remote DNS server to your local DNS servers in your network card's TCP/IP configuration
6) verify your router does not have a "block NetBIOS broadcast" option enabled
7) test if you can connect with the full computer and domain name as  \\ComputerName.domain.local  If so, add the suffix DomainName.local to the DNS configuration of the virtual private adapter/connection [ right click virtual adapter | properties | TCP/IP properties | Advanced | DNS | "Append these DNS suffixes (in order)" | Add ]
DotFoilAuthor Commented:

1. so using the server IP does work, and we may just have to set this up with login scripts because name resolution is just not working
2. I have not tried using the LMHosts mostly because this is for an office that is 45 minutes away and would be rediculouse to try and maintain that kinda list.
3. & 4. i have tried to use WINS with no luck
5. I have manually configured the DNS entries on the firewall, and individually for each machine, still i fail to resolve anykind of name, (server Name or FQDN). even though i can ping the server, and locally on the server i can resolve anything i want.
6. oops

Ok so i found the error. There was a Rule in the firewall forwarding all DNS requests to the server. Im not sure why it conflicted with the tunnel, but obviously it did. tunnel works, server names resolve, mapped network drives work.

All is well now.
Rob WilliamsCommented:
Glad you were able to get it working DotFoil.
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

DotFoilAuthor Commented:

thanks for your help, i just returned from the client, and it seems it actually needed WINS added to the remote machine adapter
Rob WilliamsCommented:
If WINS is an option it is usually the most dependable over VPN's, not sure why. If you get into the high end WatchGuards, SonicWall, CheckPoint and Cisco units I find DNS resolution works great.
Thanks for the update,
DotFoilAuthor Commented:
Id love to get it resolving using DNS, i would think the way its set up would allow DNS to resolve, but maybe im issing something on the server.  DNS just times out when performing NSlookup remotely, but it functions fine locally.  Maybe i have more firewall Mis-configuration to sort out.  but for now WINS will work just fine.

Again thanks for your help, if you have any other suggestions to try please let me know.  Thanks!
Rob WilliamsCommented:
If I come up with any other ideas I will be sure to let you know. I am surprised "adding the remote DNS server to your local DNS servers in your network card's TCP/IP configuration" didn't work.

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.