SonicWall GVPN clients can only see shares if IP not name is used

I have a good working SonicWall and several of our users need file access to a shared drive.
My testing shows its no problem to see the shares if I use
but not

I have researched it and made sure that I turned on the  "use netbios broadcast" option in the GVPN setup.

We are not in a domain.  I could add X.X.X.X to their individual host files ( I have seen this answer) or just tell them to live with X.X.X.X but was hoping that I was just overlooking something.
Who is Participating?
Blue Street TechConnect With a Mentor Last KnightsCommented:
Hi azpete,

Since the DNS server within the SonicWALL is primarily external as @bbao pointed out you need an internal DNS server but in your case since it's a workgroup you may just have Network Discover turned off.

Here is how you enable Network Discovery in Windows Vista/7:

What is the model of your SonicWALL?

What OS are your PCs?
bbaoConnect With a Mentor IT ConsultantCommented:
how do your GVPN clients get IP address? if DHCP is enabled for the VPN clients, have you specified the corresponding DNS and/or WINS server(s)?
azpeteAuthor Commented:
Thanks for your response,

I must admit DNS is one of my weak points in understanding.  
Since we are not in a Domain I am not 100% sure how local computer names  get resolved !
All the XP and Win7 workgroup workstations point to the SonicWall as their Gateway

The  SonicWalls DNS settings are all public DNS servers ( etc, etc)

I really never thought about how they figure out names in their local workgroup but they do .

( just not our gVPN clients      <grin>

I just did a nslookup command on my workstation ( i am dhcp client) and it replied with one of the public addresses that the SonicWall hands out.

Thanks again, I would very much like to hear your thoughts on this...
Firewall Management 201 with Professor Wool

In this whiteboard video, Professor Wool highlights the challenges, benefits and trade-offs of utilizing zero-touch automation for security policy change management. Watch and Learn!

bbaoConnect With a Mentor IT ConsultantCommented:
> The SonicWalls DNS settings are all public DNS servers ( etc, etc)

since your DNS is pointing to the public DNS server at, it won't help you resolve internal hosts.

> I really never thought about how they figure out names in their local workgroup but they do.

for a non-domain and non-DNS network with only local workgroup, names of Windows computers are resolved master browser and other browsers. please see below the details of different browser system roles.

therefore you do need a local DNS and assign the DNS by DHCP. the DNS resolves both internal hosts as well as external ones by sending unknown names to an external DNS such as
skullnobrainsConnect With a Mentor Commented:
it is likely that the VPN clients do not allow netbios through even if you allow it server-side

did you configure dhcp over vpn ? if you do, you should be able to use dns integration either built in the sonicwall (i guess the feature is supported) or to delegate it to another machine. a small vm running any tiny linux/bsd/solaris version with for example dnsmasq should do
Blue Street TechLast KnightsCommented:
Glad I could help...thanks for the points!
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.