If you’re in a hurry, skip down to the part that says “interesting part starts here”.
Here’s what happened.
I installed Cisco Systems VPN Client Version 4.6.02.011 on an IBM T40p laptop running Windows XP. The software wasn’t working right on my laptop, so I uninstalled it.
Things were back to normal then, except that suddenly I couldn’t connect to other Windows machines by name (that is, NetBIOS name). And other computers couldn’t connect to my laptop by name. I could connect via IP address either way no problem.
After digging through everything I could think of, I issued an “ipconfig /all” command and noticed that the “Node type” was set to “peer-peer”. That didn’t sound good, and I had never seen it before. A quick google search later turned up this at a site called TechBuilder:
- interesting part starts here -
C:\>ipconfig /all
Host Name . . . : myhostname
Primary Dns Suffix. . .:
Node Type . . .: peer-peer <- uh oh
“With Windows XP, take note of the Node Type. The error message “You might not have permission to use this network resource” will occur if the Node Type is set as “Peer-Peer.” A Node Type of Mixed, Hybrid or Unknown is okay.”
Bingo! Exactly the problem.
TechBuilder’s suggested solution involves a registry edit:
“To set the Node Type to Unknown (recommended), open the registry editor and go to:
HKEY_LOCAL_MACHINE/System/CurrentControlSet/Services/Netbt/Parameters
and delete these values if they’re present:
NodeType and DhcpNodeType. (You must reboot for changes to take effect).”
Sure enough, there was a “DhcpNodeType” entry setting my node type to “2″. Deleting this entry and rebooting fixed the problem.
Thanks TechBuilder!
0 Responses to “Fixing Windows Name Resolution Problem After Failed Cisco VPN Install”