I completely understand the segmentation of networks based on labels – Private for trusted internal communications, Public for non-trusted or external communications, and DomainAuthenticated for domain-joined systems. This allows for a more fine-tuned windows firewall experience and can create a more secure environment.<\/p>\n\n\n\n
Unless the automatic labels get it wrong. OK, I should preface that I’ve never seen the automatic network labels go the wrong way – that is to say a “public” connection that is actually labeled as a private\/trusted one. However, it’s still a PITA when Windows thinks the connection is untrusted (public) when it’s really something on the internal network.<\/p>\n\n\n\n
It generally does this with my VPN connections. TUN and TAP both have had this issue, so I think it’s more a Windows-feature than anything else.<\/p>\n\n\n\n
Enter PowerShell. You’ll see a theme here, I’ve been PSing a lot more lately.<\/p>\n\n\n\n
Get-NetConnectionProfile<\/code><\/li><\/ul><\/li>- Find the Interface Index of your connection, then set the category
Set-NetConnectionProfile -InterfaceIndex 22 -NetworkCategory Private<\/code><\/li><\/ul><\/li><\/ul>\n\n\n\nThere are ways to do this from a Registry Editor perspective as well, but this seems to be the easiest way (and doesn’t require a reboot). More info here http:\/\/woshub.com\/how-to-change-a-network-type-from-public-to-private-in-windows\/<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"I completely understand the segmentation of networks based on labels – Private for trusted internal communications, Public for non-trusted or external communications, and DomainAuthenticated for domain-joined systems. This allows for a more fine-tuned windows firewall experience and can create a more secure environment. Unless the automatic labels get it wrong. OK, I should preface that … Continue reading Windows Change Network Type<\/span>