Issues with Windows Server

[paul19920801]

Hi all...

I have a Windows Server 2016 VPS - I use netmaker to link various services to my WAN.

I'm forced to use a secondary Wireguard VPN connection linked to another Wireguard node as I've found that Netmaker clashes with my Firewall. As much as I hate Firewall software my VPS configuration is that there is no such thing as virtual servers, and port forwarding and every port that's open is exposed to the internet. So I am dependant on my Windows Firewall to ensure that ports are blocked..

I also have different location settings for my networks. my main Ethernet connection in to my VPS is set to public.
Netmaker by default is also public. I set it private - as if it's public my ports are blocked.

But it seems that despite me setting my netmaker connection to private it somehow resets itself - and becomes public again and I find myself not able to access to my ports. With the increase in port scans on my RDP port - I want to block port 3389 on public networks and only allow it via Netmaker but if this issue with Netmaker isn't sorted I will find myself locked out.

Thanks

[yabinma]

@paul19920801 , how you set the interface to private?
try command Set-NetConnectionProfile -InterfaceAlias 'netmaker' -NetworkCategory 'Private'
Also what's the netmaker version in your setup?