Re: name resolution order

From: Jeff Cochran (jeff.nospam_at_zina.com)
Date: 10/19/04


Date: Tue, 19 Oct 2004 15:08:22 GMT

On Tue, 19 Oct 2004 09:24:07 -0400, "djc" <noone@nowhere.com> wrote:

>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:

Dependent on whether you're talking TCP/IP name resolution or NetBIOS
name resolution.

TCP/IP:

Hosts
DNS
Cache
WINS
Broadcast
LMHosts

NetBIOS:

Cache
WINS
Broadcast
LMHosts
Hosts
DNS

Now, if you need the seven layers of the OSI model to help bone up on
your NT4 MCSE exams... :)

Jeff

>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!
>



Relevant Pages

  • Re: DNS-NetBios name resolution order
    ... it could help with slow access to shares but that depends on whether there is another problem other that the default name resolution ... You could setup a zone on your local DNS server, add A records for the local hosts and then use this DNS server on home LAN. ... You can add forwarders to the DNS server so the clients can resolve names out on the internet. ... >> of XP will attempt to resolve this name using Netbios. ...
    (microsoft.public.windows.server.networking)
  • Re: AD & BIND: domain listing is slow
    ... > Is it possible to skip NETBIOS resolution or at least shorten the timeout ... The reason is that Browsing is a NetBIOS problem so even ... the DNS resolution for it is technically part of NetBIOS. ... >>> The resolution of machines on the domain is very slow in the Network ...
    (microsoft.public.win2000.active_directory)
  • Re: ping keeps using old IP address of another computer
    ... HOSTS doesn't overrule LMHOSTS. ... The might be TCP/IP and NetBIOS respectively, ... ping novell ... checks first prior to making a DNS request. ...
    (microsoft.public.win2000.networking)
  • 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: Slow rlogin after upgrade to 5.2.
    ... :)> Hemant Shah writes: ... :)>>:)Sounds like a name resolution problem. ... :)> As far as that goes, an nslookup "over there" of your AIX box's DNS ... :)posts its on the hosts defined locally. ...
    (comp.unix.aix)

Loading