Share via

Unable to map a network drive using Windows 7?!

Anonymous
2013-01-24T00:39:42+00:00

Hello:

I'm having a problem connecting Window 7 to a NAS.  It used to work... with other OSes (XP and W2K).  But it will NOT with Windows 7.

At any rate, when I either try to map a network drive from Explorer, or just enter the UNC in the Address Bar in Explorer, I get a very generic “Windows cannot access” error with a code of “0x80004005 unspecified error”.

So after searching on that error across the web, here are some steps I have taken:

  • Turned the firewall off
  • Ensured MS Client for Networks is installed on my NIC

-  Verified File and Printer Sharing is enabled

  • Made sure the Server, TCPI/IP NetBIOS Helper, and Workstation services were running
  • Enabled NetBIOS over TCP/IP
  • Changed the Lanman authentication to the most unsecure option

None of that helped. 

I have Cygwin installed on the box though.  So I ran smbclient -L \\server\share and it give me the finger due to SMB signing required on the server side.  Hmmm... I'm on to something here.

After some poking around I turn signing off with this:  smbclient -L -S off \\server\share

and it works!!!  I can see all the directories and files on the NAS.

In turn, I go back to Windows and remove mrxsmb20 from lanmanworkstation's dependencies, set mrxsmb20 to disabled, and reboot the workstation.  Yet, when it comes back up, I still experience the same problem. 

Since I was able to navigate the NAS with the smbclient, I know my network and integration is set up correctly.  Mapping a drive in Windows is still problematic though.  So I go back to my original question:  what does it takes for Windows to map a drive?  Meaning what are the settings, services, etc., which are dependent upon the mapping procedure?

Windows for home | Previous Windows versions | Internet and connectivity

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

9 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2013-01-25T15:15:40+00:00

    Pinging has never been an issue. 

    Mapping by IP or name has always yielded the same results.

    Thanks!

    0 comments
  2. Anonymous
    2013-01-25T03:54:59+00:00

    It's interesting that it's changed from  "Windows cannot access” to "network path was not found."

    Can you ping the NAS?  What happens now if you try to map by IP address?

    0 comments
  3. Anonymous
    2013-01-24T22:51:54+00:00

    Thanks for the reply...

    > What happens if you try mapping the NAS in an elevated

    > command prompt?  Same error or something different?

    System error 53 has occurred.  The network path was not found.

    > I suggest resetting both winsock and the tcp/ip stack.

    Doing this cleared the IP address out of the adapter.  Grrrr.  Once I added that information back in, I got this:

    Windows cannot access \\server\share.   Check the spelling of the name.  Otherwise there might be a problem with your network.

    Error code 0x80070035:  The network path was not found.

    Well, this time, the error code is different.  In my OP the code was 0x80004005.  Now, it's 0x80070035.  So, there's still some work to do!?

    Any additional suggestions?

    0 comments
  4. Anonymous
    2013-01-24T03:14:38+00:00

    Great job on troubleshooting and describing!

    A couple of thoughts

    • What happens if you try mapping the NAS in an elevated command prompt?  Same error or something different?
    • I suggest resetting both winsock and the tcp/ip stack. See

    Windows 7 - Resetting Winsock Protocol

    http://www.sevenforums.com/network-sharing/124380-resetting-winsock-protocol.html

    And

    How to reset Internet Protocol (TCP/IP)

    http://support.microsoft.com/kb/299357?wa=wsignin1.0

    0 comments