From: Roger Wang (rwang@xxxxxxxxxxx)
Date: Wed Jun 14 2000 - 11:09:20 GMT-3
Window's Network Neighborhood's done roughly this way:
1. Each subnet (broadcast domain is probably a better term here) must have a
"master browser", the winner of that subnet's browser election.
2. All master browsers need to send what they see in their own subnets to a
"domain master browser", usually a DC (domain controller).
3. The domain master browser merges all the info, then sends out a complete
list of the network host names back to each domain browser.
4. When a user double-clicks on the "Network Neighborhood" icon, the host
goes out to that subnet's master browser and requests a copy of network host
names.
To check if a machine is a master browser, use the "nbtstat -a hostname" (or
"nbtstat -A x.x.x.x") command where hostname is the netbios name of the
machine.
If you can stop the communication between subnet's master bowser and the
domain master browser, the hosts on that particular subnet won't be seen (in
Network Neighborhood) by anyone that's not on that subnet. This does not
prevent access to hosts on that subnet because all ports are still open.
HTH,
Rog
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
> Jason T. Rohm
> Sent: Tuesday, June 13, 2000 11:45 PM
> To: 'ccielab@groupstudy.com'
> Subject: Netbios Access-Lists
>
>
> I am having difficulty with Netbios access-lists and the Network
> Neighborhood.
>
> I have a netbios host access-list enabled that successfully blocks access
> to a particular Netbeui server. However, the server continues to show up
> in my Network Neighborhood.
>
> I do not have netbios name caching enabled, and have rebooted my PC to
> eliminate any name caching that might happen on the client side.
>
> What piece am I missing here?
>
> -Jason T. Rohm
> jtrohm@athenet.net
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:23:42 GMT-3