Computer name lookup not working, only IP addresses

[Bob]

This is a problem that recently popped up on my 3 PC
network. For some reason, my laptop can no longer
connect to shared resources using computer name. It will
only work with IP addresses. For example, \\athlon\c
will not work, but \\192.168.1.108 (athlon's IP) DOES
work. NetBIOS over TCP/IP is enabled on all machines,
and they are all part of the same workgroup. The two
desktops can still talk with computer names, but I cannot
think of why the laptop does.

Thanks

 

[Steve Winograd [MVP]]

This is a problem that recently popped up on my 3 PC
network. For some reason, my laptop can no longer
connect to shared resources using computer name. It will
only work with IP addresses. For example, \\athlon\c
will not work, but \\192.168.1.108 (athlon's IP) DOES
work. NetBIOS over TCP/IP is enabled on all machines,
and they are all part of the same workgroup. The two
desktops can still talk with computer names, but I cannot
think of why the laptop does.

Thanks

Run "ipconfig /all" and look at the "Node Type" at the beginning of
the output. If it says "Peer-to-Peer" (which should actually be
"Point-to-Point") that's the problem. It means that the computer only
uses a WINS server, which isn't available on a peer-to-peer network
for NetBIOS name resolution.

If that's the case, run the registry editor, open this key:

HLM\System\CurrentControlSet\Services\Netbt\Parameters

and delete these values if they're present:

NodeType
DhcpNodeType

Reboot, then try network access again.

If that doesn't fix it, open that registry key again, create a DWORD
value called "NodeType", and set it to 1 for "Broadcast" or 4 for
"Mixed".

For details, see these Microsoft Knowledge Base articles:

Default Node Type for Microsoft Clients
http://support.microsoft.com/default.aspx?scid=kb;en-us;160177

TCP/IP and NBT Configuration Parameters for Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;314053
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com

 

[Guest]

I ran nbtstat -r and -R on the problem computer. It does not resolve any other names besides itself

 

[Guest]

I tried that fix. The reg values mentioned were not present, and I added the NodeType = 1 DWORD. The "node type" still shows as "Unknown" when doing a ipconfig /all (it did before and after adding the reg key.) One different thing I noticed on the problem computer is "IP Routing Enabled : Yes" and "WINS Proxy Enabled = Yes" in the ipconfig output. The other PC's show NO. Both desktops can talk to each other and the laptop using names, but laptop still cannot. Just IP's. I cannot view workgroup computers either. Gives a "list of servers for this workgroup not currently avail."

Im out of ideas... any one else have any??

Thanks

bob
----- Steve Winograd [MVP] wrote: -----

This is a problem that recently popped up on my 3 PC
network. For some reason, my laptop can no longer
connect to shared resources using computer name. It will
only work with IP addresses. For example, \\athlon\c
will not work, but \\192.168.1.108 (athlon's IP) DOES
work. NetBIOS over TCP/IP is enabled on all machines,
and they are all part of the same workgroup. The two
desktops can still talk with computer names, but I cannot
think of why the laptop does.

Run "ipconfig /all" and look at the "Node Type" at the beginning of
the output. If it says "Peer-to-Peer" (which should actually be
"Point-to-Point") that's the problem. It means that the computer only
uses a WINS server, which isn't available on a peer-to-peer network
for NetBIOS name resolution.

If that's the case, run the registry editor, open this key:

HLM\System\CurrentControlSet\Services\Netbt\Parameters

and delete these values if they're present:

NodeType
DhcpNodeType

Reboot, then try network access again.

If that doesn't fix it, open that registry key again, create a DWORD
value called "NodeType", and set it to 1 for "Broadcast" or 4 for
"Mixed".

For details, see these Microsoft Knowledge Base articles:

Default Node Type for Microsoft Clients
http://support.microsoft.com/default.aspx?scid=kb;en-us;160177

TCP/IP and NBT Configuration Parameters for Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;314053
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com

 

[Guest]

-----Original Message-----

Run "ipconfig /all" and look at the "Node Type" at the beginning of
the output. If it says "Peer-to-Peer" (which should actually be
"Point-to-Point") that's the problem. It means that the computer only
uses a WINS server, which isn't available on a peer-to- peer network
for NetBIOS name resolution.

If that's the case, run the registry editor, open this key:

HLM\System\CurrentControlSet\Services\Netbt\Parameters

and delete these values if they're present:

NodeType
DhcpNodeType

Reboot, then try network access again.

If that doesn't fix it, open that registry key again, create a DWORD
value called "NodeType", and set it to 1 for "Broadcast" or 4 for
"Mixed".

For details, see these Microsoft Knowledge Base articles:

Default Node Type for Microsoft Clients
http://support.microsoft.com/default.aspx?scid=kb;en- us;160177

TCP/IP and NBT Configuration Parameters for Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en- us;314053
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com
.