Link to home
Start Free TrialLog in
Avatar of David Schmalzer
David SchmalzerFlag for United States of America

asked on

private to public network

I have struggled with this repeatedly with Windows 7 and Windows 10. While there are solutions out there that describe how to change a network from Public back to Private (And not all solutions work because sometimes the options are not visible within Network and Sharing Center), I still cannot find out why this happens and it doesn't matter whether it is in a domain environment or workgroup environment. Is there a Windows Update that causes this?  I don't know, can anyone shed some light on this as to why this happens?  Why does a network, out of the blue for no apparent reason, switch from Private Network to Public network making the internet inaccessible?
Avatar of heatfan07
heatfan07

Based on my understanding from the article below, Windows will "attempt" to make a determination about the network using NLA.  The article has some suggestions (towards the bottom) regarding how to control this with Group Policy, so you might start there as far as how to force your system to remain on Private and not flip over to Public:

https://blogs.technet.microsoft.com/networking/2010/09/08/network-location-awareness-nla-and-how-it-relates-to-windows-firewall-profiles/
ASKER CERTIFIED SOLUTION
Avatar of John
John
Flag of Canada image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
No comment has been added to this question in more than 21 days, so it is now classified as abandoned.

I have recommended this question be closed as follows:

Accept: heatfan07 (https:#a42388869)

If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.

seth2740
Experts-Exchange Cleanup Volunteer
Avatar of David Schmalzer

ASKER

I would like to accept the answer by John Hurst, since we have all upgraded to Windows 10 and the latest 1709 upgrade did fix the issue.
Newest version of Windows 10 1709 addresses the issue.
Thank you. I use the new feature in V1709 quite a bit.