Re: Cannot see computers by name

Maybe some clues and links here:

Can not see vpn clients in SBS domain network view
http://groups.google.com/group/microsoft.public.windows.server.sbs/browse_thread/thread/89f19acb4865f5df/448aa8f34bad8704?hl=en&lnk=st&q=hardware+vpn+cannot+see+workstations+in+my+network+places#448aa8f34bad8704

--
Merv Porter [SBS-MVP]
============================

"Brian" <Brian@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E642D648-4D82-445B-A3C6-FEB1529BF67F@xxxxxxxxxxxxxxxx
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: Sites
    ... For location-aware services the clients will need to find a service at the main site regardless. ... You can make the clients work as though they are connected to the network but slow, or not connected to the network at all. ... Recently we installed 10 workstations in a subclinic 60 miles away. ... The tech who set this up, now gone, placed a router at the subclinic and the router routes to the hospital for one network and the default gateway is to another router connecting to the Internet. ...
    (microsoft.public.windows.server.general)
  • Re: Internet Access without Network Resource Access
    ... Networking, Internet, Routing, VPN, Anti-Virus, Tips & Troubleshooting on ... > network printers. ... Symantec Antivirus Server manages all workstations on ...
    (microsoft.public.windows.server.networking)
  • Re: Possible inside security breach
    ... By default "authenticated users" can add up to ten workstations to a domain which ... means that ANYONE that know a logon/password for a domain account can add a ... ipsec policy to use for network communications restricted to only domain ... > who connect via a VPN. ...
    (microsoft.public.win2000.security)
  • Re: Cannot see computers by name
    ... NetBIOS is allowed over TCP at all workstations. ... The VPN box itself has ... but what happens in My Network Places that is ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot see computers by name
    ... but what happens in My Network Places that is ... the VPN when displaying records in My Network Places. ... It is the only way I can see that would match the apparent one-way NetBIOS ... Each remote LAN has about six workstations ...
    (microsoft.public.windows.server.sbs)