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

Connecting RDC To External Address BY IP ONLY

I have a requirement to connect to an external Remote Desktop Console (RDC) via an IP address and non-std port (5588). I can perform a successful
NSLOOKUP from the UTM to the external address. When attempting an NSLOOKUP from my machine it goes to the UTM then dies, but that is most likely because of the ICMP settings.

I have monitored the logs for everything I can think of and cannot find the drop.

Firewall Rule: Internal VLANS > any> Internet IPV4
DNS Set up per recommendations on this forum.

What do I need to configure to allow this traffic

This thread was automatically locked due to age.

Parents

0 Yogi_Bear_79 over 10 years ago

An TRACERT from my Client goes: to the UTM, but stops there. MY UTM itself can TRACERT the address. I assumed this was by design and a condition of my ICMP settings on the UTM.
I took this to mean that my machine knows to route via Sophos to the IP in question.

NSLOOKUP from either UTM or Internal nets nothing useful

All I want to do is: Internal --> UTM --> External IP on using RDP via custom port 5588

What I don't understand is no log contains any record of a drop or any type of communication for this req.
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 Yogi_Bear_79 over 10 years ago

An TRACERT from my Client goes: to the UTM, but stops there. MY UTM itself can TRACERT the address. I assumed this was by design and a condition of my ICMP settings on the UTM.
I took this to mean that my machine knows to route via Sophos to the IP in question.

NSLOOKUP from either UTM or Internal nets nothing useful

All I want to do is: Internal --> UTM --> External IP on using RDP via custom port 5588

What I don't understand is no log contains any record of a drop or any type of communication for this req.
Cancel
Vote Up 0 Vote Down

Cancel

Children

No Data