Cannot map network drives

One Windows XP (SP3) laptop cannot map network drives to any network system (server or workstation).

From Toolbar - Map Network Drives = A pop-up box appears stating "The mapped network drive could not be created because the follwing error has occurred: The request is not supported."

From Command Line Net Use = "System error 50 has occurred. The request is not supported."

From RUN type \\servername or \\IPAddress = "The request is not supported."


We can ping the servers by name and IP address. We can access the Internet. Email program works correctly.


System = Windows XP Pro SP3
Actions taken = 1. ran "repair" on NIC,    2. removed from domain and re-added,   3. removed from domain, renamed laptop, readded to domain.     4. Tested with user's profile and an admins profile. Same error regardless of actions taken.
ateecoAsked:
Who is Participating?
 
ateecoAuthor Commented:
Issue resolved -- Monday morning we performed a system restore to a date prior to the event. Had to log in with the local admin user account. The system restore renamed the laptop back to the previous name, so we removed it from the domain by adding it to "Workgroup". On the domain controller we recreated the computer account in the domain using the original laptop name. On the laptop we rebooted and rejoined the laptop to the domain utilizing the original computer name. The user was able to log in and access all shared folders and mapped drives.
0
 
shahzoorCommented:
Please check the time on remote server and your machine
disable auto update time
0
 
ateecoAuthor Commented:
Cannot disable the auto update time. The Internet Time tab is not available if your computer is a member of a domain. I apologize I did not mention the system is in a domain.
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!

 
DynamicNetworxCommented:
Sounds like there is a Global Policy that is preventing this.  Usually an erroneously applied policy or another admin limiting things causes this.  Try logging in as another user, preferable complete admin rights and see if it still happens.  Also, note that from a command prompt \\servername is not the complete command.  The command should be "net use f: \\servername\sharename" where f: is replaced with the desired drive letter.  Also, check in Windows Explorer and be sure you can connect from there, in the address bar type "\\servername\sharename".
0
 
ateecoAuthor Commented:
No changes to the Global Policy have been made. This is affecting only one machine. I did try using another user on the laptop with admin rights (see #4 above in Actions Taken). From the command prompt, I did use "net use...." (3rd paragraph above). I have tested using Windows Explorer, but could not connect from there (by using \\servername\share).
0
 
ateecoAuthor Commented:
When using Windows Explorer and typing \\servername\share -- the error is "Windows cannot find \\servername\share". Check the spelling and try again."   The spelling is correct and this happens no matter what server or workstation I try to connect to.
0
 
DynamicNetworxCommented:
Sounds like DNS issue.  Can you connect in Windows Explorer using the ip address? Ex "\\192.168.1.xxx\sharename"
If so, the network settings may be pointing to an invalid DNS server or it is just "broken".  If the latter is the case, you can workaround by editing the hosts file and adding a manual mapping for the IP and ServerName.
0
 
masnrockCommented:
TCP/IP and DNS are definitely working fine. The problem is only occurring trying to browse your local network. Try uninstalling and reinstalling Client for Microsoft Networks. (Depending on how bad your issue is, you may have to do the reinstall from a system folder on your PC.. I was tackling a somewhat similar issue on a server about a week ago)
0
 
ateecoAuthor Commented:
This comment was the solution to the issue. One other comment from a moderator was close, but all others were tried and submitted in the original comments.
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.

All Courses

From novice to tech pro — start learning today.