Computer browsing, NETBIOS

[Guest]

I am currently a Windows NT 4.0 Domain with 20 W2K Servers, 20 Unix Servers.
In preparation for AD migration, Enterprise IT group had us remove our DNS
Servers and WINS servers. Right now, we have LMHOSTS and HOSTS files on
Windows Servers. We have disable the computer browser service on all servers
except for the NT 4.0 PDC and BDC. On occasion, the W2K Servers can nolonger
reslove NetBios Names. To resolve the issue, we have ran nbtstat -R to
reload the LMHOSTS file, and reboot. Once the reboot is complete we see all
the computers. One tool we use a log is the terminal services manager, and
only the local server is seen.

What is best way to handle NetBios name resolution without having a WINS
server, and is there some tie into the Computer Browser serivice on W2K that
will help?

Thanks.

Don Jones

 

[Doug Sherman [MVP]]

Well, if IT won't let you have WINS or DNS servers, then lmhosts, hosts, and
broadcast are all thats left. In a non-routed environment, your current
setup should work. If however, you are routing between segments; then you
should enable the computer browser service on at least one (preferably 2)
computers on each segment so that there can be a segment master browser.
Make sure that lmhosts loookup is enabled on the WINS tab - this is the
default, and make sure that every computer has an lmhosts file with a PRE
tag for the PDC. You might get better results if you configure clients to
use b node vs. h node - See:

http://support.microsoft.com/default.aspx?scid=kb;en-us;119493

Doug Sherman
MCSE WIN2k/NT4.0, MCSA, MCP+I, MVP

 

[Bruce Sanderson]

Perhaps what the "IT group" meant was to switch to using the DNS and WINS
services that are installed with the AD Domain(s), rather than independant
ones.

Seems to me that operating any size network without using DNS and WINS (for
downlevel clients) is a peculiar and problematic way to do things.

Name resolution and "Browsing" are separate things. Name resolution is
translating a name to an IP address which can be done by DNS, WINS,
broadcast or LMHOSTS files. Browsing is gathering a list of computer and
other names so that lists can be populated (e.g. in Windows Explorer) for
users to see; that's what the Computer Browser service does. The Browser
service requires name resolution capability, but name resolution works just
fine without "browsing" working.

Browsing (e.g. populating the list of domains and computers in My Network
Places) requires NetBIOS over TCP/IP, but name resolution does not (at least
with Windows 2000 and later).

Even if a computer's name does not appear in My Network Places (a
representation of the "browse list"), name resolution (e.g. in Map Network
Drive, Start, Run or any access by UNC name) will still work as long as
there is a name resolution process available.

 

[Guest]

Thanks for the info. I'll give it a try to see what happens.

Don Jones