Comments
 
posted on January 1st 1970, at 01:00
by lunarg
It can happen that the network profile on a domain controller switches to Private, usually after changing network settings or a network adapter. The network profile is then set to Private with no way to switch to Domain.

The first thing you can attempt is to restart the Network Location Awareness service. This service is responsible for setting the network profile depending on several parameters. It can sometimes get it wrong (usually because of startup order).

If restarting NLA helps, then there's an easy registry fix to permanently resolve it. This is the preferred method over manually configuring service dependencies in the registry, which is more complex and prone to errors. While the   ...
Add a new comment
 
Your name:
Your e-mail:
Your comment:
 
Basic BBcode is supported.
Captcha:
Type the letters and numbers as shown.
/get/captcha/1729069043
Not readable? Get another.
 
 
 
 
« October 2024»
SunMonTueWedThuFriSat
  12345
6789101112
13141516171819
20212223242526
2728293031  
 
Links
 
Quote
« Debating Windows vs. Linux vs. Mac is pointless: they all have their merits and flaws, and it ultimately comes to down to personal preference. »
Me