Difference between revisions of "The list of servers for this workgroup is not currently available"
Jump to navigation
Jump to search
(a solution!) |
(corrected solution; more description of symptom; better organization) |
||
| 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]]. |
| + | ==Symptoms== | ||
| + | This error may occur in conjunction with: | ||
| + | * [[System error 6118]] | ||
| + | * [[Network Neighborhood]] not available | ||
| + | * Can't connect to [[Windows domain]] (times out); other machines remain connected to it | ||
| + | * [[TCP/IP]] (web, ping) seems to be working fine. | ||
==Solutions== | ==Solutions== | ||
| − | * ''' | + | * '''Solution''': Deactivate [[McAfee Internet Security]] -- firewall was blocking access to [[Windows Network]] but not [[TCP/IP]]. Network Neighborhood instantly begins working, no reboot required. --[[User:Woozle|Woozle]] 20:29, 7 September 2010 (UTC) |
| − | |||
==Leads== | ==Leads== | ||
Possible leads for solving it, if the above doesn't work: | Possible leads for solving it, if the above doesn't work: | ||
Latest revision as of 00:42, 7 October 2010
About
"The list of servers for this workgroup is not currently available." is an error message in Microsoft Windows XP.
Symptoms
This error may occur in conjunction with:
- System error 6118
- Network Neighborhood not available
- Can't connect to Windows domain (times out); other machines remain connected to it
- TCP/IP (web, ping) seems to be working fine.
Solutions
- Solution: Deactivate McAfee Internet Security -- firewall was blocking access to Windows Network but not TCP/IP. 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.)
- suggests that problem is due to not having a master browser; force browser election by restarting all systems.
- 2008-04-21 The Magic of Life (blog)