Cannot see computers by name

Here's the short version of the question:

If I can ping a workstation by its NetBIOS name across a VPN and can find it
by its IP address doing a Search for Computers in Network Places, but it does
not appear in Network Places, what am I missing?

Here's the long version of the same question:

SBS2003 domain.
Server & 35 workstations local
Two remote LAN's connected via hardware VPN (i.e. one at host site, one at
each client site)
Each remote LAN has about six workstations
Windows firewall disabled on all stations.
DNS is correctly configured on all workstations to point to the SBS. SBS
points to itself for DNS with correct ISP forwarders.

Both VPN's work perfectly, except for one thing. All workstations can access
the server (e-mail, shared files, printers), I can ping all workstations,
including those across the VPN's, from the server by their NetBIOS names (and
vice versa, workstation-to-server), but cannot see any of the workstations on
one of the remote VPN's via Network Places. I can find them by IP address but
not by name. I can see the PC's via the other remote VPN just fine.

The effect is that I cannot distribute Symantec Corporate to the clients on
one VPN. Symantec says, "If you can't see workstations in Network Places,
then the remote client install won't work." Well, I already discovered that.

So I contacted Netgear about their VPN/router boxes, and they tell me it is
a Windows problem and recommended that I Search for Computers using the IP
addresses of the PC's. This works but does not solve my Symantec problem. I
suspect something in the Netgear FVS318v3 VPN box (FVS338 at host, FVS318 at
good site, FVS318v3 at failing site).

Is there anything I am missing in Windows? My next step is to replace the
failing VPN box with one identical to the working one & THEN go back to
Netgear with proof of the problem.
.

Relevant Pages

  • Re: Changing Corporate subnet address
    ... your workstations & servers after changing the subnet, ... Maybe my thinking is flawed but I believe after changing the subnet I ... VPN users must not be using the same IP network as the ... changes if you have no remote connectivity to them. ...
    (microsoft.public.windows.server.dns)
  • Re: Cannot see computers by name
    ... Have you enabled to allow NetBIOS over TCP at all sites? ... FVS318v3 VPN site remotely via My Network Places. ... Two remote LAN's connected via hardware VPN (i.e. one at host site, ... Each remote LAN has about six workstations ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot see computers by name
    ... Search for Computers; however, I am still unable to see the stations at the ... FVS318v3 VPN site remotely via My Network Places. ... Two remote LAN's connected via hardware VPN (i.e. one at host site, ... Each remote LAN has about six workstations ...
    (microsoft.public.windows.server.sbs)
  • Re: Is it possible to see the network neighbourhood through the VPN?
    ... What's your goal for the VPN (remote administration, file sharing, etc.)? ... What OS are the workstations on your network? ... If all your user and company data is located on the server (for centralized ...
    (microsoft.public.backoffice.smallbiz2000)
  • [opensuse] mount remote NFS share Time Out
    ... I have two SUSE 10.3 workstations in the same network and are running ... want to mount the remote NFS share on a Windows 2003 R2 Server. ... folder.All the network connection between these machine is OK,I'm sure. ...
    (SuSE)