Orchestrator Login To Console = No + RDP Port Number

Help Orchestrator
,
1

Hello guys!

How are you?

Recently, for security reasons, we changed the RDP port number from 3389 to another number.

However, our scheduled processes stopped working. We use the Orchestrator option: Login To Console = No.

I would like to know how should I proceed to change old RDP port to the new one?

Thank you very much!

1 Like
2

If you are using Console:False / Login To Console = No than

  1. Orchestrator communicates with the Robot Service using HTTPS / SignalR and waits/listens for commands
  2. The Robot Service (Local to the Robot Machine) spawns a Windows Session through RDP.
  3. Spawns Robot Executor
  4. Executes Process with IPC Communication (Named Pipes)

RDP is not used between Orchestrator and the Robot’s host machine

Please see Robot - Windows Sessions for more in-depth details.

Are you presented with an error?

I did give it a try with one of my sandbox environments and a Robot in a Modern Folder. After adjusting the Listening RDP on the Robot’s Host Machine to 3390 followed by a Restart. When attempting to start a job it faults with the following message.

Could not start executor. Rdp connection failed: Message: The connection failed at negotiating security settings., Last error: 131084

RemoteException wrapping System.Exception: Could not start executor. Rdp connection failed: Message: The connection failed at negotiating security settings., Last error: 131084

My assumption would be because the RDP / Creation is happening at the local Windows Session, that it would use the port that the OS is configured to listen on. I haven’t found any configuration within UiPath or in the documentation.

Perhaps @Forum_Staff can advise, or you might need to reach out to the Support team via the Customer Portal or Technical Support Form.

1 Like
3

Thanks for the reply, Tim.

Exactly, we had the same problem (131084) after changing the RDP port.

We also didn’t find any specific documents about it.

We have contacted the UiPath representative and are awaiting a response.

Any news, I’ll let you know.

1 Like
4

Hi,
Our hosting provider had a non standard port for RDP.

After extensive discussions with UiPath support, there is no current capability to get UiPath to use a port other than 3389.

I am pleased to share that we have found a solution !

Use a CMD window and use netsh commands.
This allows the UiPath code on the server to make its outbound connection request on port 3389 and have it re-routed to another port e.g. 3489.

netsh interface portproxy add v4tov4 listenport=3389 listenaddress=WIN-Machinename connectport=3489 connectaddress=WIN-Machinename

Where WIN-Machinename is the name of the machine.

You can check the rule using:

netsh interface portproxy show all

I hope this information is of use to others.

Dave