NAT Configuration to access Remote Desktop

Announcements

ATTENTION Customers, All Partners and Employees: The Customer Support Portal (CSP) will be undergoing maintenance and unavailable on Saturday, November 7, 2020, from 11 am to 11 pm PST. Please read our blog for more information.

Reply
Highlighted
L2 Linker

NAT Configuration to access Remote Desktop

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.

Highlighted
L4 Transporter

Hi @feelgood ,

 

Hope you have configured the NAT and security rule properly. refer below doc for help.

https://docs.paloaltonetworks.com/pan-os/8-0/pan-os-admin/networking/nat/nat-configuration-examples/...

Highlighted
L2 Linker

Hi @Abdul_Razaq,

 

Thank you for your answer, I go test that.

Highlighted
Cyber Elite

@feelgood,

While this certainly works I would question why you wouldn't simply give whoever's needs access to this device access through the built in GlobalProtect VPN solution. 

You are still exposing this desktop to the outside world. You might be limiting it via a security policy but the NAT statement is still there. To avoid issues due to a misconfiguration I would recommend against your current approach. 

Highlighted
L2 Linker

@BPry 

We have already GlobalProtect configured on our PanOS but it's for our users. This NAT configuration is for a partner who needs to access an environnement via our public IP address.

 

We don't want grant access at this partner on our VPN access because it's not partitionned correctly at this time.

 

So, the only solution I founded it's this NAT rules restricted on the IP address of this partner.

Highlighted
Cyber Elite

@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. 

Highlighted
L2 Linker

@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.

Highlighted
Cyber Elite

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,

Highlighted
L2 Linker

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.

Highlighted
L2 Linker

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 ?

capture.png

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the Live Community as a whole!

The Live Community thanks you for your participation!