10:02 - Friday, 18 April 2014

Windows 8 – Mapping Network Drive (NAS)

#Topics: windows 8 synology mapping network drive,connect network drive windows 8,synology windows 8 mappen,synology windows 8 user mapping,windows 8 map to synology drive

This question has been asked throughout the web, but I am simply not able to get it working.

I am Running Windows 8 Pro (x64), when I connect to the office network, I can connect to all network shares except the ones that is on our (NAS).

As soon as I boot into Windows 7, I am able to connect.

So far I have tried the following:

  1. http://support.microsoft.com/kb/2686098
  2. http://help.unc.edu/help/connecting-to-nas-with-windows-8/
  3. http://social.technet.microsoft.com/Forums/en/w7itpronetworking/thread/c1d2e480-65e8-41ad-b7a4-73d4ba3ca09d
  4. Windows 8 Pro NAS not recognized? (tried all suggestions)

All of the above with no success.

I also tried the net use command, to see if it might return additional info, but i get Error 53

net use k: \omsmds001System error 53 has occurred.The network path was not found.


net use k: \ error 53 has occurred.The network path was not found.

When i ping the device i get no response

When i try and browse the network location, i get an error:

Windows Cannot access \omsmds001Error Code: 0x80070035The network path was not found

I have disabled "SecureNegotiate" and i can’t enable SMB on the device, it is out of my control.

I have had some luck here:
I connected to a server that is on the domain, i pinged the server again and received a different IP address. I used that IP address and i am now able to map the disk with the IP. using host name still fails in windows 8.

  1. IP address

    Check Windows 7 and Windows 8 are using same subnet and gateway. Use following command


    If Windows 7 can ping the device, Windows 8 should be able to also.

  2. Turn off firewall

    In file explorer, go to following and turn off firewall

    Control PanelAll Control Panel ItemsWindows Firewall

    If you have other firewall software like norton360, you will have to disable it within those software.

  3. Check file sharing is enable

    In file explorer, go to following

    Control PanelAll Control Panel ItemsNetwork and Sharing CenterAdvanced sharing settings

    Under section All Networks, check File sharing connections, select Enable file sharing for devices that use 40- or 56-bit encryption

  4. Check remembered credentials

    In file explorer, go to

    Control PanelAll Control Panel ItemsCredential Manager

    Click Windows Credentials. Check if there are credential related to that NAS, delete it.

  5. WiFi and Wired

    If you have both w-fi and cable connection, try turn off wi-fi.

As I understand it, you need to map a share on a NAS, you cannot map the NAS itself. So try

net use k: \omsmds001nameOfTheSharedFolder

Whether or not your share works with the name (as opposed to the IP address) could depend on various factors, such as

  • your DNS setup – does the configured DNS server know about the NAS’s name?
  • the WINS setup – is there a WINS server in your network
  • the Windows Domain setup – are you part of a domain, does the domain controller know the NAS name, does the NAS know your domain controller and is part of the domain

SO my NAS by dlink couldn’t be seen wither and Synology help was of no help either. I tried uninstalling my LAN driver, re-installing it, trying every thing on this forum:


Also enabled SNMP under components/enable windows features

What I think finally helped was this:

Go to System in Win 8. This is really easy on the metro screen type system then in settings its right there. (this screen has your Windows Experience rating)

Under Computer name, domain, and work group settings to the right it says change settings. Clink this.

Under Network ID it will have 2 bubble options: This computer is part of a business netowork or part of a home computer. I chose HOME COMPUTER option. Restarted and problem solved. Good luck!

The fix is easy:

  • Find your way to the registry entry HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesLanmanWorkstationParametersRequireSecuritySignature

  • Set the parameter to 0

Microsoft acknowledges this issue and has two workarounds: “System error 2148073478,” “extended error,” or “Invalid Signature” error on SMB connections in Windows 8 or Windows Server 2012