Unable to access NAS through file explorer

Don
Joined
23 Oct 2005
Posts
44,453
Location
North Yorkshire
Hi guys,

Strange issue, last night out of nowhere after a reboot of my PC a message popped up saying Windows couldn't connect to all mapped drives. No biggie, it usually happens. However, 24 hours later I'm still unable to access my WDMyCloud through file explorer, I want to get to the root folders I've created. I can access it fine on my Surface Pro.

Usually I can browse to the IP if the name doesn't resolve using \\192.168.*.* or usually just \\wdmycloud, however Windows just kicks up an error saying it can't connect to it.

I can ping it and access the webpage on my browser just not get to it via file explorer!

I'm on Windows 10 which it has been working flawlessly, nothing has changed on my PC. Any ideas what I could try as I feel I have exhausted all options.

Thanks
 
Click Start, type in credential, click on Credential Manager. Click Windows Credentials, find your NAS in the list and delete every entry. Then reboot and try again.
 
Have you tried creating a user account and requiring it? I've seen strange stuff happen when trying to authenticate anonymously.
 
Turn your Firewall off and try again.
Are you able to access other services on your network, like your Surface?
Open a cmd prompt as an administrator and type in net use - what does it show as your mapped drive?
What does a NBTSTAT -a ipaddressofNAS show?
 
Turned off firewall, no change.
Surface can access everything on the network, can see the NAS files no problems at all, Windows 10 on that too.

BSTSTAT:



The NAS is even recognised in Device Manager.
 
Well I reinstalled Windows 10 today, just using the in built restore service within 10. Started working again and has stopped just now. The only things I have installed are iTunes, TeamViewer, Zviewer, Hotspot shield and Logitech Setpoint software. Software I've had installed for 1 1/2 years I've had the NAS and they're also all on my Surface Pro.

I've tried flushing the DNS to no avail.

Anything else? Could there be a service that hasn't started?
 
Seems a lot having issues on Windows 10 with mapped drives, so silly that it's worked all this time, makes life so much harder!
 
Fixed! I'm not sure if Windows Updates rectified something, or the latest NIC drivers I installed but it just started working....Let's hope it stays that way. Thanks for the help!
 
Back
Top Bottom