NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
mlobrien117
Feb 21, 2019Aspirant
Cannot connect to ReadyNAS with windows 10 with new router
I have a RN31222D. I recently installed a new router on our network. I can access the RN312 through the new router on my MacBook but cannot on my Windows 10 machine. I can access the RN312 through a ...
- Feb 25, 2019
Thanks for help. I will continue to use the ip address and not worry about the hostname.
Sandshark
Feb 25, 2019Sensei - Experienced User
That's not an uncommon problem. The only solutions I have found are to just use the IP address or put the host name in your Windows hosts file (Google to find out how). Doing either of those requires the NAS to always have the same IP address. It is better to reserve an address in your router than to use Static IP within the NAS.
mlobrien117
Feb 25, 2019Aspirant
Thanks for help. I will continue to use the ip address and not worry about the hostname.
- aks-2Feb 25, 2019Apprentice
I know this might be a bit of a waste of time, but surely we can find out what's causing this problem, come on, we are techies :).
from a command prompt (as administrator) try: nbtstat -RR
- SandsharkFeb 26, 2019Sensei - Experienced User
I have a complete thread elsewhere trying to fiure this out. Nothing has helped. The biggest clue is that Windows never even presents a login window. The first time after reboot that you try to access it, it takes longer, like it's thinking about asking for credentials, then it fails. Thereafter, it fails immediately.
Oh, and if my dual-boot machine is running Windows 7 when you do the first access, then it works (on the Win10 computers).
This all began on the 1803 Win10 update.
Note, too, that I do not and will not consider putting NAS credentials in the Windows Credentials manager.
- StephenBFeb 26, 2019Guru - Experienced User
Sandshark wrote:
Note, too, that I do not and will not consider putting NAS credentials in the Windows Credentials manager.
I don't think that would solve the OP's issue anyway, since he can access the NAS by IP address.
In this case it appears to be "just" a name resolution problem, perhaps because the NAS is on a different subnet. There is a "legacy windows discovery" control in system->settings->smb, but that's really for Win7 (and earlier). Still, if the Win10 system has SMB 1.0 installed it might help.
- aks-2Feb 28, 2019Apprentice
Is it possible that Credentials Manager has remembered some credentials somehow?
A quick test to try is map a drive, untick "reconnect at sign-in", and tick "connect using different credentials". This *should* force Windows to show the credential dialog box?
It might also be worth opening a command prompt and typing: ipconfig /all
Check: default gateway, ip address, subnet mask, netbios over tcpip is enabled.
I do realise that you may have already tried some of these, just making suggestions in case you haven't!
- SandsharkMar 01, 2019Sensei - Experienced User
For me, I've tried all that and more. Trust me, I'm way ahead of you trying everything.
For the other user, maybe.
Related Content
NETGEAR Academy

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