There are several factors that come into what a client sees in the browse
list (NetHood). Firstly, providing you've not disabled NetBT (NetBIOS over
TCP/IP - turn off or on under the WINS section of TCP/IP properties) and the
'Computer Browser' and 'NetBIOS over TCP/IP Helper Service' are still
enabled and are running you will see all machines who also match this
configuration on the local subnet. Machines from other subnets can also be
seen, providing the same options apply to those (remote) machines and the
local (to the remote subnets) master browsers can contact the domain master
browser. WINS helps, but isn't strictly needed, as the browse masters take
care of the cross subnet traffic -the rest (the client stuff) is pretty much
all done via broadcast traffic.
NetBEUI will resolve this on a per-subnet level but is not an optimal
solution -you only need TCP/IP why complicate things with another protocol,
or even bother with such a basic and redundant protocol?. You need to
ensure that the appropriate services are running (the helper can cause other
issues too - like GPO processing failure) and that you are using NetBT. If
this is left as default, it'll be obtaining this setting from DHCP -which is
on by default, but could have been changed.
As much as some of us are keen to move on and bin NetBT, applications and
even bits of Windows simply aren't ready for that change.
--
Paul Williams
_______________________________
http://www.msresource.net
Join us in our free, public forum:
http://forums.msresource.net
_______________________________
We have recently developed a browser issue in that when
opening network neighborhood some users see all servers
and pcs while other only see member servers and pcs or
just the domain controllers.
I have run the active directory tools and the system says
all is fine.
Any ideas?
Thanks, Roy
