Share via

Network profile switches back by itself from Private to Public after each reboot on all VLAN interfaces

Anonymous
Mar 20, 2024, 12:03 PM

Hi folks. I have to manage a complex backup network and the backup server has multiple VLAN interfaces under a NIC team. The backup software on this server automatically creates all the necessary Windows Firewall rules during the installation or on each update. Those rules are created to apply only in NICs with the domain or private profile.

The problem is that after every single reboot, all the VLAN interfaces under the NIC team switch back from private to public, it doesn't matter if I change it through PowerShell or registry key, it always switches back to public.

Has someone faced this issue before or has a definitive solution?

Thanks!

(I'm running Windows Server 2022 in a Dell R650, fully patched).

Windows Server Networking Network connectivity and file sharing

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments
Accepted answer
  1. Anonymous
    Mar 22, 2024, 8:39 AM

    Hello,

    Based on your current problem, please first modify the registry through the following solution, modify it to a private network and then modify the permissions of the registry to prevent other processes from modifying the registry again.

    1. After WIN+R, enter regedit and press Enter to open the registry and locate HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\Profiles
    2. Click on the code style folders and check the ProfileName data on the right to see if there is one that matches your current WIFI name. Once found, make sure it is in the registry folder.
    3. Double-click to modify the Category. 0 is public and 1 is private. In your current situation, you need to modify the data from 0 to 1. At this point, you can go back to the settings to check whether your current network is confirmed to be changed to a private network. If not, please check again whether the ProfileName is correct and see if there is a more accurate name under other paths.

    If you confirm that the network has been modified to a private network, please go back to the registry and right-click the code path of your current registry-Permissions-Advanced-change the owner here to "Everyone" and then enter the permission content below. Also add a user Everyone, and then set the permission to only allow reading and special permissions that cannot be canceled and confirm. Click OK to close all windows.

    Disclaimer: Modifying the registry or workgroups is generally intended for advanced users, administrators, and IT professionals and can help fix some problems, however, serious problems can occur if the registry is modified improperly. Therefore, please be sure to follow the steps below strictly. For further protection, back up the registry before modifying it. For more information on how to back up and restore the registry reference: How to back up and restore the registry in Windows - Microsoft Support

    After investigation here, we found that this problem is generally caused by third-party anti-virus software, which believes that the network you are currently connected to is more suitable to be set as a public network, so the network will automatically switch configuration after booting. Please check your system. Is there any third-party anti-virus software in the device? If necessary, you can temporarily uninstall it and restart the device again to see if the problem still exists.

    Hope this helps!

    Best regards

    Zunhui

    0 comments

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest