Hi,

The name resolution to some pcs in my small workgroup network is very slow.
If I add the names in "hosts" file, it becomes fast. I prefer not using
hosts.
Is there any tool(s) that help me with the following tasks?

1) Shows the computer's NetBios node type
2) Trace the name resolution. Show which methods are being tried to
translate a name to IP address (hosts, cache, broadcast.)

Thank you,
Max

Hi Max,

Thank you for your post.

Regarding the #1, you can run the following command to check NetBios node
type.

IPCONFIG /ALL

The "Node Type" is exactly what you need.

For more information about node type:
KB119493 NetBIOS over TCP/IP Name Resolution and WINS
(http://support.microsoft.com/kb/119493/)

Regarding the #2, normally the Name Resolution Order is: cache(The hosts
file will preload on the computer as cache when booting)-> broadcast. If a
request cannot be addressed by cache, the task will be transfer to next
process.

You can use Network Monitor (blogs.technet.com/netmon/) to check if the
name resolution is using broadcast. If not, you could check the cache by
taking following command:

IPCONFIG /displaydns

For more information about it:
Display and view a client resolver cache using the ipconfig command
(http://technet.microsoft.com/en-us/l.../cc758108.aspx)

Mostly, slow name resolution is not caused by cache. For general
troubleshooting, you can refer to the following link:

Trouble Shooting Name Resolution with NM3
(http://blogs.technet.com/netmon/arch...ooting-name-re
solution-with-nm3.aspx)

Hope it helps.

Robinson Zhang
Microsoft Online Support

On Fri, 24 Apr 2009 00:02:10 -0400, "Max2006"
<(E-Mail Removed)> wrote:

>Hi,
>
>The name resolution to some pcs in my small workgroup network is very slow.
>If I add the names in "hosts" file, it becomes fast. I prefer not using
>hosts.
>Is there any tool(s) that help me with the following tasks?
>
>1) Shows the computer's NetBios node type
>2) Trace the name resolution. Show which methods are being tried to
>translate a name to IP address (hosts, cache, broadcast.)
>
>Thank you,
>Max

Max:

This might be in the "way too obvious" category - but have you checked
their time to get to DNS server? Are they slow just getting to the
server? That would be a different solution set than the resolution
chain.

Hi Max,

Do you have any update on the question? If so, please do not hesitate to
let me know.

Thanks.

Robinson Zhang
Microsoft Online Support