Page 1 of 1
XP Networking

Posted:
Fri Oct 08, 2004 11:31 am
by kratak
ok, 2 machines both running XP Pro. Both with files shared to each other. Both PC's can see each other on the workgroup. However PC1 cannot access PC2 via the workgroup. PC2 can access PC1 via the workgroup. The error message is
\\PC2 is not accessible. You might not have permission to use this network resource. Contact the administrator of the server to find out if you have access permissions
However if i use PC1 and type //machineIP/shareName I get access to the share that is available
Any reasons why i cant do the same and see all the shares via the workgroup?

Posted:
Fri Oct 08, 2004 1:44 pm
by Geekgirl
Check your TCP/IP settings making sure they are the same on both machines.
I was having difficulty transferring files untill I changed the settings, instead of obtaining an IP automatically I had to put the settings in manually.

Posted:
Fri Oct 08, 2004 3:58 pm
by kratak
Hi
We are using the same subnet mask and gateway address. Are IP address's are differernt but thats it. All of which was done statically.

Posted:
Fri Oct 08, 2004 5:11 pm
by Restek
Are you using any firewalls? Are you both in the same subnet? Are you using netbios over tcp/ip on both machines (as opposed to basic netbios)?

Posted:
Fri Oct 08, 2004 5:21 pm
by kratak

Posted:
Sat Oct 09, 2004 12:34 am
by brad
Try turning off the Windows Firewall.
brad

Posted:
Sun Oct 10, 2004 6:35 pm
by kratak

Posted:
Sun Oct 10, 2004 8:17 pm
by Restek

Posted:
Sun Oct 10, 2004 8:53 pm
by kratak
Hi
the NIC is a trusted device via IP address of each machine on Norton's firewall. Both are static address's. I dont see a way of adding mac address's on the firewall
Sorry that i missed your question. But to confirm we are on the same subnet
Thanks for all the suggestions so far. It's really bugging me. I cant access his computer via the workgroup but i can map individual shares!!


Posted:
Mon Oct 11, 2004 3:51 pm
by kratak
hI
Just thought i would say thanks for all the help, ive solved the problem!
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Lsa DWORD KEY "restrictanonymous" = 0
My mates machine was set to 1 instead of 0. It works now, not sure how that got changed!
Thanks