RDP NAT connection issue?
cancel
Showing results for 
Search instead for 
Did you mean: 

RDP NAT connection issue?

L4 Transporter

Hi folks,

 

For test purposes, I am trying to get RDP to work going through my PA-200 OS 6.1.4 to an internal PC.

I've been following several articles like this one, but not getting it to work.

https://live.paloaltonetworks.com/t5/General-Topics/MS-RDP-NAT-Issue/m-p/15217/thread-id/11171/highl...

 

I must be doing something wrong since my internet access rules are working fine.

Anyone see anything in my rules that look wrong?

 

RDPNAT.jpg

 

RDPsecurity.jpg

 

 

1 ACCEPTED SOLUTION

Accepted Solutions

I disagree.

Your Security Policy does NOT need to include internal IP.

As first is done NAT evaluation. This will tell firewall where packet needs to go to.

Then security policy is checked.

And last NAT is applied - just before packet is sent out to wire.

So security policy is checked when packet still has original IP but destination zone has already been changed in packet metadata.

Enterprise Architect @ Cloud Carib www.cloudcarib.com
ACE, PCNSE, PCNSI

View solution in original post

7 REPLIES 7

L7 Applicator

Hey your second line shows your IP so no reason to hide it in first one.

NAT screenshot does not show right column that should include RDP server internal ip. So can't validate if this is there.

 

Other thing you can try is to enable bi-directional checkbox on second NAT rule. This will do the trick also create hidden NAT rule for incoming RDP traffic).

Hidden NAT policy is visible in CLI "show running nat-policy"

Enterprise Architect @ Cloud Carib www.cloudcarib.com
ACE, PCNSE, PCNSI

L4 Transporter

--- removed  ---

--
CCNA Security, PCNSE7

I disagree.

Your Security Policy does NOT need to include internal IP.

As first is done NAT evaluation. This will tell firewall where packet needs to go to.

Then security policy is checked.

And last NAT is applied - just before packet is sent out to wire.

So security policy is checked when packet still has original IP but destination zone has already been changed in packet metadata.

Enterprise Architect @ Cloud Carib www.cloudcarib.com
ACE, PCNSE, PCNSI

View solution in original post

In my experience Raido is correct. 

you are correct. I completely reversed the policies. I confused myself. apologies.

--
CCNA Security, PCNSE7

Thanks folks! 

 

I will follow up and update this post later this evening.

This is my diagram trying to accomplish.

RDPdiag.jpg

 

Ok, got it!  Thank you for the feedback!

 

I forgot to adjust my gateway on internal server.  Also do not need a bi-directional NAT rule.  Just D-NAT and Internet S-NAT.

 

For the record, my correct rules below.

RDPsuccess1.jpg

 

RDPsuccess2.jpg

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 LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!