Re: Computer browsing, NETBIOS

From: Bruce Sanderson (bsanders_at_junk.junk)
Date: 01/30/05


Date: Sat, 29 Jan 2005 16:36:58 -0800

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.

-- 
Bruce Sanderson MVP Printing
http://members.shaw.ca/bsanders
It is perfectly useless to know the right answer to the wrong question.
"Don Jones" <DonJones@discussions.microsoft.com> wrote in message 
news:CE5C8735-B95A-4721-A740-EE9894090B32@microsoft.com...
>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 


Relevant Pages

  • Re: DNS Error after running DCPROMO
    ... point the new domain controller to itself for name resolution, ... whith a default DNS installation. ... > three new servers to the new domain, the message given is: ... when I open DNs admin on the DC, ...
    (microsoft.public.windows.server.dns)
  • Re: 2 sites - vpn link - Slow local browsing
    ... > Does name resolution occur the same way at both sites? ... Do i need wins on the servers? ... domaincontroller and secondary dns on the sec.domaincontroller. ... do i need to install winsservers for this ...
    (microsoft.public.windows.server.networking)
  • Re: Should I be able to browse using network neighborhood?
    ... 5.point PDC and DC to themselves as WINS servers ... are also WINS clients on their NIC IP properties. ... which is likely an Authentication problem which is itself likely a DNS ... Notice that "browsing" is NOT name resolution, ...
    (microsoft.public.win2000.dns)
  • Re: Disaster recovery scenerios for DNS/AD
    ... > scenario then would probably be best to bring up a 3rd server with DNS ... > Primary and Alternate servers that already exist. ... > But for a short-time this caused issues and no resolution occurred. ... >> secondary zone and enable zone transfers. ...
    (microsoft.public.windows.server.dns)
  • Re: Help SMPT Errors
    ... FAIL Reverse DNS entries for MX records ERROR: The IP of one or more of your ... it may mean that your DNS servers did not respond fast enough). ... INFO NS records at parent servers Your NS records at the parent servers ... PASS Parent nameservers have your nameservers listed OK. ...
    (microsoft.public.exchange.admin)

Loading