NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
DuckSoupNAS1
Dec 19, 2019Aspirant
Windows 10 loses discoverablity when ReadyNAS joins network
My home network contains a Windows 7 PC, a Windows 7 laptop, a Windows 10 PC and my ReadyNAS 102 running the latest update. If I shut down my NAS and reboot my W10 PC, the W10 PC can network browse itself and all W7 systems. All W7 systems can browse my W10 PC. If I then boot my NAS, my W10 PC can network browse the W7 systems and my NAS, but not itself. Not of the other systems can browse the W10 PC.
I suspect it has something to do with SMB, but am unable to find the right combination of settings to make things work correctly.
Thanks for your help!
8 Replies
- SandsharkSensei
Do you have a static IP on the NAS? If you do, and it's in the range that DHCP hands out, that could be the issue. When you boot the NAS first, it grabs it's static address, which is unused. When the PC is booted next, it's given a different one. But if you boot the PC first, and it gets assigned that same address the NAS uses, then booting the NAS will cause a conflict for that address because it uses the static one, not one assigned by DHCP.
- DuckSoupNAS1AspirantThe NAS does have a static IP but all of my DHCP devices use a different range so there’s no IP conflict.
Do you have legacy windows discovery enabled on the NAS?
Related Content
NETGEAR Academy

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