Guest User!

You are not Sophos Staff.

This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

RDP from Internal to DMZ not working

Hi UTM Community,

I'm trying to get standard RDP working from our internal network to a server located in our DMZ.

I can ping the server via IP/name from internal no problems.

The rules I've set are (source/protocol/destination) "Internal (network)" - "RDP" - "DMZ (network)" - Allow.
Also tried more a more granular "internal PC" - "RDP" - "Server in DMZ" - Allow.
Finally "Internal (Network)" - "ANY" - "DMZ (network)" - Allow.

None of the above seems to be allowing traffic. Each time I try to connect I get:

13:00:51

Default DROP

TCP

 

10.150.46.3

:

3389

10.150.0.2

:

59868

10.150.46.3 is the server in DMZ I'm trying to RDP to
10.150.0.2 is the workstation in INTERNAL I'm connecting from.

One thing that I’ve noticed in comparing the log with other working rules is the source and destination addresses are the opposite way around. I think this is likely my problem?

For example a rule that IS working is “Server in DMZ” (10.150.46.3) – 32001 – “Server in VS-002” (10.150.2.2) – Allow. The log shows:

12:59:49

Packet filter rule #35

TCP

 

10.150.46.3

:

60481

10.150.2.2

:

32001

On the rule that is failing I would have thought the log should be 10.150.0.2:59868 -> 10.150.46.3:3389

So it appears I’m setting up the rule the wrong way, can anyone point me in the right direction?

Appreciate your help.



This thread was automatically locked due to age.
Parents
  • ICT123 said:
    On the rule that is failing I would have thought the log should be 10.150.0.2:59868 -> 10.150.46.3:3389

    Right.

    You can try to RDP from the server in the DMZ to the Internal-PC to confirm the rule in set in the wrong way.

    Look at the rule definition in the Firewall section, it shows the allowed traffic direction. If the rule looks good then you should verify the RDP service definition. RDP doesn't need to be manually defined in the UTM.It is listed as "Microsoft Remote Desktop (RDP)" in the services list.

    Hope this helps.

Reply
  • ICT123 said:
    On the rule that is failing I would have thought the log should be 10.150.0.2:59868 -> 10.150.46.3:3389

    Right.

    You can try to RDP from the server in the DMZ to the Internal-PC to confirm the rule in set in the wrong way.

    Look at the rule definition in the Firewall section, it shows the allowed traffic direction. If the rule looks good then you should verify the RDP service definition. RDP doesn't need to be manually defined in the UTM.It is listed as "Microsoft Remote Desktop (RDP)" in the services list.

    Hope this helps.

Children
No Data