Sometimes a Windows server is assigned to the incorrect network profile. It can cause applying the wrong Windows Firewall rules. Here is how to change its network profile.
For standalone server
- Can change the profile to public or private; but cannot set to domain
- For Windows Server 2012
- Open PowerShell as administrator
- Get-NetconnectionProfile | Set-NetconnectionProfile -NetworkCategory [Private | Public]
- For Windows Server 2008 or 2012
- gpedit.msc, Computer Configuration, Windows Settings, Security Settings, Network List Manager Profiles
- Select the network name, Properties, Network Location
- Under Location Type, select Private or Public
For domain joined server
- Cannot change the profile manually
- It’s determined by Network Location Awareness (NLA) service (see “Network Location Awareness (NLA) and how it relates to Windows Firewall Profiles”)
- If the network profile is incorrect,
- verify the server can contact a DC via UDP port 389
- restart the Network Location Awareness service on the server
Wow what a Great Information about World Day its very nice informative post. thanks for the post. National Wealth Center FAQ
ReplyDeleteOpen the Network Properites and enable version 6 again, this worked for me not sure if it will work for you, let me know www.cloudzion.com
ReplyDeleteI admire this article for the well-researched content and excellent wording. I got so involved in this material that I couldn’t stop reading. I am impressed with your work and skill. Thank you so much.
ReplyDeleteThis was really an interesting topic and I kinda agree with what you have mentioned here! bookmetoday.com
ReplyDelete