NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Can't Access NAS Shares Consistently on Windows 10 – Any Fix?
I upgraded my PC to Windows 10 mainly to play Stardew Valley multiplayer, but now I’m facing an issue where my NAS (RNAS2120) shares only work once after reboot. After that, it says the drive is already in use or throws a login error.
I’ve set up NFS support and identity mapping, and it worked the first time — but stops after closing and reopening Explorer. Anyone know a reliable fix?
Windows only allows you to log in as one user on any network asset. Your problem sounds like you (intentionally or not) are trying to use two different sets of credentials. When the second set is used, that is the typical error message. There is a way around that. Windows treats the device name and IP address as different devices. In fact, you can create many aliases in the Windows hosts file and it will treat each as separate, so you can have separate logins for each.
If that's not it, it may also be a known issue with some Linux systems and Windows. It only seems to happen when the Windows user name and/or password is different than the NAS one and it seems to affect some users but not all. I have yet to find a real solution, but the work-around is to always use the IP address instead of the NAS name.
2 Replies
Windows only allows you to log in as one user on any network asset. Your problem sounds like you (intentionally or not) are trying to use two different sets of credentials. When the second set is used, that is the typical error message. There is a way around that. Windows treats the device name and IP address as different devices. In fact, you can create many aliases in the Windows hosts file and it will treat each as separate, so you can have separate logins for each.
If that's not it, it may also be a known issue with some Linux systems and Windows. It only seems to happen when the Windows user name and/or password is different than the NAS one and it seems to affect some users but not all. I have yet to find a real solution, but the work-around is to always use the IP address instead of the NAS name.
Thanks a lot for the detailed explanation — this really helped!
Turns out I was trying to connect using two different sets of credentials without realizing it. I used the IP address method you mentioned, and that worked perfectly. Issue is now resolved.
Appreciate the workaround and clear breakdown — saved me a lot of time! 🙌
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
