Re: Cannot see computers by name



it all has to do with 'the browser service' operation over VPN, basically,
it don't work, hasn't worked properly (over VPN) on any version of Windows.

You are able to connect to 'the NETBIOS name' because it and the AD DNS name
are similar and the VPN connection is picking up DNS (and yes maybe WINS)
from the server. When you tell XP/Vista 'start, run, \\server (otherwise
\\netbios_name)' it doesn't say 'OH, that's a NETBIOS name, I'll resolve it
through the browser service', what it does is say 'hmmmm, name, and I need
IP, what are my name resolution methods?', it then falls through it's name
resolution methods trying to resolve the name, starting with DNS. Similar
story for 'search' (not sure, it may query LDAP, whose location it gets from
DNS).

The preferred (possibly only, not sure) method of populating 'My Network
Places' is the browser service. Doesn't work reliably over VPN, never did.

"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: Connecting to Windows Network via VPN
    ... You have a share folder on you windows ... You have established connection to you remote network via vpn. ... secondary DNS address 10.1.2.3 ... pptpconfig: pppd process exit status 0 ...
    (Fedora)
  • Re: When Domain Controller DNS is unavailable, workstations cannot resolve names
    ... The problem is that the SBS Box is NOT down. ... Outlook functions normally without the VPN but it is absolutly neccissary ... What I want to do is have the primary DNS point to the DC but when the DC ... >> I have a situation where some workstations are logging onto the domain ...
    (microsoft.public.windows.server.sbs)
  • When connection to the DC is down, I cannot resolve Domain Addresses on the Internet
    ... I have posted this earlier and received a responce from a GSEC. ... remote locations that log onto the DC via a VPN tunnel (That should always ... the remote computer from fielding DNS queries from the DC. ... >> I have a situation where some workstations are logging onto the domain ...
    (microsoft.public.windows.server.sbs)
  • 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)

Loading