Windows 10: NAS not accessible for writing from Win10 IP

I have two VMs in a VirtualBox Win7 Host.
One is an upgrade of a Win7 machine and the other is a conversion of a IP install to the ISO download.
I am having a problem accessing my NAS (an old Netgear ReadyNAS) from these machines.
I read in another thread about someone who got it to work by changing to a local account. This also worked for me on the ISO installed version but not on the upgrade. Both machines are activated and have been updated to latest.
I am baffled what is the difference between the machines that allows one to write to the NAS and not the other?

:)

 

homegroup with windows 10 & windows 7.

On the windows 8.1 machines: When I first tried to access the NAS network credentials were asked for. I signed in with the user names and passwords established in the NAS and checked for them to be saved. This provided me with seems access. By the way
the machine already saw the NAS on the network. The NAS was is setup as DHCP, not static.

As for Windows 10: The machine doesn't see the NAS on the network (the NAS has all the same settings and passwords). Only sees it after a reboot, power cycle or factory reset of the NAS; for a limited time and then it can't find it again. When I accessed
the NAS through the app on the win10 machine, network credentials were asked for given and saved, access to the NAS was given. When win10 sees the NAS, I have access to it.

Therefore the credentials must be established.

If there is something extra to do in win10, I'm not aware of it. If the NAS has to be a static IP, I'm not aware of it. If you mean something else or have further direction, like how to create said network credentials, I'm reading.

 

One specific UNC path suddenly not working on one specific Win10 machine

Hi,

A month or two ago, my main computer stopped being able to access my NAS' UNC path (\\corbeau\...). It used to work.

• I do not remember changing anything on that NAS
• Other Win10 machines can access that same UNC path
• The problematic machine can access the NAS by using its IP in the UNC path (\\192.168.2.10\...)
• All machines can access other machines by their UNC path (\\cardinal\... or \\epervier\...)
• A ping for the NAS name from the problematic machine fails to resolve
• Pings from other machines work
• Every machine can ping other machines by their name

I'm totally lost. Where should I look for to resolve this very annoying issue?

Thanks.

 

What anti-virus software to you use?

 

So its not that then, I've found that programs like Avast can block local IPs.

 

Thanks for your interest please don't hesitate to report any other suggestions.