Troubleshooting networks: changing node type

Network cable

Last Friday at work I was determined to solve a problem that we’ve had since I arrived in May 2006. It was to do with our network: why could my colleague Steve connect to my PC but I couldn’t connect to his?

Why had it taken us until Friday last to get around to troubleshooting this problem? Because it wasn’t until then (eleven days before the public release of Microsoft Windows Vista) that Steve upgraded from Windows 2000 to XP, and as we share so much data between us it felt quite important to finally nail this problem.

We’d done the usual things:

  • Made sure that printer and file sharing was switched on
  • Checked firewall settings
  • Ensured that we were on the same workgroup

“That’s really odd,” I said. “Why can you see my PC and connect to it but I can’t see or connect to yours on the network?”

And then I remembered that I’d said that very same thing about my newly installed laptop back in the autumn and the problem had been to do with network node types. (Of course!)

Were we using two different (and presumably incompatible) node types? A quick trip to the Command Prompt (Start > Run…, then CMD) and ipconfig /all gave us the answer we needed: yes. Steve’s PC had “Peer to Peer” while mine said “Hybrid”.

Here’s what we did to change Steve’s PC to “Hybrid” which solved the problem:

Windows XP: Changing Network Node Type

If you want to explicitly configure the Node Type:

  1. Run the registry editor and open this key: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Netbt\Parameters
  2. Delete the DhcpNodeType value if it’s present.
  3. If the NodeType value isn’t present, create it using type: DWORD.
  4. Set NodeType to 1 (Broadcast), 4 (Mixed), or 8 (Hybrid).

For details, see these articles:

A quick reboot (or simply disable the “Local Area Connection” in Control Panel > Network Connections, and then re-enable it) and all was fixed.

(This post is as much for my own reference in the future as to help others.)


Wednesday 28 October 2009

This has just solved an issue I had with Windows 7 not showing my XP machine in its network folder.

Wednesday 27 January 2021

Microsoft has removed support documentation for XP, so I have amended the help articles bulleted-list.

Published by

Gareth Saunders

I’m Gareth J M Saunders, 52 years old, 6′ 4″, father of 3 boys (including twins). Enneagram type FOUR and introvert (INFP), I am a non-stipendiary priest in the Scottish Episcopal Church, I sing with the NYCGB alumni choir, play guitar, play mahjong, write, draw and laugh… Scrum master at Safeguard Global; latterly at Sky and Vision/Cegedim. Former web architect and agile project manager at the University of St Andrews and previously warden at Agnes Blackadder Hall.

19 thoughts on “Troubleshooting networks: changing node type”

  1. After searching the for a few hours I was glad I came to your small corner of the net. This post solved an issue I was having linking up a second computer to a NAS device (D-Link DNS-320 or ‘Sharescentre Pulse’). The first computer (HP G62) played ball but the second (HP G6) was having none of it. I ran ipconfig/all and found the node type was ‘peer-peer’ – not the most versatile setup I hear. After deleting said reg key, I restarted the second comp and ran ipconfig/all again to see it had changed to ‘hybrid’. Now both comps can communicate with the NAS device with ease. Ta much for the informative post!

  2. I have this issue and have been messing with it all day I have tried your fix, but my node type is still unknown. According to MS the NodeType=8 should override DHCPNodeType but I deleted that key anyway, it was recreated on reboot however.

  3. Three of my XP machines suddenly “disappeared” and I didn’t know why. Followed the advice above and now I can “see” them from the rest of my network which is Win 7 based. Most useful thank you.

  4. Thank you! I have been trying to get my one Windows 7 Computer to view all computers (XP and Windows 7) computers on my network for WEEKS now and This fix worked like a charm! Thank you!!!!!!! You have saved my sanity!!!!

  5. I am having the same issue however my node type is already Hybrid. I have one of my retail stores that are in a WorkGroup and my Windows 7 machines cant browse to shares on the XP machine by hostname \\machinename\share. I get an error saying the network name cannot be found. If I browse by IP address \\\share it works as normal. I have read hundreds of article with people having the same issue with multiple resolutions and none seem to work. Each one of my stores communicate with each other internally through a local router.
    Any help is appreciated


    1. I’m sorry, I don’t know what the issue might be — I simply posted what worked for me at the time. I’m now running one Windows 8 machine and a Windows 7 machine and everything’s working fine with that setup.

      Anyone else have an answer/suggestion?

      1. Angelo I have been having this issue for years now on one system that I have even reloaded and changed the NIC on. I think it is an oddball piece of software that causes it, but can’t prove it. Easiest solution have found to fix it is a windows system restore back to when it was working.

        1. Thank you all for the responses. Its with great pleasure to say that changing the DHCP Node type to “8” or “Hybrid” if you will in the registry did work. As it turned out I was focusing my efforts into the Win 7 terminal when in fact I had to make the change on the XP Main terminal in our store. Odd setup we have but I am glad its all working now. Thanks for the original post and all others..
          Take care

    2. Run these commands, it has worked for me.
      Some commands may hang for a few minutes which is fine, eventually it will go through.
      Just copy and paste it into a batch file named something like “Network_Reset.BAT” (without the quotes):
      arp -d *
      netsh winsock reset
      netsh winsock reset catalog
      netsh int ip reset Reset.LOG
      netsh int ipv4 reset Reset.LOG
      netsh int ipv6 reset Reset.LOG
      ipconfig /release
      ipconfig /release6
      ipconfig /flushdns
      ipconfig /registerdns
      ipconfig /renew
      ipconfig /renew6


  6. Yesssss, It solved my problem als well with Windows 10!!!

    I couldn’t connect my laptop via the name of the NAS, but it worked fine with the IP-adress. My wif’s laptap (identicat) worked well.

    This little thing solved that problem.
    (solving the browsing problem in ‘Network’ is the next thing 😉 to do)

    Many thanks,
    Eric Hoenderop
    The Netherlands

  7. Wow! This just fixed a client who still has a few XP clients running around his network. One (and only one) couldn’t see the server. Ran this little regedit tweak, and it’s reconnecting. What’s weird is the other XP machines are identical, and don’t need this fix. (yet?)

    BTW, as a twin-dad/geek myself, glad to meet another! (My twins: Christopher & Victoria, followed up by Robert then Rebecca.) Yes. Hands & heart full….

    ~Dan (in the colonies)

  8. Hi Guys,

    Just had to refresh some old Hp laptops for some XP based software…yes we are going backwards for a small project.

    2x laptops are working with windows 7/10 but switched to XP 32/64 and cant get network access. I get an ip address and able to ping pcs on the network but cant get to the network share. Also cant browse online.

    Cant get the software to work with windows 7 and above so XP is my only option. I know its not hardware since its works on a windows PE boot disk. I can browse when using Hirens!!! but cant in windows XP.


Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.