Windows 10: Set Network Location to Private or Public in Windows 10
I just wasn't looking close enough. I cannot think of any advantage to having a wifi profile set to Public other than it may be needed for a HomeGroup? And the only thing left was to offer them a choice.
As there are only two options, it would be easiest to simply provide a script for PRIVATE and another for PUBLIC and let this one be "OVER" with .
On a side note, the use of the Free version of NetSetMan (which I believe you have offered people before) also is a nifty thing to have. It seems to do everything else other than offer a fix for the "Private vs Public"
No problem. Hopefully the different options in the tutorial will give folks a variety to meet their needs.
I'm running 1511 and have the same problem(s).
What does "Homegroup" consider to be a network?
This may belong in another thread, possibly another forum; I'll apologize in advance, but if this rings any bells, let me know; in the meantime I'll investigate more widely.
The reason I've spent the last 20 hours or so trying to make my local network(s?) Private is I'm trying to add 2 PCs to my Homegroup. One is a Windows 7 machine, the other a Windows 10 (1511, 10586.218). Homegroups, as I suppose everyone now knows, only work with Private networks.
My LAN is fed by a Netgear router providing Gb Ethernet, and 2.4GHz b/g/n, and 5 Ghz a/n wireless connections. All interfaces share the same Class C address space. It looks like Windows is considering those three connections as separate networks -- it will only allow a Homegroup connection to a computer connected to the same interface used by the computer that defined the Homegroup. Specifically, the W7 server that defined the Homegroup is connected via Ethernet; I was able to easily add another Ethernet-connected W7 PC to the Homegroup, but not one connected wirelessly. It did recognize that a Homegroup was available, but when I told it to join, it just sat there. The Homegroup diagnostics and network diagnostics were silent. But when I added a wired connection, the join was completed in a few seconds. Bad wireless link, one might say, but it worked flawlessly to install close to 200 Windows Updates during the day, and worked just now to join the W10 machine, after I used the Registry mod (#1, as I remember) to make the interface Private. Many thanks for that tip and the rest of this thread.
That's correct. A homegroup requires the joined PCs to be set to a Private network.
It would be best to pursue the homegroup issue in a new thread in the Network and Sharing forum area.
For now, you might see if the information in the tutorials below may be able to help.
Homegroup - Create in Windows 8
Homegroup - Create - Windows 7 Help Forums
Homegroup - Join in Windows 8
Homegroup - Add Computer or Join - Windows 7 Help Forums
I just found this forum and I have a question related to this thread:
I have two desktops (mine and my wife's), one laptop (shared), and a Western Digital MyCloud hard drive connected to my home network. The desktops and the MyCloud are Ethernet wired and the laptop is wireless. All connections go through the Netgear router. I have Norton installed for firewall and anti-virus. I am the one who sets up the computers, so I have been running my desktop as Administrator. Today I was looking at the Network and Sharing Center control panel and I see that I have two active networks as shown below.
I'm afraid I don't know where this "Unidentified network" came from and I don't know which device it applies to.
(1) Can you point me in the right direction so I can figure out which device this "Unidentified network" applies to?
(2) I assume it's not one of the desktops, so is there a risk involved if I just make the network Private?
Thanks for the great info.
Hello JDA53, and welcome to Ten Forums.
If you like, click on the "Change adapter settings" link, and see if the network adapter for "Ethernet 3" is listed. If so, you could disable it to remove the "Unidentified network".
Thanks a lot for the great post. I'm just wondering is it ever possible (for example due to Windows update) for network discovery to turn on or for network locations to change without user permission ?
Usually this setting will not get changed unless you do so, but it wouldn't surprise me if a Windows Update may reset it back to default.
I have noticed in the last couple of builds the network defaults to public instead of private. I can see that on a tablet but not on a desktop. It is not hard to change the network to private but I wonder how the upgrade will behave on the millions...
I just noticed in Windows defender My network is listed as public. Does it matter if my network is listed as private or public. I found how to change it if I have to. I just want to know if it matters. I don't know if this has anything to do with it...
I have noticed something I think is a little strange. If you install one of the later builds from offline, or where a Microsoft account is not involved, it appears your Local Network will be designated as "Public" even though the correct IP address...
Does anyone know how to change the network from Public to Private in build 9926? It's defaulting to Public with network discovery turned off, etc, and I'd like to change it to Private.