Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 796
  • Last Modified:

Mapping to a specific network drive does not work from some computers

We are experiencing an issue mapping to a shared folder. We are in domain environment.
So far we have come accross three computers that refuse to map to a particular computer, but have no issues with mapping to other computers.
In the past they connected fine, but have recently stopped working.

Steps to troubleshoot that have been taken already:
- Verified DNS resolves properly and that the drive can be pinged by name and IP
- Checked File share and folder permissions.
- Logged in as domain admin and still could not map the drive
- Tried net use from command prompt, but got error 53
- Modified Nic TcP/IP DNS settings to append domain settings
- Changed speed/duplex from auto to 100/full and 100/half.
- Uninstalled and Re-installed File and Printer Sharing
- Left and Re-joined the Domain
- Connected via wire instead of wirless
- Tried connecting using different user accounts with no luck.
- Created a new shared folder with permissions to EVERYONE but still no luck on the trouble computers.
0
xsol05
Asked:
xsol05
  • 4
  • 3
1 Solution
 
lnkevinCommented:
What error message pop up when mapping failure?
Is DHCP enable in your environment especially in the network that these two computers connected?

One suggestion is you want to check "Enable NetBios over TCP/IP" in tcp/ip properties

K
0
 
xsol05Author Commented:
The Error message when trying from Windows is
"The Network Path xxxxx could not be found"
In a Command Prompt:
"System error 53 has occurred.
The network path was not found."

I justed Enabled the NetBios over TCP/IP and had no luck.
Have tried mapping to both the IP and the server name.

It is DHCP, the server is on a static IP.
0
 
lnkevinCommented:
justed Enabled the NetBios over TCP/IP and had no luck....
Do both on client and server

Did you try to map with server ip address instead of computer name?
What OS is client running?

K

0
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

 
xsol05Author Commented:
Enabling that on server side corrected the problem.

Could you explain why that corrects the problem and also why it works while in the Default mode from most computers but not from others.

All PCs are on XP Pro-SP2.
0
 
lnkevinCommented:
If you don't have Win server or your win server does not work properly, enable NetBios over TCP/IP will solve your name resolution in Windows network environment.

K

0
 
xsol05Author Commented:
We are in a DNS environment. The issue was not name resolution, the name resolved fine if you pinged it.
What else would cause the server to be unmapable from a handful of computers?
0
 
lnkevinCommented:
Do you have a mix mode environment (W3K, XP, vista...)? or some workgroup mixing with domain client?
If yes, you need to have Win server to resolve name in mix mode in addition of DNS (resolve name and IP address).

K

0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get 10% Off Your First Squarespace Website

Ready to showcase your work, publish content or promote your business online? With Squarespace’s award-winning templates and 24/7 customer service, getting started is simple. Head to Squarespace.com and use offer code ‘EXPERTS’ to get 10% off your first purchase.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now