Re: name resolution order

From: Doug Sherman [MVP] (dsherman_at_nospam.tampabay.rr.com)
Date: 10/19/04


Date: Tue, 19 Oct 2004 11:08:25 -0400

The short answer is .... well, it depends. In h node the default search
order for name resolution is:

1. NetBIOS name cache
2. WINS server
3. B-node broadcast
4. LMHOSTS file
5. HOSTS file
6. DNS server

A Windows computer assumes you are seeking to resolve a NetBIOS name unless
you use a winsock based program such as ping or http. In that case, the
search order becomes, cache, hosts file, DNS server, and yup - lmhosts file.

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

"djc" <noone@nowhere.com> wrote in message
news:%235UBr7dtEHA.1336@tk2msftngp13.phx.gbl...
> I knew this at one time but I think I need a refresher. The order of name
> resolution mechanisms used by Windows clients IN ORDER from 1st to last
are:
>
> 1) hosts or lmhosts files
> 2) any configured DNS or WINS servers
> 3) broadcasts
>
> Thats how I remember it.... but its been a while.
>
> 1) could someone please correct me if I'm wrong.
> 2) I am confused about the order with regard to the different types of
> 'names'. Meaning, in my recollection of the order (which may be wrong) it
> combines both DNS and NETBIOS name resolution methods in the same
'tier'...
> this would lead one to believe that the machine firsts attempts say, the
> hosts file, which is for DNS host names, then it tries the lmhosts file,
> which is for NETBIOS names, etc... does it keep flopping back and forth
> between name types like that or does it exhaust all DNS methods before
> moving to NETBIOS methods or vice versa?
>
> any info is apprecated. thanks!
>
>

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.778 / Virus Database: 525 - Release Date: 10-15-2004


Relevant Pages

  • Re: The specified network name is nolonger available
    ... the "The specified network name is nolonger ... > works, NetBIOS is working. ... > you can substitute server with computer if that helps your understanding. ... Edit your LMHOSTS file. ...
    (microsoft.public.win2000.networking)
  • Re: Never Saw Something This Weird
    ... NetBIOS name "OLD". ... The most common reasons for redefining UPN suffixes are ... it's DNS name. ... I'm told was the domain that was created on the 2000 server when AD ...
    (microsoft.public.win2000.active_directory)
  • Re: A g;lobal catalog cannot be located to retrieve the icons from the member list
    ... Please post your Netbios domain name, the AD domain name and the DNS ... Server has eveng logging set to no events, and I am unable to change ... Attr: subschemaSubentry ...
    (microsoft.public.windows.server.active_directory)
  • Re: Browsing Subnets
    ... Another server at the 2nd site also provides the DNS. ... Name resolution possibly (although inefficiently for NetBIOS names) ...
    (microsoft.public.win2000.dns)
  • Re: WHY WINS
    ... uses Netbios names. ... This is not really about DNS and WINS servers, ... does Network Neighborhood depend on the computer browser service ... WINS server must exist fot the DNS server to integrate with (which is why ...
    (microsoft.public.windows.server.networking)