Posted: 6/21/2006 11:08:17 AM EDT
|
I have 2 computers running XP on a home network, I can access comp 1 from comp 2, but not comp 2 from comp 1. I have the permissions all set correctly, firewalls off, and when I try to access comp 2 from comp 1, It shows up on the network(MSHOME), but when I click to open it, I get the message that "comp 2 could not be accessed you might not have permission to use the network resource, contact admin" I have tried everything, got on the knowledge base, short of a firewall that I don't know about running in the background, I don't know what to do. Any advice would be appreciated. 
|
|
Assuming both computers are running some form of Xp (home,pro,MC): Make sure both computers have the same workgroup name. Make sure both have the same user name and password, or that you add the user name and password of each computer to the other via the control panels user area. Also on both computers make sure you've actually enabled sharing, allowed it through Windows firewall (the "exceptions" tab), and have a folder shared. You might have to try dropping the firewall entirely just for testing; I've seen it cause problems between varying versions of Windows or varying service pack levels. I've seen some routers/switches that have issues with Windows file sharing and TCP/IP (your networking protocol). If you still have issues after all this, try adding the "NWLINK IPX/SPX Netbios compatible protocol" to both computers, then reboot both of them. Sometimes this helps, but it's just a workaround, not a fix. Hope this helps. ETA: Damn my slow typing! |
Which key? I'm going to guess "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\LSA" and you set "restrictanonymous" to "0." You can also access these through Control Panel -> Administrative Tools -> Local Security Policy -> Local Policies -> Security Options. Find "Network access: Do not allow anonymous enumeration of SAM accounts and shares" and set to "Disable." |
say what
Thats the one, I also changed the restrictanonymoussam to a value of 0 as well, after a reboot the problem was fixed, best of luck. |