I recomend you get in the habit of *always* using the FQDN and not
single-word Netbios Names. In your example that would be
\\server.companyname.com\share
The VPN connection must always have the correct DNS associated with it in
the TCP specs of the VPN Connectiod (at the Client). Since this is a
Watchgaurd box, and I believe the Watchgaurd boxes does *not* use a true
DHCP for the VPN Clients but randomly grants IP#s from a Pool,...you may not
get the correct DNS unless it is statically assigned in the DUN Connectiod.
You'll have to investigate that yourself.
We once had a Watchguard box and I stopped using it for VPN because of its
limitations,...I now use MS ISA Server (now called MS TMG) as trhe "VPN
Server" and it is a 100x's more flexible.
--
Phillip Windell
www.wandtv.com
The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------
"Eddie Walker" <(E-Mail Removed)> wrote in message
news:AAC76575-452C-41DB-81A7-(E-Mail Removed)...
>I have users that want to access our shares over a VPN.
> I have a watchguard firebox x1000 device.
>
> When I or anyone else connects, we are unable to get to our shares by
> typing
> \\server\share
> nor does the network browse list come up in the network list.
>
> if i type \\server.companyname.com\share it does work?
>
> I now have a mac user that also needs access and even typing the above
> doesnt work.
> Is there something I can do to make this work?
>
> I recall a few years back this did work correctly when we were still
> running wins..
>
> thanks,
> Ed
>