networking:windows:network_profiles
Differences
This shows you the differences between two versions of the page.
Both sides previous revision
Previous revision
Next revision
|
Previous revision
|
networking:windows:network_profiles [2021/11/19 10:42] gcooper |
networking:windows:network_profiles [2025/05/19 19:27] (current) gcooper |
| |
http://blog.mpecsinc.ca/2013/08/server-2012unidentified-network-with.html | http://blog.mpecsinc.ca/2013/08/server-2012unidentified-network-with.html |
| |
| <note tip>If you have problems with the Windows Firewall selecting **Private instead of Domain Profile**: |
| |
| Add the follow registry key (you may need to reboot) (this worked on Server 2022): |
| |
| ''[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NlaSvc\Parameters] "AlwaysExpectDomainController"=dword:00000001'' |
| |
| Other suggestions that may not work: **restarting the NLA service** or setting the NLA service to ''Automatic (Delayed Start)''.</note> |
| |
===== Registry ===== | ===== Registry ===== |
http://blogs.technet.com/b/networking/archive/2010/09/08/network-location-awareness-nla-and-how-it-relates-to-windows-firewall-profiles.aspx | http://blogs.technet.com/b/networking/archive/2010/09/08/network-location-awareness-nla-and-how-it-relates-to-windows-firewall-profiles.aspx |
| |
<note tip>The ''DomainAuthenticated'' category is set automatically. If you need to change from Private to ''DomainAuthenticated'', try rebooting the server. You might also just disable, then enable the network interface in question.</note> | <note tip>The ''DomainAuthenticated'' category is set automatically. If you need to change from Private to ''DomainAuthenticated'', try rebooting the server.</note> |
| |
| <note tip>If rebooting is problematic, you might try **disabling, then re-enabling the network interface** in question.</note> |
| |
===== In PowerShell ===== | ===== In PowerShell ===== |
networking/windows/network_profiles.1637343730.txt.gz · Last modified: 2021/11/19 10:42 by gcooper