Difference between revisions of "The list of servers for this workgroup is not currently available"

from HTYP, the free directory anyone can edit if they can prove to me that they're not a spambot
Jump to navigation Jump to search
(another link)
(a solution!)
Line 1: Line 1:
 
==About==
 
==About==
[[category:error messages]]"[[The list of servers for this workgroup is not currently available]]." is an [[error message]] in [[Microsoft Windows XP]].
+
[[category:error messages]]"[[The list of servers for this workgroup is not currently available]]." is an [[error message]] in [[Microsoft Windows XP]]. It may occur in conjunction with [[System error 6118]].
 
+
==Solutions==
Possible leads for solving it:
+
* '''Symptoms''': Internet works fine, can ping other servers on LAN but can't browse or connect to them for Windows filesharing ([[Network Neighborhood]]).
 +
** '''Solution''': Turn off [[McAfee fierwall]]. Network Neighborhood instantly begins working, no reboot required. --[[User:Woozle|Woozle]] 20:29, 7 September 2010 (UTC)
 +
==Leads==
 +
Possible leads for solving it, if the above doesn't work:
 
* '''2005-07-04''' [http://forums.practicallynetworked.com/showthread.php?t=5648 Practically Networked] (forum)
 
* '''2005-07-04''' [http://forums.practicallynetworked.com/showthread.php?t=5648 Practically Networked] (forum)
 
** suggests that problem is due to not having a master browser; force browser election by restarting all systems.
 
** suggests that problem is due to not having a master browser; force browser election by restarting all systems.

Revision as of 20:29, 7 September 2010

About

"The list of servers for this workgroup is not currently available." is an error message in Microsoft Windows XP. It may occur in conjunction with System error 6118.

Solutions

  • Symptoms: Internet works fine, can ping other servers on LAN but can't browse or connect to them for Windows filesharing (Network Neighborhood).
    • Solution: Turn off McAfee fierwall. Network Neighborhood instantly begins working, no reboot required. --Woozle 20:29, 7 September 2010 (UTC)

Leads

Possible leads for solving it, if the above doesn't work:

  • 2005-07-04 Practically Networked (forum)
    • suggests that problem is due to not having a master browser; force browser election by restarting all systems.
      • There used to be other ways to force a browser election, but apparently it's more difficult in NT-based systems.
      • Samba may have a way to do it. (Just restarting Samba should, but doesn't always.)
  • 2008-04-21 The Magic of Life (blog)