Location:
State:
Carrier
Country
Status

HELP [MAPPING NETWORK DRIVE]--Cannot Connect to NAS


Going to make this short and to the point.

I am on windows 10, tried to map my NAS using map network drive but says "Windows cannot access \Nas102
check spelling or might be problem with your network. Next, I tried to map a specific folder inside Nas102 and it worked! For example \Nas102Music

I also tried to make a fake folder name and map that for example, \Nas102FakeFolder
and the error said check spelling of "fakefolder" Nas102 was detected but not the fakefolder.

So, I need help trying to connect to the whole NAS instead of just mapping individual folders inside of the NAS.
Any help would be appreciated...Thank you in advance.

Hello and welcome to the windowssh blog!

I'll also try to keep this concise! W10 has had quite a few problems with detecting networked devices and it is often due to problems when your W10 device is not the Master Browser on the Network. To get around this make sure you switch on your PC/Laptop first before you turn on any other devices or your NAS on your network. That is one workaround which might help for now. You could do a Google search for more information on this.

Thanks, I've tried google search but all I can find is how people can connect to a network drive, My issue is i can connect to a specific folder but not the whole drive itself.

Do you know the IP address of the drive? Try connecting to that.

Do you know the IP address of the drive? Try connecting to that.
I have 2 identical WDC 2TB NAS drives and the newer one could not be found so I used my Linux computer to get the IP address for both and remapped them in Win7, Win10 and Mac OS X using those numbers for the identification. The first one attached was the default Z: and the other is Y: . To make life [identification] a bit easier for file management I put an empty Folder on each named ~~Y and ~~Z as appropriate, always appears at the top of the Folder lists.

Note: by default Windows starts lettering Network drives beginning with Z: and working back up the alphabet but should be able to use Disk Management to change according to desires.

I have not tried mapping it with IP address.. Will give it a try and let you know how it works out. Thanks so far for your advices


Just an update* Tried the IP Address method, still not working

I have not tried mapping it with IP address.. Will give it a try and let you know how it works out. Thanks so far for your advices


Just an update* Tried the IP Address method, still not working
One of the diagnostics I use is a Linux LiveDVD [or LiveCD for lite versions], boot to it and see it the drive/s can be found. Booting to an Optical disc can be slower but it bypasses Windows, helpful in determining if it is a hardware issue or only with the installed Operating System. I like Linux Mint but Zorin OS or Linux Lite.
Main Page - Linux Mint
Zorin OS - Home

The downloaded file is .iso format and most disc burning programs can create the DVD [or CD] which is then an exact copy of the original disc. They may be either 32-bit or 64-bit, get the one for your type computer.

Hi Phreshboy,

Out of interest what do you get when you enter net view into a command prompt window?

Hi Phreshboy,

Out of interest what do you get when you enter net view into a command prompt window?

I get a message saying the following:
"System Error 1231 has Occured. The network location cannot be reached. See windows help..."

That is most interesting, it confirms my point made in post#2 that your PC is not the Master Browser.

Did you try turning off your NAS and any other devices on the network and restarting your PC to become the Master browser before turning the others back on?

If you do, you might find things will work.

HELP [MAPPING NETWORK DRIVE]--Cannot Connect to NAS