NAT Configuration to access Remote Desktop

[feelgood]

Hi,

We need to configure an input rule to authorize an public IP address to access at one of our virtual machine on our subnet.

Concretely, I need to authorize public IP address 195.193.194.195 access directly to our virtual machine with the private IP 192.168.1.1 on the port 3389 (Remote Desktop) only via our public IP address (82.83.84.85).

I configured a NAT rule but it didn't work. May be I doing something wrong ?

Can you help us about this topic ?

Thank you for your help.

[BPry]

@feelgood,

This is a "quick" solution to the problem, but I would seriously look at getting GlobalProtect in a good working state to allow Vendor solutions access to select machines rather than a NAT solution. You already have GlobalProtect exposed to the outside and this solution is just adding another entry point into your network. It might be secure by a source address, but one small configuration mistake would open it up to anyone. 

Just my two cents, clearly either is a viable solution. 

[feelgood]

@BPry 

Thanks for your advices. We need to grant access to partner this week so I need a quick solution. But we are aware that is a dirty solution and we need to more secure our GlobalProtect access in the future.

[OtakarKlier]

Hello,

RDP is unsecure and I do not recommend you use it over the internet. Please use a secure channel like one Bpry suggeted.

Regards,

[feelgood]

Hi @OtakarKlier @BPry 

I reconsider my position and you're wright, it's so dangerous to expose RDP on Internet.

So, I search other solution without VPN (for the moment). May be a VNC solution.

[feelgood]

Finally, I think to segregate subnets ont my GlobalProtect configuration but I have a question : Can I apply different segregation by users or users group ?