<workgroup> is not accessible problem

**rdrnnr** · 02-01-09 at 12:27 PM

i got 3 computers connected on my home network 1 runs on vista, the other 2 on xp let's call them v1, x1 and x2

i got no problems with v1 & x1, both can access workgroup, see and read/write files from/to the other two computers, but when i try to access workgroup using x2 i get

workgroup is not accessible - you might not have permission to use this network resource - contact adiminstrator - device is not functioning (or) list of servers not currently available

so basically x2 is seen and can be accessed but can't see or access the other two

any ideas how to fix this

update

when i'm on x2 and type \\x2 i cant access shared folders (i can see them) and when i try \\x2.ip i get "windows cant find x2.ip, you might not have permissions", now that's weird

and x1 and x2 cant ping each other

lancer672 · 02-01-09 at 12:56 PM

I have a few machines around the house, 2 Macs, a couple XP machines, a Vista/Windows 7 machine. A couple of them I use just testing or servers, whatever it is I need to play with. So in other words I format a lot, from time to time I get that problem where everything seems right and I can't get access to a machine through Workgroups. Usually my problem has always been that I over look running network setup and turning on File Sharing. I always feel silly after realizing that I have forgotten to do that, yet once again.

I am curious to your previous solution of needing to do some registry fixes, I will will pay attention to this thread to see what comes of the solution since Workgroup problems happen more then people think.

**rdrnnr** · 02-02-09 at 04:56 AM

after a night spent on tryin to solve this i think that it's worse than i thought, so added an update

hsyeow · 02-02-09 at 07:33 PM

Google a bit and found a thread with problem exactly like yours.

Code: Select All

http://www.pctools.com/forum/showthread.php?t=33684&page=2

Look for post #12 as most people reported success with it. If that doesn't, try post #14.

**rdrnnr** · 02-03-09 at 02:21 AM

as always solutions that work for most ppl don't work 4me. I guess i'm not most ppl.
But I found a solution, when all failed I did it the hard way and reinstalled tcp/ip protocol, i guess winsocks library and/or tcp/ip stack were corrupted