Hi, I have a three pc's network using XP Pro (A, B and C). Computers A & B can see C but cannot access it when I tried to click on the workgroup, it says that it is not accessible. On the C computer, I cannot see the workgroup at all, not even itself. What can cause computer C to be not accessible. I turned off the firewall on all computers but still not showing. Need help. Thank you in advance.

Assuming that C has the same workgroup name as the other two computers and that sharing of one of its disks or folders is enabled, you should check to see if the network protocols installed on C are the same as on A and B. Have you tried using the Network Setup Wizard accessible from the Openning menu of the XP CD?

The workgroup name for all 3 computers are the same. I did share the drive for the C computer. I have not tried using the Network Setup Wizard. Do I still need to do this even though I will not be connecting to the internet on this computer.

If you go into your Network Properties make sure IPX SPX is in the list. I had a very similar problem. Regards Stealth

The Network Setup wizard isn't the same as the Network Connection Wizard. Put your XP CD in the drive, let it autostart or run setup. Choose [additional tasks]. Choose [Set up home or small buiness network] Follow the wizard and repeat the process on all three machines if necessary (making sure the correct workgroup name is input each time. :-)

I've had the same problem. Persistently over the past year. Three of my pcs could access each other fine, but although they could see the fourth, they sometimes couldn't access it. Running the NETWORK SETUP WIZARD again usually made the problem worse. Instead, I installed and uninstalled XP 3 or 4 times in a night to fix it. Last night I followed this link http://support.microsoft.com/?kbid=318030 and yes, on my three good pcs ADVANCED TCP/IP SETTINGS >> WINS >> NetBIOS SETTING was set to ENABLE NetBIOS OVER TCP/IP but the dodgy pc wasn’t. This caused the unreliable connection and the initial breakdown, but resetting to ENABLE still didn’t restore the connection. A writer in another forum mentioned finding a ghost IP address deep down somewhere, and it seemed to conflict with an actual address. I changed the IP address of my problem pc to a number not used before, from “192.168.0.2” to “192.168.0.5” with instant, beautiful success. “192.168.0.2” is not in use anywhere, as far as I can see, but it won’t work anymore. I guess running the NETWORK SETUP WIZARD a dozen times to fix the initial problem isn't a good idea.