Domain Joined Server Shows Public Network

Some desktops especially those that have are behind a couple switches often have problems confirming that they are on the domain so they come up on the public network which messes up rdp connections.

Domain joined server shows public network. Therefore some outgoing connections may be blocked and some. Anyway it can happened that nla service starts before the ad services are started or before dc is reachable on a non dc server. If firewall is enabled most of network services will not run as the firewall for the public profile is almost closed. Run the elevated powershell console.

It s a wired mostly gigabit network. The domain profile will always be used for a domain network connection. On a computer that is running windows 7 or windows server 2008 r2 the network location profile that is selected changes unexpectedly from domain to public. There are 2 dcs both w2k12 r2.

Change network types using powershell in windows 10. Additionally the firewall settings these are determined by the network location profile change to the settings that correspond to the public network location profile. In this case we will have public network profile on dc or domain joined computers. Windows server 2012 connected to a local domain network reports network type as a public network.

On windows 10 windows server 2016 2019 you can manage network connection location from the powershell. One small client has a server 2012 r2 essentials domain controller and a few windows 7 desktops. However found that one of the dc and few other w2k12 r2 member servers all are vms was assigned with guest or public network profile instead of domain network. On the network and connection center it was shown with unidentified network.

Also you cannot change the network profile on the domain joined computer. This causes windows firewall to block some network services that are expected to work on a domain network i e.