|
|
Question : Remote Assistance: How to connect using non-standard RDP Port
|
|
I have a few users that use Remote Desktop from home. For security, we have changed the default RDP port on these machines to something else other than the standard 3389. Port 3389 is blocked from the Internet.
I have recently setup Group Policy to Allow specific users/groups to Offer Remote assistance without having to use invitations. (GP:CompConf\AdminTemplates\System\Remote Assist\)
From what I understand, the Remote Assistance features uses port 3389 just as Remote Desktop does. This is fine with the pc's using the standard RDP port (within the internal network)- but the PCs that have a different port number for RDP will not connect.
At the following screen (paste into IE): hcp://CN=Microsoft%20Corporation,L=Redmond,S=Washington,C=US/Remote%20Assistance/Escalation/Unsolicited/Unsolicitedrcui.htm
I try to enter the address as eg. OFFICE5:10999 (10999 is a non-standard port number set for RDP). or even 192.168.2.50:10999 and the Remote Assistance window tells me that the machine does not exist.
Any ideas as to how I could work around this by still keeping the non-standard port and being able to use Remote Assistance too?
Can RDP be set to use two different port numbers?
|
Answer : Remote Assistance: How to connect using non-standard RDP Port
|
|
You could set port triggering that traffic on 10999 forwards to the standard port on your firewall.
|
|
|
|
|