'Workgroup is not accessible' error when trying to get the list of available machines in workgroup

Hi all,

I have the following problem:
I have a small home network of 2 machines. I have a similar problem on both machines in my network - When I try to view the list of workgroup computers, I get the following error:
" Workgroup is not accessible. You might not have permission to use this 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"

I wnat to stress out that I get this error when I click in the "View Workgroup computers" link in "my network places". I know that a common problem is that after you get teh list of all computers you cannot access them, but I fail a step before that - I don't even get any list.

Some relevant details:
* Both computers run WinXP Pro. Computer A has SP2, and computer B has SP1
* On both computers I work with the same user (Administrator) and the same password
* Both computer have Zone alarm Pro installed (the home network is in the trusted zone, and the DSL connection on computer A is in the internet zone)
* on both computers windows Firewall is disabled.
* NetBios over TCP/IP was enabled on both computers
* Computer Browser service is running on both computers
* Both computers can ping each other
* Computer A is a Windows ICS gateway, and computer B browses the Web through computer B - This works fine.

I'd be gratefull (lifetime grateful) to the one who solves this for me. My next step is to re-install XP on both machines, and I would really like to aviod this.

Thank you all in advance,
Who is Participating?
georgecooldudeConnect With a Mentor Commented:
Double Check windows firewall (windows SP2 seems to turn it back on sometimes- at least with my machines). And also disable your zonealarm firewall just for testing. then you can enable it.

OK, now just go over and give your PC new IP's. Overwrite what is there. Trust me will work even if it seems dumb. ;-) I use it as a short cut alot. Make sure you run over it, it may seem like a waste of 5mins but I spent 10mins writing this out. ;-)

I am assuming PC1 is the master PC that connects to the internet. PC2 is going to be the slave PC.

PC 1.
IP =
Subnet =
Gateway = Empty

PC 2.
IP =
Subnet =
Gateway =  - the IP of your master PC.

Now they should ping and as long as internet connection sharing is enabled that should work too.

Go to control panel, system, double click the computer name tab. where it says "to rename this computer to join domain/workgroup" click the change tab. Make the workgroup as "WORKGROUP" without quotes.

Got to my network places, browse! bingo! you should see your PC's.
Debsyl99Connect With a Mentor Commented:
Make sure both machines have ip's in the same subnet ie,, then try adding your pc details in the lmhosts file as this may assist with resolution. Look for lmhosts.sam (sample file) here:


Edit it with notepad, add the following entry for PC2, add PC2's details on PC1


Save the hosts file as lmhosts (no extension - not .sam, not .txt)

See if that helps,

Deb :))
EladGanotAuthor Commented:
Thanks fo the quick reply :-)

I followed yoursuggestion, but for some reason I can now ping PC1 from PC2 but not vice versa. PC1 is and is the ICS gateway. PC2 was getting a dynamic IP so far. Both could ping each other. Now PC2 has a fixed IP, and can still ping PC1, but PC1 cannot ping it back...
Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

EladGanotAuthor Commented:
Also, I lost the ability to surf the web on PC2 (via PC1) :-(
Ok - undo the hosts file fix - it's obviously made things worse!!! Just delete the entries from both hosts files for the pc names and addresses, or delete the hosts files themselves. I'll have a look for further info (am a domain admin).

You'll get more posts no doubt, but have you tried disabling simple file sharing?

Deb :))
EladGanotAuthor Commented:
I'm willing to invest much more than 10 minutes in order to solve this :-)

Thanks for the advise. I can only continue worknig on this problem tomorrow, so I'll try that first thing tomorrow.

Deb - simple file sharing was disabled when the problem started. I enabled it since as part of my tries to find a solution, but I will disable it again tomorrow.

abu_deepConnect With a Mentor Commented:
it seems that DNS / WINS issues so here is what the greatest  "lrmoore" post in a question similar to yours…..

Troubleshooting the Microsoft Computer Browser Service



Problems with workgroup networking in XP:

Problems seeing workgroups when connected to a router:

How to Write an LMHOSTS File for Domain Validation and Other Name Resolution Issues

Windows 2000 server with Active Directory does'nt use NETBIOS for name resolution.

Windows 2000 DNS - Diagnosing Name Resolution Problems
FQDN = Fully Qualified Domain Name

Windows 2000 DNS - Solving other common DNS problems

Ping Utility Takes a Long Time to Return Results with NetBIOS Name

NetBIOS over TCP/IP Name Resolution and WINS

EladGanotAuthor Commented:
Hi again,

Tried georgecooldude's advise, and it solved the original problem I had. I can now see both computers from each other, can ping them, browse theie files etc. (The network is set up as in georgecooldude's post).

The problem now, is that PC2 cannot surf the web via PC1 anymore :-(
When I look at the network connections of PC2, I see the Internet connection on PC1 as available and connecterd, but when I try to use any web application I fail.

Any ideas?

Thanks again,
EladGanotAuthor Commented:
Sorry - ICS problem was due to bad ZA settings. Everything works fine now.

Thanks you all!

Glad your problem is fixed.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.