MS Server 2012/2016 Shows Wrong Network Profile
(also applies to Windows 8.x and 10)
One of those little annoyances that can sometimes happen with the Network Location in MS Server 2012/2016, is that the network gets misidentified as Public when it should be Private, or the other way around. Changing this in the GUI is certainly possible, but can be annoying, so we can take advantage of the improved Windows PowerShell support in Server 2012 and 2016 and do it quickly and easily.
First, let's open up an elevated PowerShell window, from the main menu, under W -> Windows PowerShell -> more, then right-click ‘Run as Administrator’:
Now, in that window, let's find out what our current network location is set to:
From this, we see that the problem interface has an Interface Index of 18, so:
And we’re done, if we check the network location again, we can see it is now Private again.
- This can also occur on domain attached servers. In that case, it will usually be necessary to detach the server from the domain, run the above procedure, then reattach to the domain, but Domain Administrator credentials will be required.