Win10 & QNAP NAS aren't cooperating

Under Win7 I could map a network drive like \\MYNAS\homes\myname. Doesn't work under windows 10. The NAS unit does not appear as a "computer" under w10 list of available network devices. It does, however, appear under a list of "media devices". This would work for my media content but does not work for giving me access to my user account.

Any ideas?

Also my old network map to \\MYNAS\multimedia wouldn't connect (no surprise there), but I couldn't get it to unmap that drive letter. I get "device not found" (captain obvious).

Any time you have three or more “levels” in a UNC path you’re including navigation into a folder as part of your drive mapping. For troubleshooting purposes, I would suggest trying to map to just \\[Server]\[ShareName] . Using the example you gave, that would be simply \\MYNAS\homes . If that still doesn’t work then try using the QNAP’s IP address instead of the “MYNAS” name. For example \\192.168.1.50\homes .

Billiam29 said:

Any time you have three or more “levels” in a UNC path you’re including navigation into a folder as part of your drive mapping. For troubleshooting purposes, I would suggest trying to map to just \\[Server]\[ShareName] . Using the example you gave, that would be simply \\MYNAS\homes . If that still doesn’t work then try using the QNAP’s IP address instead of the “MYNAS” name. For example \\192.168.1.50\homes .

Click to expand...

Excellent info. I'll give it a try after dinner.

<sarcasm>Thank you Microsoft</scarcasm>

Windows 10 wouldn't remove a disconnected (unmapped) drive until you reboot.

Also, my NAS didn't show up as a "media device" after reboot. This I still don't understand, but it works so I won't knock it.

Carey Brown said:

<sarcasm>Thank you Microsoft</scarcasm>

Windows 10 wouldn't remove a disconnected (unmapped) drive until you reboot.

Also, my NAS didn't show up as a "media device" after reboot. This I still don't understand, but it works so I won't knock it.

Click to expand...

For a small home network, I've never really found it worth the effort to figure out any issues with network "browsing" services for locating file servers. I even keep the Network Discovery service disabled on my Win 10 machine. I find that you seldom, if ever, need to remember anything since Windows keeps the last three or four drive mapping stored within the Map Network Drive dialog box.

Start with the QNAP Qfinder application and have it locate the NAS on the network. After that you can login and if all is well you can get Windows to see it as well. It helps a great deal to have a fixed IP address for any NAS and not use DHCP where the address changes day to day.

So I purchased a QNAP. From my desktop it shows up as both a media device and a server. From my laptop, it only shows up as a media device, and it's not found using "net view" from a command prompt. Both machines are running W10 Pro. I've installed QFind on the laptop and it finds the QNAP.

Tried two other laptops, both W10, one home edition and the other Pro. Both don't see the QNAP as a server.

Of course a drive can be mailed to a share on the QNAP device using it's IP address (if the name of the share is known), but I'd like to be able to browse it as that will show all available shares.

Anytime know why some clients can't see the QNAP device via Explorer or net view? I've done some searching but haven't found anything. QNAP support didn't have an answer either.

I'm assuming your laptops connect with WiFi. Does one of them have a hardwired Ethernet port? If so, do you get the same behavior when connected hardwired?

In my experience, network browsing/discovery services are usually based on broadcast or multicast network traffic. These almost always seem to be among the first things affected by WiFi configuration nuances. The easiest thing to check first is if your WiFi clients are using the same IP network as hardwired Ethernet clients. For example, is everything 192.168.1.[something] or something like that?

Does the NAS have a Static address?

No. But I did setup a DHCP reservation for it so that it always receives the same IP address.

All devices are on the same subnet.

All laptops are on WiFi, and I've not tried connecting one via Ethernet cable. Good suggestion.