New Windows NLA profile after Mikrotik upgrade

[n1am]

Hello guys,
I noticed that sometimes after a Mikrotik upgrade, and the Mikrotik is the DHCP server for the network, Windows NLA (Network Location Awareness Service) create a new network profiles. The only problem is the Windows default network profile Public. The firewall in this profile is more aggressive and deny RDP access, for example.

Is there a way to fix this behaviour?

Thanks

[jarda]

If you do use bridge for local network, do you use administrative mac address for it? If not, Windows may detect different networks as the mac is set for the bridge dynamically, therefore can change as the connected ports are changing times to times.

[n1am]

@jarda

If you do use bridge for local network, do you use administrative mac address for it? If not, Windows may detect different networks as the mac is set for the bridge dynamically, therefore can change as the connected ports are changing times to times.

Thank you for the reply.

[jarda]

… and did it help or the problem lies elsewhere?