[SOLVED] Untangle, Open VPN, and RDP question---It's about the ports man

occsean

Active Member
Reaction score
127
Location
Oregon City, OR
I just finished deploying my first Untangle UTM the other day and am now trying to implement remote access for the partners in the firm. I've been able to create the OPEN VPN client, install it on my machine at home, successfully connect to the company LAN and I can ping the machine I want to RDP to by it's internal static IP (although can't ping by hostname). I can also ping the UTM internal LAN interface via it's IP address

But I cannot connect using RDP.
upload_2017-5-3_21-49-13.png

So far I have done the following:

Disabled firewall and antivirus on the target machine, changed connection port in registry from 38000 to 3389, and checked the same registry entry on my machine and made sure it is set for port 3389 as well...

Any ideas or suggestions?

This is also posted over on the Untangle forums in this thread

Thanks in advance for your ideas and help
 
Have you tried to RDP to it from another machine on the local network? That will at least narrow down if the problem is on the host machine or not.
 
  • Like
Reactions: CLC
Have you tried to RDP to it from another machine on the local network? That will at least narrow down if the problem is on the host machine or not.

Someone had suggested that to me over on the UT forums..Unfortunately, I can't try that tonight as I don't have alternative remote access set up on any other machines there (I use teamviewer)..However I did remote into the original target machine using TV and attempted using RDP on the local LAN to get to several other local machines with no luck....I'll try your suggestion when I go onsite tomorrow morning...thanks!!
 
Going to mark as solved but leave up in case someone else has this issue later on....

Rob of NexGen made a suggestion over in the UT forums that fixed it all up..

Port had been set for 38000 for RDP...I changed the registry to reflect port 3389. Since I had not restarted machine port 38000 was still active as RDP port and IP address:38000 connected right away...
 
Deep dark secret: you can actually have multiple ports listening for RDP. Requires just a bit of registry editing, basically you export the RDP-TCP definition, then in the .reg file change the name and specify the additional port, then re-import.

I'm not sure if I've ever done this on anything newer than 2003 though. Probably on 2008, but can't confirm that.

See: https://serverfault.com/questions/528639/remote-desktop-listen-on-2-different-ports or various discussions in the past on petri.co.il
 
Back
Top