\\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

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?
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

fastbreaktechConnect With a Mentor Author Commented:
Ok, well never did find what the underlying problem was.  We ended up just moving the data to a new system and sharing it out that way, and reformatted the laptop.  Thanks to everyone for their help.
So PC1 and PC2 are on the domain correct?  Can they access the Laptop through \\ip address?  Is the server service started on the laptop in services.msc?  Do all 3 stations have "Client for microsoft networks" checked in local area connection properties?
Have you tried resting the Laptop computer account.Give this a try and let me know
The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

fastbreaktechAuthor Commented:
tried both IP and UNC, as well as My Network Places, and get the same issue each time.  I will check to see if the setting you mentioned is checked.  All services are running correctly.

I assume you mean resetting the computer account for the laptop in AD.  I did not as it was just joined, but I will try that next as well.

Thanks both, and I will let you know.
fastbreaktechAuthor Commented:
All system are on the domain, the laptop was preiosouly a stand-alone system that has recently been added to the domain.
"Clients for Microsoft Networks" was checked on PC1, PC2 and Laptop.

I reset the computer account for Laptop, still having the same issue.  I haven't renamed/readded yet, but I am thinking that might be the only other thing left.
What are your IP Addresses and Default Gateways on the machines?
Unshare the folder, share it out again, re-add groups and permissions
fastbreaktechAuthor Commented:
The IP scheme is correct, all systems are configured for dynamic and server ihas DHCP configured and running.  I can ping the laptop using IP, shortname and FQDN, and NSLOOKUP returns the correct values.

I can unshare the folder, but the problem is it won't even show the shares available on the system itself.  RUN > \\computername  //or// RUN > \\computername.domain.int  //or// RUN > \\192.X.X.X  all say the network path cannot be found.  Now, I can view the shares from the server, as well as from the laptop itself (i.e. RUN > \\
What OS is on the Boxes? XP?

With the share created what do you see on the offending box when you type in 'Net Share' in a Command PRompt?
Silly Question But Have you tried it without Firewall protection?
fastbreaktechAuthor Commented:
All systems are running windows XP (except the server which is Windows 2003).

Not a silly question, but yes I have tried with on and off, then only thing I didn't do was try disabling the windows firewall from the command prompt (disabled from control panel)

I'll try that and let you know what net share reveals
fastbreaktechAuthor Commented:
Disabled firewall through control panel, still no good.
Disabled firewall from command line, still no good.
Net Share from command line shows the correct information (as far as the shares are concerned)
Removed laptop from domain, renamed laptop to something not already in AD, re-added to domain and have same issue.

I found that Symantec had been installed at one point, so I uninstalled all AntiVirus from the control panel, ran the Norton Removal tool, and confirmed in the registry that no traces of other AV (past or present) was there.  Yet, the problem still remains.

I am leaning towards performing a repair install, unless anyone else has an idea of what to check.
All Courses

From novice to tech pro — start learning today.