Re: DNS-NetBios name resolution order

From: Sergio Moreno (Sergiom_at_online.microsoft.com)
Date: 04/23/04


Date: Fri, 23 Apr 2004 21:06:11 GMT

Here is a suggestion, it could help with slow access to shares but that depends on whether there is another problem other that the default name resolution
process.
Do you have a Windows server where you can run DNS in your Home LAN?
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 would then use the FQDN to access the local resources i.e. \\FQDN
You can add forwarders to the DNS server so the clients can resolve names out on the internet.

--------------------
>From: "Albilol" <albilol@nomail.com>
>References: <#C2FoCsJEHA.3412@TK2MSFTNGP09.phx.gbl> <ce9a9081.0404200533.3d4a0233@posting.google.com>
>Subject: Re: DNS-NetBios name resolution order
>Date: Tue, 20 Apr 2004 17:21:57 +0100
>
>That is all correct if Win XP isn't part of a domain.
>Now, if XP is joined to a Win2k3 domain, and after that is connected to
>another network it seems to try DNS queries first. This situation arrrises
>from disconnecting a notebook from the office LAN and reconnecting to a Home
>Lan which doesn't have any domain controllers at all. Anyway, at home in a
>peer-to-peer LAN, the notebook becomes very slow at connecting to Windows
>file shares.
>Does anyone have some insight on this issue?
>
>
>
>
>"Matt Hickman" <hemo_jr@space.com> wrote in message
>news:ce9a9081.0404200533.3d4a0233@posting.google.com...
>> "Albilol" <albilol@nomail.com> wrote in message
>news:<#C2FoCsJEHA.3412@TK2MSFTNGP09.phx.gbl>...
>> > Is there a way to make a XP Pro box joined to a domain to broadcast
>NetBios
>> > name resolution packets before trying DNS queries?
>>
>> Name resolution is context driven. If you access a remote computer for
>> file sharing using a computername, the file and printer sharing service
>> of XP will attempt to resolve this name using Netbios. If you use an IP
>> address or FQDN, it will skip Netbios name resolution.
>>
>> Generally, if you have WINS and the XP box is set up to know about it,
>> you are automatically an H-node. That means the computer tries to resolve
>> the Netbios name through WINS prior to broadcast. If no WINS is set up,
>> the computer default to b-node resolution and it will broadcast to
>> resolve the Netbios name. However, both node types check the Netbios
>> name cache first for names preloaded (using LMHOSTS file) or previously
>> resolved.
>>
>> So essentially, as a default, when use use computer names to access
>> file and print services on the network, XP will use Netbios first and
>> netbios broadcast before DNS.
>>
>> However, if you are using services that are traditionally TCP/IP,
>> host name resolution (which includes DNS) is used. This includes
>> web services, USENET, FTP, PING, et al.
>>
>> --
>> Matt Hickman
>> Mike, you want to discuss the nature of humor. Are two types of
>> jokes. One sort goes on being funny forever, Other sort is funny
>> once. Second time it's dull.
>> Robert A. Heinlein (1907 - 1988)
>> _The Moon Is a Harsh Mistress_ c 1966
>
>
>

-- 
Sergio Moreno
Microsoft Windows Networking
This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at 
http://www.microsoft.com/info/cpyright.htm 
Note:  For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.  


Relevant Pages

  • 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: 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: Verify how a name is resolved
    ... > our network runs both DNS and WINS, and many clients have a HOSTS ... Or can WINS resolve it? ... Win2000 and newer machines uses the DNS process FIRST. ... does not get resolved using the DNS process, then it uses theh NetBIOS ...
    (microsoft.public.win2000.dns)
  • Re: How do I track down which server is resolving my DNS query?
    ... If I pinged it with just the host name, the IP address came back with an incorrect ip addressI have now removed the node from the network. ... DNS Server ... Broadcasts might resolve NetBIOS names (and even be used by a DNS ... enters into both DNS and NetBIOS name resolution. ...
    (microsoft.public.win2000.dns)
  • Re: Name Resolution
    ... Name resolution can occur via DNS, WINS, NetBIOS and registry-specified ... hosts. ... ask each one of them to resolve the name. ... Do I have to enable name resolution on my device? ...
    (microsoft.public.windowsce.embedded.vc)