NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Weird "Unknown" and "Public" Network Issue With Windows 10, ReadyNAS and Static IPs
I have a home network with all computers running Windows 10, except for my ReadyNAS 628X and my pfSense computer router. When a Windows 10 computer is added to a network, Windows 10 somehow magically decides whether the network is known or unknown. If known, you can toggle between "private" or "public" network profiles. If Windows decides the network is unknown, however, it forces the public network profile on the computer. This public profile then disables network discovery and file and printer sharing.
The last two computers I have built have both been forced to the public network profile when I try to use static IP addresses. Using 3 different "hacks" to force a private profile (including a registry hack) only works until the computer is rebooted. Once rebooted, it detects an unknown network and is forced to the public profile again. This problem doesn't happen if I use DHCP to get the IP addresses.
I then stumbled upon a weird fact. The two new computers did not have the ReadyCLOUD desktop app installed. Once I installed this app, I was able to assign static IPs to the computers and they could keep a private network profile.
1. Has anyone experienced this problem before?
2. Is this a known issue with having a ReadyNAS device on your home network?
3. Do you think the ReadyNAS is the cause of Windows 10 deciding it's an "unknown" network and then forcing the "public" profile?
4. I wonder if Netgear is aware?
5 Replies
Replies have been turned off for this discussion
Hi XrayDoc88
Not really sure if the NAS is causing this issue since we don't think the ReadyNAS can control anything on what the Windows OS does within the Network or PCs when it comes to Public or private profiles. If in any case, contacting Support might be a good idea so they can check and investigate if needed.
Regards
Marc_V wrote:
we don't think the ReadyNAS can control anything on what the Windows OS does within the Network or PCs when it comes to Public or private profiles.
I agree, though I guess it's possible that installing the ReadyCloud application on the PC might affect the Windows behavior somehow.
XrayDoc88: I am wondering if you are assigning private (not internet routable) static addresses, or if you are assigning public addresses.
You should be assigning addresses from the following ranges which are designated for private networks:
- 10.0.0.0 to 10.255.255.255.
- 172.16.0.0 to 172.31.255.255.
- 192.168.0.0 to 192.168.255.255.
If you are using other addresses, it would be reasonable for Windows to assume you were on a public network.
FWIW, you can reserve addresses in your router (pfsense calls this "static IP mappings). That's a better strategy than assigning static IP addresses to clients - it's more easily managed, and makes it less likely that you'll misconfigure a device (resulting in a duplicate address, etc).
- I am definitely assigning static IP addresses that are in the private range. I use 192.168. 0. X with a subnet mask of 255.255. 255. 0. All of the static IP addresses are also in a separate range from the DHCP addresses that are also active on the same network.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
