The list of servers for this workgroup is not currently available

This message…

the list of servers for this workgroup is not currently available

must be one of the most annoying messages in Windows you could imagine. You have two computers on the same LAN, you can ping, so you know that the connections are right, but if you want to access the files on a share of the other computer you get this message without any hint what might be the cause.

I could try to explain why you just have to set this registry entry


to 1 (instead of the 8 it was set to on two of my computers), but you are probably in a hurry to just access the other file and are not interested in research. If you are interested in the why then continue searching the web. I did and found my answer.

But as I said, you are most likely in a hurry, so set that registry value and reboot, and if you are as lucky as I am then you will be able to see the other machine(s) on the LAN and share happily.

  • You might meant “NodeType”…

  • Stone Taggart

    um… you … you didn’t LIST A REGISTRY ENTRY… you only listed a directory WITHIN the registry. There are TWELVE KEYS in there. Which one were you supposedly setting to ‘1’?

  • I guess I was in a hurry. Here is the info that should explain it all:

    This parameter specifies the NetBIOS over TCP/IP (NetBT) node type. The node type specified by the entry NodeType, if valid, overrides the value of this entry. If neither this entry nor NodeType exist in the registry, and there are no WINS servers configured on the network, then NetBT uses B-node name resolution. If there is at least one WINS server available, NetBT uses H-node name resolution.

    Meaning of Value

    1 = B-node. NetBT uses IP broadcast messages to register and resolve IP addresses from NetBIOS names.

    2 = P-node. NetBT uses point-to-point communication with a NetBIOS name server (in Windows Server 2003–based networks, this is the WINS server) to register and resolve IP addresses from NetBIOS names.

    4 = M-node. NetBT uses a mix of B-node and P-node to register and resolve NetBIOS names. M-node first uses broadcast resolution (B-node), then if necessary, uses a server query (P-node).

    8 = H-node. NetBT uses a hybrid of B-node and P-node. An H-node client always directly queries a name server first and then uses broadcasts only if the direct query fails.

  • Kelvin

    Hurray! After hours of trying various offered solutions to this problem (reboot after reboot after reboot after changing various other things), this simple trick immediately took care of it. Thanks for posting it!

  • nice trick 😉 thanks!

  • jordan

    great tip

  • Michael Selph

    I have many hours trying to fix this problem. Also used up a lot of searching the web. But this tip worked. Thanks

  • Paul

    I think I found this tip months ago and it worked .. until today. Two XP machines not talking. Any even deeper ideas?

  • Mike

    Found this thru Google….worked for me too. I’ve spent two evenings fumbling through settings trying to figure out why two old Dells couldn’t talk to each other….this fixed it in two minutes. Thanks!

  • anton

    i dont have DhcpNodeType in
    what do i do?

  • Add a DWORD parameter to the key and give it the value 1 (Right-click in the empty space and select New)

  • anton

    i created it,and it isnt working :/

  • Mike

    Dude, you are the MAN! I’ve spent days trying to figure out why one of my three systems couldn’t find hosts on the LAN. This fixed it. *thank you*

  • Ron

    After months of futile attempts to communicate with the rest of my network, brought on by an sp3 upgrade (dame u Microsoft . . . lol), I finally asked the right question “the list of servers for this workgroup is not currently available” found your response and fixed my problem. Thanks!

  • Michael

    Thank You, Thank You

    You can’t believe what a pain in ___ this has been to trouble shoot. I work on two computers side by side (portable and desktop) and need to constantly syncronize files. When I lost connectivity las week, I was high and dry.

    This fixed it. Google search term worked as Ron says above

  • YellowShark

    christ what a stupid problem and stupid solution to have to implement. but THANKS!!! serious. real serious. this fixed my crap. in case others have same problem, here’s a few more deets:

    2 win xp pro systems, both have passwords assigned to guest accts
    1 xp home system. couldn’t access workgroup, couldn’t access shares. the 2 xp pro systems had zero problems seeing and accessing each other. the xp home machine could see the others, but could not access them. the other machines coul see the xp home system, but also could not access it.

    this made things work, for that i am extremely grateful. blogs rule! share your knowledge!

  • Curt

    after scouring the web after weeks of struggling with this problem I found this blog. And I might add that it worked for me too

  • Alan Hunter

    I’ll join the chorus! After months of frustration and trying all the exotic solutions, to find one so simple, that WORKS is gratifying.

  • Daemon

    I was so hoping this would work for me, but it didn’t. I didn’t have that registry entry so I created it as described (and double checked it) and set it to 1. No change. Sigh, I guess I have more searching to do.

  • ather1232002

    I have a problem, I run a network of 10 PCs with windows XP. I have turned of my firewall. They can ping each other, they can access each other by using run. e.g: \\ or \\computername. but no computer shows in my network places. and some time shows this error
    “workgroup is not accessible. you might not have permission to use ths network resource. Contact the administrator of this server to find out if you have access permissions. The list of servers for this workgroup is not currently available.
    Any one tell me the solution….

  • One other cause for this I noticed is a disabled guest account.

  • Mike

    Hey Merlin, Worked for me on one of my Networks. But on anotherone no dice.

    Was the disabled guest account on the workstations or on the server?

    I am running a domain controller and this has been going on for over two years. Sometimes it is working but most of the time it is not.

  • Mike

    Just made some headway on the issue but am still totallay baffled as to why.

    I just cured the problem by disabling the second NIC….??????

    It is too late in the day to try to figure this one out. I will work on it more tomorrow.

  • Hi Mike, don’t we hate those ‘sometimes’-problems?
    Guest account was on the server.
    I just had another annoying problem. Replaced on HP printer with a newer, better, bigger one. The old one was shared and I could print from other machines no problem. The new one showed up as shared but when the other machine tried to print, everything appeared to work but nothing came out of the printer. Long sessions with HP – nothing. Then the second computer was replaced by a Mac (!) and that one has no problems printing to that printer – funny, eh?

  • Hi Merlin, i think i’ve figured mine, it was eset antivirus that disable system sharing, so i’ve re-enabled it.

  • Cool – and thanks for sharing. There are quite a few that find this post and it can surely help somebody.

  • Ken

    How do you enable that again.. dont seem to be able to find “system sharing” to enable that again..

  • Larry

    Wow. Have no idea how it changed to a “2”. Set to “1”. Great! Thanks much!

  • Mike

    I am having the same issue. I have a number of computers on the network.
    2 XP, 2 Linux, HP-UX and, when turned on, a laptop (Windows 7 or Linux)
    and a netbook and an HP “PhotoSmart” with the last three being wireless and
    the others wired LAN through a hub. The router is contained within the
    DSL modem.

    For some time things were working O.K. I could “see” the other computers
    from any other computer. Then things abruptly changed and no longer
    work. I can ping between any of the computers. I changed the DhcpNodeType on
    one XP computer, re-booted it and one Linux desktop with no apparent change.
    One additional point: the Linux desktops, HP-UX unix and HP printer use
    static addresses. The rest are DHCP.

    Any ideas?


    Mike Stansberry

  • I get this error message that’s being reported by a specific dll within an application we use but the registry key you mention doesn’t see to be there. I’m guessing it could be different versions of Windows Server. Users get it in a terminal server session so would the problem be on the Terminal Server or could it be the Domain Controller or the SQL server that holds the databases the application connects to?

  • Kcramo

    Hi there! you didn’t LIST A REGISTRY ENTRY,  listed only a directory WITHIN the registry. There are TWELVE KEYS in there. Which one were you supposedly setting to ‘1’?Please Help!

  • Timothy Roussel

    Check the Computer Browser service….usually the culprit.