net neighborhood empty

i got my site to site routing working properly finally. i have two subnets
connected to a third in a pyramidal fashion. 192.168.0.1, 192.168.1.1 and
192.168.2.1; communication between the two is functional from any location.
problem is, now my network neighborhood is empty, originally it would at
least show everything on my subnet. each subnet has a wins server with
replication setup and netbios transport over tcp is enabled over all vpn
interfaces. all clients are 2000 or xp machines and all the servers are
2003. what am i missing here?

any suggestions would be appreciated.

I would disable Netbios over TCP/IP on all interfaces except the local
LAN interface on the RRAS servers.

NN relies on the browser service. The browser service does not like
multihomed servers, especially DCs. Your servers should have only one
interface with Netbt enabled.

Each site will then build a local browse list using broadcasts. Over
time, the browser service will build a network-wide browse list, using WINS
to find the master browsers which are not available by broadcast (as long as
you have at least one domain controller).

See KB 150800 for browsing a segmented network and 188001 for a
description of the browser service.

"Christopher S. Daane" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> i got my site to site routing working properly finally. i have two
subnets
> connected to a third in a pyramidal fashion. 192.168.0.1, 192.168.1.1 and
> 192.168.2.1; communication between the two is functional from any
location.
> problem is, now my network neighborhood is empty, originally it would at
> least show everything on my subnet. each subnet has a wins server with
> replication setup and netbios transport over tcp is enabled over all vpn
> interfaces. all clients are 2000 or xp machines and all the servers are
> 2003. what am i missing here?
>
> any suggestions would be appreciated.
>
>

does that include disabling netbios over tcpip in the demand dial interfaces
as well?

"Bill Grant" <not.available@online> wrote in message
news:(E-Mail Removed)...
> I would disable Netbios over TCP/IP on all interfaces except the
local
> LAN interface on the RRAS servers.
>
> NN relies on the browser service. The browser service does not like
> multihomed servers, especially DCs. Your servers should have only one
> interface with Netbt enabled.
>
> Each site will then build a local browse list using broadcasts. Over
> time, the browser service will build a network-wide browse list, using
WINS
> to find the master browsers which are not available by broadcast (as long
as
> you have at least one domain controller).
>
> See KB 150800 for browsing a segmented network and 188001 for a
> description of the browser service.
>
> "Christopher S. Daane" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > i got my site to site routing working properly finally. i have two
> subnets
> > connected to a third in a pyramidal fashion. 192.168.0.1, 192.168.1.1
and
> > 192.168.2.1; communication between the two is functional from any
> location.
> > problem is, now my network neighborhood is empty, originally it would at
> > least show everything on my subnet. each subnet has a wins server with
> > replication setup and netbios transport over tcp is enabled over all vpn
> > interfaces. all clients are 2000 or xp machines and all the servers are
> > 2003. what am i missing here?
> >
> > any suggestions would be appreciated.
> >
> >
>
>

Hi Bill,

I agree multihomed master browsers will cause problems
by enumerating a separate list for each subnet but this won't
cause the list to disappear. Most of the time this is caused
by a machine pointing towards a different SMB (segment
master browser) most likely on the remote subnet either by
a router forwarding broadcasts or a rogue machine forcing
browse elections in attempt to become the master browser.
A packet sniffer on the problem machine for more than 12
minutes should reveal the host name announcement packet
and where it's going.


"Bill Grant" <not.available@online> wrote in message
> I would disable Netbios over TCP/IP on all interfaces except the
local
> LAN interface on the RRAS servers.
>
> NN relies on the browser service. The browser service does not
like
> multihomed servers, especially DCs. Your servers should have only one
> interface with Netbt enabled.
>
> Each site will then build a local browse list using broadcasts.
Over
> time, the browser service will build a network-wide browse list, using
WINS
> to find the master browsers which are not available by broadcast (as
long as
> you have at least one domain controller).

True, the list will still be there. But if the client looks for a list on
the "wrong" interface, it will see a different one. There are probably
multiple IP addresses in WINS for the browse master. If it looks at the
browse list for the VPN link, it will probably be empty! I imagine he is
getting heaps of browser elections.

"Michael Giorgio - MS MVP" <(E-Mail Removed)> wrote in
message news:#(E-Mail Removed)...
> Hi Bill,
>
> I agree multihomed master browsers will cause problems
> by enumerating a separate list for each subnet but this won't
> cause the list to disappear. Most of the time this is caused
> by a machine pointing towards a different SMB (segment
> master browser) most likely on the remote subnet either by
> a router forwarding broadcasts or a rogue machine forcing
> browse elections in attempt to become the master browser.
> A packet sniffer on the problem machine for more than 12
> minutes should reveal the host name announcement packet
> and where it's going.
>
>
> "Bill Grant" <not.available@online> wrote in message
> > I would disable Netbios over TCP/IP on all interfaces except the
> local
> > LAN interface on the RRAS servers.
> >
> > NN relies on the browser service. The browser service does not
> like
> > multihomed servers, especially DCs. Your servers should have only one
> > interface with Netbt enabled.
> >
> > Each site will then build a local browse list using broadcasts.
> Over
> > time, the browser service will build a network-wide browse list, using
> WINS
> > to find the master browsers which are not available by broadcast (as
> long as
> > you have at least one domain controller).
>
>