NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
daweezels
Aug 19, 2020Aspirant
ReadyNAS RND4210 v3 - 1 WIn 10 Station cant connect , 4 others no problems
I have a customer that has 1 Station Win10 that sees the Nas under Network, mapped drives come up with Green but cant connect via mapped drives that have been setup up for a long time 2yrs+. They do ...
- Aug 20, 2020
aks-2 wrote:
You can use Windows Credential Manager to clear any passwords to the named network connection, which I think is what using teh IP address as an alternate "name" for the NAS is doing.
No. Some Windows PCs have trouble resolving the hostname of the NAS to the IP address - especially with the older NAS like the one here.
Though if the credentials aren't correct you can end up with access problems.
daweezels
Aug 20, 2020Aspirant
Sorry if I wasn't clear. Only 1 Station is having trouble (not connecting). All others are fine. I will not be back there til tonight but I will give it a try. Just to add. The NAS shows under Network but "windows cant access", the mapped drives I get different errors on "network name no longer available" and "local device name is already in use. This connection had not been restored. Also have a mapped drive to another station and that link works just fine also. Should have been clearer on that.
Thanks for the responses!
Sandshark
Aug 20, 2020Sensei - Experienced User
I have had a problem like that for some time when using the NAS name to map the shares. Try re-mapping using the IP address. Of course, for that to be a permanent solution, the IP address of the NAS must remain fixed. That is best done by address reservation in your router, not by static IP in the NAS.
Adding the NAS IP to the HOSTS file is another potential solution.
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!