network neighborhood problem

  • Thread starter Thread starter joe haydn
  • Start date Start date
J

joe haydn

hi all, Wonder if I can get some help...



1. Sometimes Network Neighborhood disappears completely, sometimes only a
few domain names with some computers appear, sometimes everything is there.
No problem with connecting a machine using UNC format though. Wonder why it
is happening?



2. I wish to enable WINS service on the W2k domain controller, just for a
few remaining NT4 machines in existance. I know that at the WINS server, it
should be configured on its TCP/IP setting to aim itself. Can I really do
that on this domain controller though? Also, Do I need to statically add
non-NT4 machine names in WINS database so that NT4 machines can access them?



3. This leads me to think ... Is it that network neighborhood (ie. My
Network Places) no longer a major aspect of AD paradigm? Is it designed
purposely so that in a pure AD (*without* NetBios and WINS), network
neighborhood ought to appear empty? So that normally the users cannot browse
and are forced to use mapped drives in order to access the network
resources? Am I correct in saying this?

Our network environment is as follows:

W2000 domain with xp and w2k pro (a few remaining nt4)

Several multiple domains in existance, on the same subnet.

NetBios is enabled on all XP and W2K (should I disable it, to prevent NBT
broadcasting?)



Thank you, any suggestion I'd appreciate!

Joe
 
joe haydn said:
hi all, Wonder if I can get some help...



1. Sometimes Network Neighborhood disappears completely, sometimes only a
few domain names with some computers appear, sometimes everything is there.
No problem with connecting a machine using UNC format though. Wonder why it
is happening?
Click to expand...

I don't know if anyone can answer that one. It started with NetBIOS over TCP
(NBT). The browser works fine if you install the NetBEUI protocol on all
machines, but not so well under tcp/ip. Why you can resolve the UNC and not
have it work in the browser is a mystery.
2. I wish to enable WINS service on the W2k domain controller, just for a
few remaining NT4 machines in existance. I know that at the WINS server, it
should be configured on its TCP/IP setting to aim itself. Can I really do
that on this domain controller though? Also, Do I need to statically add
non-NT4 machine names in WINS database so that NT4 machines can access them?
Click to expand...

You can install WINS on the DC, and it should point to itself as its WINS
server. You would point the rest of the workstations to the server, and they
will register themselves. This will also fix the network browser ("My
network Places") problem.

3. This leads me to think ... Is it that network neighborhood (ie. My
Network Places) no longer a major aspect of AD paradigm? Is it designed
purposely so that in a pure AD (*without* NetBios and WINS), network
neighborhood ought to appear empty? So that normally the users cannot browse
and are forced to use mapped drives in order to access the network
resources? Am I correct in saying this?

Our network environment is as follows:

W2000 domain with xp and w2k pro (a few remaining nt4)

Several multiple domains in existance, on the same subnet.

NetBios is enabled on all XP and W2K (should I disable it, to prevent NBT
broadcasting?)
Click to expand...
NetBIOS is not required, but is still nice because of the browser. If you
turn it off, you'll no longer be able to browse the network or be accessible
via the browser, although you can do AD searches. DFS is a good way to
consolidate shares on multiple servers so all users can access them that way
instead of via the network places.
 
Back
Top