Windows 8 – Mapping Network Drive (NAS)

nasnetwork-shareswindowswindows 8

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:

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: \\omsmds001\
System error 53 has occurred.
The network path was not found.

and

net use k: \\10.0.25.3
System 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 \\omsmds001
Error Code: 0x80070035
The network path was not found

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

UPDATE
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.

Best Answer

IP address

Check Windows 7 and Windows 8 are using same subnet and gateway. Use following command
```
ipconfig
```
If Windows 7 can ping the device, Windows 8 should be able to also.
Turn off firewall

In file explorer, go to following and turn off firewall
```
Control Panel\All Control Panel Items\Windows Firewall
```
If you have other firewall software like norton360, you will have to disable it within those software.
Check file sharing is enable

In file explorer, go to following
```
Control Panel\All Control Panel Items\Network and Sharing Center\Advanced sharing settings
```
Under section All Networks, check File sharing connections, select Enable file sharing for devices that use 40- or 56-bit encryption
Check remembered credentials

In file explorer, go to
```
Control Panel\All Control Panel Items\Credential Manager
```
Click Windows Credentials. Check if there are credential related to that NAS, delete it.
WiFi and Wired

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

Related Solutions

Windows – Can’t reach Qnap NAS from Windows 7

First of all it puzzles me a bit too that you say you cannot reach the web interface (HTTP) of the NAS via the browser.

But regarding SMB shares this might be related to some Windows 7 settings in combination to older SAMBA versions (don't know which version is run by your Qnap NAS).

First of all you should open the Network and Sharing Center of Windows 7. Then make sure your network is listed to be a "Home network" - and not a "Work network or "Public network".

If this is correctly set and it still does not work you might have to check your network policies. On Windows 7 Pro just launch Local Security Policy from your start menu and check the following values:

Local Policies -> Security Options -> Microsoft network client: Digitally sign communication (always)
- This should be set to disabled as most Samba servers in NAS devices to not work with signed communication.
Local Policies -> Security Options -> Microsoft network client: Digitally sign communications (if server agrees)
- This can be set to "Enabled" as Widnows will still fall back to unsigned communication if the server does not support it.
Local Policies -> Security Options -> Microsoft network client: Send unencrypted password to third-party SMB servers
- In general this option shall be set to "Disabled". However some pretty old Samba versions used in older NAS devices do require the password to be sent in plain for authentication. So if you still cannot access the NAS shares you might try setting this policy to "Enabled". Do only enable this if your NAS really does not support encrypted passwords or for testing purposes. It can and it will expose your password to network intruders.

Regarding the web interface. You said you can ping your NAS IP. What is the IP? Is it possible there is some IP conflict in your network? If no, then you might try telnet to test whether your NAS web-server answers:

telnet <NAS-IP> 80

Caution: The telnet client is not installed by default on Windows 7. So either install it or use alternative telnet clients like PuTTY.

To install the Windows 7 telnet client you might either do this via control panel/Programs or via elevated command line prompt:

pkgmgr /iu:"TelnetClient"

Edit 1: Registry values

Before I did not have time for a research on the registry values. If you would like to enable plain text passwords sent to 3rd party SMB servers or change the other policies I was referring to you can of course do this on Windows 7 home too. But you need to edit registry values since the security policy editor is not available in home premium or basic version of Windows 7 (according to my knowledge).

So here are the values which I've described above. Just copy the contents of this file to a *.reg file (e.g. call it SMB-security.reg and then import it with elevated permissions.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\LanmanWorkstation\Parameters]
; Microsoft network client: Send unencrypted password to third-party SMB servers
; If this option is enabled then passwords are sent in plain over the network
; Only disable if you're running a really really old SMB server (e.g. old NAS)
; which does not support encrypted passwords:
; Default Value:
"EnablePlainTextPassword"=dword:00000000
; Enable sending of unencrypted passwords over the network
; "EnablePlainTextPassword"=dword:00000001

; Microsoft network client: Digitally sign communications (if server agrees)
; This enables digitally signed communication between SMB/CIFS clients and
; servers if the server supports it. If the server does not support it, then
; unsigned communication might still be established.
; Default:
"EnableSecuritySignature"=dword:00000001
; Disable digitally signed communication (even if server would allow it)
; "EnableSecuritySignature"=dword:00000000

; Microsoft network client: Digitally sign communication (always)
; This enables the requirement for digitally signed communication between
; SMB/CFS clients and servers. If the server does not support digitally signed
; communication, then connection will fail in case this option is enabled.
; Default:
"RequireSecuritySignature"=dword:00000000
; Enable required signature - communication will fail if server does not support
; signed communication
; "RequireSecuritySignature"=dword:00000001

; Disable requirement for DNS name resolution:
; Setting this option to 0 might be required if you use Samba as a domain
; controller
; Default:
; "DNSNameResolutionRequired"=dword:00000001
; Disable requirement for DNS resolution for server communication
; "DNSNameResolutionRequired"=dword:00000000

Windows – Win 7 mapping to NAS only works by IP, not UNC

Ok, based on what you've said here's my guess/suggestions...

Assumptions/guesses about configuration:

Your "Diskstation" NAS is using DHCP to get it's IP.
Your DHCP is being handed out by your router, and in those DHCP settings it's giving out itself as the DNS server for clients to use.
Your router is aware of the host names of the devices that requested DHCP from it, and it adds those host names to its internal name (DNS) records.
Anyone using the router as their DNS server will have those host names resolved.
Your PC is using the Windows server as its DNS server.
You have no record in your Windows DNS server for the "Diskstation" host.
You Windows DNS server is not setup to forward unknown requests to the router.
Therefor any machine that requests a name lookup for the "Diskstation" host from the Window DNS server isn't going to get an address returned.

Short Solution 1):

Set your PC to use the router as its DNS.

While this will work, it's a bad idea, as this will greatly slow down your domain logins while it tries to find the Domain Controller (usually quickly found via a DNS lookup).

Short Solution 2):

Setup the Windows DNS server to forward requests for unknown hosts to the router.

The router will get those requests that the Windows DNS doesn't have entries for, and answer with the right IP (if it's a host the router knows about, which the Diskstaiton should be).

Suggestion solution:

Setup DHCP on the Windows server.
Disable the DCHP server in the router.
Configure Windows DHCP to be allowed to update DNS records of the Windows DNS server.
Configure windows DHCP to hand out the Windows server as the primary/only DNS server for clients to use.
Setup the Windows DNS server to forward requests for unknown hosts to the router, or directly to your ISP's DNS (or a public one like Google's or OpenDNS or whatever).

By using the Windows DHCP integrated with Windows' DNS server means that you can/will have DNS entries automatically added/updated for any devices that successfully use the DHCP server (ie: your NAS).

As above, the Windows DNS will try to answer first, and if it doesn't have a record for that host it'll pass it up the DNS server chain.

Best Answer

Related Solutions

Windows – Can’t reach Qnap NAS from Windows 7

Edit 1: Registry values

Windows – Win 7 mapping to NAS only works by IP, not UNC

Related Question