DNS-NetBios name resolution order

Is there a way to make a XP Pro box joined to a domain to broadcast NetBios
name resolution packets before trying DNS queries?

"Albilol" <(E-Mail Removed)> wrote in message news:<#(E-Mail Removed)>...
> 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

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" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) om...
> "Albilol" <(E-Mail Removed)> wrote in message
news:<#(E-Mail Removed)>...
> > 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

This has always been a problem. Switching machines between locations,
especially between domains causes all sorts of problems with the required
settings. You can try setting up different profiles, or have a look at
something like Netswitcher.

"Albilol" <(E-Mail Removed)> wrote in message
news:#(E-Mail Removed)...
> 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" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed) om...
> > "Albilol" <(E-Mail Removed)> wrote in message
> news:<#(E-Mail Removed)>...
> > > 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
>
>

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" <(E-Mail Removed)>
>References: <#(E-Mail Removed)> <(E-Mail Removed) >
>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" <(E-Mail Removed)> wrote in message
>news:(E-Mail Removed). com...
>> "Albilol" <(E-Mail Removed)> wrote in message
>news:<#(E-Mail Removed)>...
>> > 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.