Windows 10: Problem accessing a NAS drive

I have 2 NAS drives and 3 computers in my home network. The NAS drives and one PC are Ethernet-connected to a router/wireless access point; the other 2 PCs use wireless connections. All 3 PCs can access one NAS drive with no problem. The drives show up in the Network section of File Explorer, and if I click on the NAS's icon all it's shares are displayed (whether or not the PC has credentials to access the shares). The shares on the other NAS drive can be seen by only 2 of the PCs.

On the failing PC the inaccessible NAS drive shows in File Explorer, but if I click on it I get




However, on that same PC, Firefox can access the FTP server on the NAS drive



so Windows obviously has no trouble communicating with the NAS. And Windows must be configured to allow communication with a NAS in general or it could not successfully connect to the other NAS. (Those two screen snips were stored on that working NAS.)

The problematic PC doesn't really have to reach the NAS, but I would like it to, and I'm frustrated that I can't figure this out. Anyone have any suggestions?

BTW, the error popup says I should ask the administrator of the server about this. I would, but I'm not speaking with myself at the moment.

:)

 

Unable to connect to NAS with Windows 10...? Annoying and Frustrating as he** is being polite...

Hello,

NAS: QNAP TS-2119P II

Firmware: Latest installed

Cloud Drive: WD My Cloud

Firmware: Latest Installed

Now and then us professionals have to bite our lip buckle up and ask for HELP! I have a problem which I have tried to resolve and I cannot get Windows 10 to talk to my NAS and my NAS to talk to Windows 10. But this question has a double edged sword...? Speaking
metaphorically. My main rig is running the same OS and build and I can access my NAS and my Cloud Drive via Network within Windows 10. The settings are identical for each machine. However main rig can access the NAS and the Cloud but the Surface 3 Pro cannot
access the same network attached Server (Linux Box) and It is driving me crazy because...

The problem is related to permission... not with my Network nor my NAS regarding permissions as Windows 10 is stating is the cause of the problem. If that was there case, then I wouldn't be able to access this on another machine running an identical OS.
Windows 10 is stating the cause of the problem is with permissions on my Network or with my NAS. But these are all set correctly and again, Identical to the other machine with the same OS. Okay arguably the two are not similar because one is built-in whereas
the other is custom built to my spec. But running the same OS and accessing the same NAS and Cloud Drive.

Ever since I started using Windows 10 my access to my NAS has been on an off with different builds of Windows 10. Although W10.10240 on my Microsoft Surface 3 Pro. 10.1066 it was working and now it is on 10.10240 it has stopped again. Although I can access
the NAS if I map a Network Drive from the NAS. QFinder can see the NAS. But I cannot connect to the File. I think this is specifically related to the Surface 3 Pro and nothing to do with Windows 10.

Any ideas would be deeply appreciated. It's really starting to do my head in because I know my settings are correct. Its the Surface 3 that cannot connect to the NAS or Cloud Drive.

 

Cannot see NAS drives after intalling build 10.0.10586

I have seven win 10 machines in my household. After updating 3 of the machines from 10.0.10240 to 10.0.10586 they lost the ability to see all of the NAS drives (2 Dlinks, one Lenovo and one WD My Cloud) in windows explorer. The un-updated machines continue
to access the NAS drives as before but the updated machines cannot see the NAS drives. Are there any suggestions before I start randomly changing the settings to get NAS access back?

Thanks.

 

try checking this fix too perhaps

Solved nas connect problem - Windows 10 Forums

 

The Western Digital My Clouds have been an issue for a very long time, way before Windows 10 rolled out.

 

I'll check that out. I'm thoroughly confused about NetBIOS in a Samba environment. I thought with Windows using SMB over IP (TCP and UDP ports 445) that NetBIOS was no longer needed, but I seem to have problems if I disable NetBIOS. Maybe I have it disabled on the problematic PC.

 

SAMBA is the technology that is used for connecting to Windows and other network systems. NetBios tells windows machines and Samba on LInux & Unix systems how to know how to communicate.

"NetBIOS was developed in 1983 by Sytek Inc. as an API for software communication over IBM PC Network LAN technology. On PC-Network, as an API alone, NetBIOS relied on proprietary Sytek networking protocols for communication over the wire. Because PC Network only supported up to 80 devices in its most accommodating mode (baseband), NetBIOS was itself designed with limited nodes in mind."

Windows is so tightly wound with old tech, that because Netbios is embedded in the OS, along with their version of Samba, one thing breaks, everything breaks.

 

the default in win 10 (default) doesn't seem to work on all pc's from some reason , setting to enabled cured my issues and others.

KB