Forum Discussion
Domain Controller showing network connection as Public
Notice for quite awhile now with the vnext server builds that when you promote it to domain controller it shows the network connections as public or private instead of DomainAuthenticated. Is the...
This is not new, not limited to Server vnext rather "normal" since Server 2008 (without R2 - yes vista level!).
Three and a half solutions.
Half: Just wait, after a few minutes it usually detects it.
1. Quick: Restart "Network Location Awareness" aka "NlaSvc".
2. Correct: Set fixed IPV4 config (duh!), and then Policy -> Computer Policy -> Windows Settings -> Security Settings -> Network List Manager Settings -> set how to treat unknown and "detecting" networks. Your Windows Firewall should be set up correct too of course. IPV6 is a different beast.
3. Wrong: Disable Windows Firewall, neither GUI nor the services. Just don't. Windows often switches back to "total paranoia" mode randomly if you do that, and then you have to get to the local console.
Better use "Correct". Since the network location awareness starts before the DC services are fully available it cannot detect on which network you are. Same happens if, for some reason, default gateways answer on second of third ping after restart (complex switch environment etc).
I use the "Correct" method whenever possible, including networks of customers I see for the first time. Solves a lot of weirdness in many cases.
Three and a half solutions.
Half: Just wait, after a few minutes it usually detects it.
1. Quick: Restart "Network Location Awareness" aka "NlaSvc".
2. Correct: Set fixed IPV4 config (duh!), and then Policy -> Computer Policy -> Windows Settings -> Security Settings -> Network List Manager Settings -> set how to treat unknown and "detecting" networks. Your Windows Firewall should be set up correct too of course. IPV6 is a different beast.
3. Wrong: Disable Windows Firewall, neither GUI nor the services. Just don't. Windows often switches back to "total paranoia" mode randomly if you do that, and then you have to get to the local console.
Better use "Correct". Since the network location awareness starts before the DC services are fully available it cannot detect on which network you are. Same happens if, for some reason, default gateways answer on second of third ping after restart (complex switch environment etc).
I use the "Correct" method whenever possible, including networks of customers I see for the first time. Solves a lot of weirdness in many cases.
I removed the default NIC from vmware, added a new one and that solved the issue. Joachim_Otahal
Gumby617 😄 everything is fine when it solves the issue!
