Tunnels Openvpn - Lan to lan - Nethserver 7.9, port open 3389 server windows, red client

[polcrito (pol criollo)]

My greetings.
I mention that I have a configuration of an openvpn tunnel in netserver 7.9, on one side you have public ips (server) and on the other side only private ips (client), as vpn everything works excellent.
The need is that I want to open port 3389 on a windows server that is on the client network side, where I only have private ips, internally I can open port 3389 of the windows server that is on the other side, but when I access the internet with a public ip through PORT FORWARD I can’t access.
Any ideas to fix this configuration.
They are thanked.
Att.

PAUL CRIOLLO

[mrmarkuz (Markus Neuberger)]

Did you already exclude firewall issues on the Windows server itself?

You may check the network traffic with tcpdump:

Port forwarding is not opening ports

Hi to all. I’m trying to configure nethserver 7.2 and I need port forwarding to use with internal web server. I configured the red and green interface. I can reach the server form the outside on port 980 (httpd-admin). I can surf the internet and every seems normal. But when I try to configure port forwarding the server just won’t open the port. I need to know of there is something more I need to do besides creating the configuration in Gateway > Port Forwarding. The documentation looks very…

Please secure the public RDP connection as good as possible (SSL, 2FA). As an alternative you may use a roadwarrior openvpn for internet clients to access the Windows Server.

[royceb (Royce)]

@mrmarkuz

Please secure the public RDP connection as good as possible (SSL, 2FA). As an alternative you may use a roadwarrior openvpn for internet clients to access the Windows Server.

You could also consider using Guacamole or MeshCentral for remote access/management of your clients and not expose anything related publicly.