Link to home
Create AccountLog in
Avatar of PeterSinger
PeterSingerFlag for Australia

asked on

RDP Gateway at a non defult port

I have a RDP gateway setup and have it pointed using a firewall on port 3395 externaly then 3389 internaly.

When I try to use an RDP client from a host externaly, I go to the options/advance/settings/use these RD gateway server settings.

When I put in the gateway address, I cannot put the port number after it as the field will not accept the port number. e.g. address:3395. It will only accept device without the port number.

Of course, I can put a port number in if I just put the port number in the normal connect box, but if I do it at that location, it will not use the cateway.

Any help would  be great.
Avatar of Jackie Man
Jackie Man
Flag of Hong Kong image

Have you added port 3395 in the exception list of the host firewall?
Avatar of PeterSinger

ASKER

Port 3395 works fine through the firewall. Please read the question again.
ASKER CERTIFIED SOLUTION
Avatar of Hypercat (Deb)
Hypercat (Deb)
Flag of United States of America image

Link to home
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
See answer
ok, I understand, thanks.  So can it be changed from port 443?
Your firewall is a physical dedicated one or a broadband router?
A broadband router that can be configured Vigor.
Understood why you cannot use port 3395 externally.

Port 3395 is blocked from the external location where you initiate RDP.

Normally, there are firewall installed in public hotspot, hotel, conference rooms, and it is a not unusual to block ports other than 443, 80, 110, 21, 25, 995, 465.
In short, you cannot change the firewall settings at the locations outside your office or home.
No, the RDP client can't be set to use a different port for the gateway server, as far as I know. The gateway server, by its nature as a web server using SSL, is set to listen on port 443.  If you already have a web server behind your firewall listening on port 443, then you'd need to use a different public IP address for your terminal server. Is that a possibility in your situation?