\\computername 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 network path can
Posted on 2009-05-18
Domain running Windows Server 2003 Standard and 15 Win XP clients. Had a seperate laptop that was not on domain running an application perfectly fine for many years. Owner decides that he wants to now use this app on 2 other PCs, but does not want to buy a fourth license to put data on server, instead two PC will access the data from a shared folder on the laptop.
Join laptop to domain, can ping laptop from PC1, PC2 and DC. However, cannot map Shared drive or view shared drive(s) from PC1 or PC2. DC can see just fine.
-Have enabled and disabled Netbios on all three PCs (previous settings was "Default").
-Disabled Windows Firewall from all three PCs
-Re-enabled Windows Firewall from all three PCs
-Uninstalled AV (have not yet reinstalled)
-reset TCP/IP (netsh int ip reset resetlog.txt)
-reset winsock (netsh winsock reset)
-tried logging in as different users, including those that are members of domain admins group, with same results.
-check sharing permission and folder permissions on Laptop, added each specific user, added user groups, added "Everyone" and removed everything and tried various combinations of each, still same result.
-the only thing I have not yet tried is removing the laptop from domain, rename and then rejoin it to domain.
I get the above error when I try to double click on the laptop when browsing through My Network Places.
When going run > \\unc
I get "Network path cannot be found"
cmd > net use Z: \\unc\share
Returns: Error code 53
HOWEVER, I can map the shared drive on the Laptop and the server using the same methods above, it's only these two desktops that cannot map the shared folder. I have not yet tried any additional PCs.
NSLOOKUP resolves somewhat correctly, I do have an interesting error when running against IP address, (says "server unknown") but resolves correctly.
I have also verified the DNS records manually, checked to see that stale records have been purged. Any other ideas?