NetBios Name Resolution Problem

  • Thread starter Thread starter KC
  • Start date Start date
K

KC

I know this has been discussed endlessly -- but I can't figure out the
fix after numerous queries and attempts. So I appreciate the help:

Problem -- One XP SP2 portable on home network (through Linksys router)
has classic netbios name resolution symptoms: basically, everything
available through network addresses but not network names (using
NBTSTAT, etc.). All other computers work fine.

I am at a complete loss how to fix this (without creating a LMHOSTS
table which appears to be a lot of work and prone to error - and, even
then, I need a good reference to help set it up).

Current settings: all automatic DHCP, no WINS server specified (don't
understand if this is even relevant in a home network), LMHosts off.

Finally, can't figure out how to view the node setting since it falls
off the screen in DOS, but I assume this is not a problem.

What do you recommend? Glad to provide additional info.

Thanks in advance
 
I know this has been discussed endlessly -- but I can't figure out the
fix after numerous queries and attempts. So I appreciate the help:

Problem -- One XP SP2 portable on home network (through Linksys router)
has classic netbios name resolution symptoms: basically, everything
available through network addresses but not network names (using
NBTSTAT, etc.). All other computers work fine.

I am at a complete loss how to fix this (without creating a LMHOSTS
table which appears to be a lot of work and prone to error - and, even
then, I need a good reference to help set it up).

Current settings: all automatic DHCP, no WINS server specified (don't
understand if this is even relevant in a home network), LMHosts off.

Finally, can't figure out how to view the node setting since it falls
off the screen in DOS, but I assume this is not a problem.

What do you recommend? Glad to provide additional info.

Thanks in advance
Click to expand...

KC,

Please provide "ipconfig /all" from each computer, or examine each yourself.
Read this article, and linked articles, and follow instructions precisely:
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>

Then, look for misconfigured / overlooked firewalls, and at registry setting
restrictanonymous, on each computer. Either can cause problems with NetBIOS
Name Resolution.
<http://nitecruzr.blogspot.com/2005/06/mysterious-error-53-aka-name-not-found.html>
Misconfigured / overlooked firewalls:
<http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>
Registry setting restrictanonymous:
<http://nitecruzr.blogspot.com/2005/07/restrictanonymous-and-your-server.html>

Please let us know if any of these suggestions are of any help. What you learn
may help others in the future, and that's the purpose of these forums.
 
Chuck --

Thanks for the response -- extremely helpful.

However, as it turns out, I tried one last fix after I posted and it
seems to work. Even though I did not know the node value from IPCONFIG
/all, I checked the registry entry
HLM\System\CurrentControlSet\Services\Netbt\Parameters and found the
DHCPnodetype parameter. After backing up the registry branch, I
eliminated the parameter, rebooted -- and amazingly Netbios name
resolution worked perfectly.

Question is since I did not know the IPCONFIG node setting, is this a
true fix or did I just luck into something temporary.

If you think it's a fix , I call it quits. If not, I'm glad to proceed
with your suggestions or any others.

THanks again.
 
Chuck --

Thanks for the response -- extremely helpful.

However, as it turns out, I tried one last fix after I posted and it
seems to work. Even though I did not know the node value from IPCONFIG
/all, I checked the registry entry
HLM\System\CurrentControlSet\Services\Netbt\Parameters and found the
DHCPnodetype parameter. After backing up the registry branch, I
eliminated the parameter, rebooted -- and amazingly Netbios name
resolution worked perfectly.

Question is since I did not know the IPCONFIG node setting, is this a
true fix or did I just luck into something temporary.

If you think it's a fix , I call it quits. If not, I'm glad to proceed
with your suggestions or any others.

THanks again.
Click to expand...

KC,

If you corrected the problem by deleting the value of DhcpNodeType, you probably
changed it from Peer-Peer to Unknown.
<http://support.microsoft.com/kb/903267>

The Node Type value Unknown works fine in a network without a WINS server, and
will be treated as B-node or Broadcast.

Please read my articles, for your own peace of mind.
<http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html>
<http://nitecruzr.blogspot.com/2005/05/reading-ipconfig-and-diagnosing.html>
 
Back
Top