How do I make a connection private on Windows Server 2012 R2
Solution 1:
Powershell. Here is an example of changing the network profile of a network interface called Ethernet1 from whatever it is now to "Private." I got this info from Get-Help Set-NetConnectionProfile -Full.
PS C:\>$Profile = Get-NetConnectionProfile -InterfaceAlias Ethernet1
PS C:\>$Profile.NetworkCategory = "Private"
PS C:\>Set-NetConnectionProfile -InputObject $Profile
Documentation: https://technet.microsoft.com/en-us/library/jj899566(v=wps.630).aspx
Solution 2:
A GUI way of making this change:
- Hit Winkey + R to open Run prompt and type gpedit.msc
- Navigate to:
Computer Configuration/Windows Settings/Security Setting /Network List Manager Policies. - Choose your Network name in the right pane.
Note: To show networks not currently connected, right-click Network List Manager Policies in the left pane and choose Show All Networks. Go to Network Location tab and change the Location type from Public to Private.
Close Local Policy Editor.
Source: https://social.technet.microsoft.com/Forums/lync/en-US/82ccc68c-947e-435a-a237-1090f38d0dbe/windows-server-2012-r2-datacenter-network-stuck-in-public-mode
Solution 3:
Using Powershell. Here is an example of changing the network profile of a network interface called Ethernet to "Private." This is a one line command.
Set-NetConnectionProfile -InterfaceAlias Ethernet -NetworkCategory Private
This will work on any local computer with Powershell installed.
Solution 4:
I've had a similar issue for months on my home 2012R2 Domain Controller.
After patching and a reboot I could not connect via RDP.
I have MS firewall turned off in GPO for domain networks. After not being able to connect I found that the primary Ethernet connection was listed as public and therefore the firewall was ON.
Why is the NIC changing from domain to public ?
After researching a few articles on the web, I've concluded the following:
After a restart of the only DC in the domain, AD services are not immediately available when the IP stack is initialized.
This results in the OS sensing that this is a public network and it sets the NIC accordingly.
Permanent resolution of this problem on this machine was to set the Network Location Awareness service to delayed start.
This allows AD services to become available and then the OS senses a domain network and sets the NIC accordingly.
Solution 5:
Another simpler way with Powershell:
Set-NetConnectionProfile -NetworkCategory Private