Win10 networking problem - at wit's end

[Whoozit]

NAS drive on the network has worked fine for the last 5 years. Recent upgrades to Win 10 with Microsoft account caused me to lose direct network access, but could still access from main PC through a mapped network drive.

Changing my router today (Virgin upgrade) changed the DHCP range and grenaded the mapped drive. No way to change it back apparently. The frustration is that a local account on another Win10 machine works fine - but that machine doesnt have Lightroom installed for my photography. So years of image catalogs now no longer work.

The NAS drive is a Netgear ReadyNAS duo v2. I've tried adding user accounts on the NAS, with matched Windows permissions. And fiddled in every arcane part of networking protocols and services that Google suggests.

Ideas?!

[Whoozit]

Cheers Tonsko. If I really have to, I can take the drives out of the NAS and stick one in the main PC (RAIDed so they are mirrored drives). But that defeats the object of having redundancy built in, and in a separate box.

[Chris Hinds]

Check the configuration of your network card in the Network and Sharing Center... better than even money for security Windows 10 has defaults to the new network (as defined by the new DHCP scope) as a Public Network, which means File Sharing is blocked. If it's public, change it to Private then try mapping again.

Kind regards

Chris

[Whoozit]

Chris Hinds said:

better than even money for security Windows 10 has defaults to the new network (as defined by the new DHCP scope) as a Public Network,

Yup, one of the first things I tried.

After further fiddling, it appears I need to allow Anonymous access on the NAS as well as specifying allowed IP addresses...now having fun wrestling the new Virgin Superhub to allow static IPs for the connected machines. I am enormously impressed with the Hub thinking, after assigning a static IP to the machine, that there are now two users trying to access the maintenance web page. You can't release the original lease, and you can't go back in to establish the reserved IP address...brilliant.

[colin79666]

I had the same issue and got round it by using Windows Credential Manager to store the login for the NAS box. The problem comes when you move to Windows 10 and your user account is no longer as simple as the same username/pass as you used on the NAS but is now a Microsoft account. Using credential manager basically maps the two together so Windows passes the local account details on the NAS to the NAS when you connect.

Screenshot below of mine:

[Whoozit]

colin79666 said:

I had the same issue and got round it by using Windows Credential Manager to store the login for the NAS box.

Thanks Colin. That was the fix that worked to restore the NAS box to the (Win10, with Microsoft account) Microsoft network. The fact the local account-only Win10 box connected just fine was immensely confusing.

Even having done that, I still couldn't access one of the shares though - that required permitting anonymous connections with specific IP addresses listed.

Simple this was not!