I’m starting a job of my unattended robot, and I get a message that my domain is not available.
Hi @Manuel_Sori
How have you passed the username?
Check the below thread to pass the username like below.
Regards
Hello!
I’m doing exactly the same steps that the video,
Can you check if the port 3389 is open on the robot machine?
What is the value for whoami in the robot VM?
What is the setup in Robot Settings in Orchestrator → Tenant → Manage Access for your robot. I am interested to see the Login To Console setup. Robot - Windows Sessions
STATUS_NO_LOGON_SERVERS
Active Directory authentication server : No logon servers are currently available. Device could not connect to any domain controller of the domain. STATUS_NO_LOGON_SERVERS - The domain controller was not reachable/resolvable. Possible failure reason are DNS forwarder configurations issues, Invalid entries in HOST file, Network issues etc.
More information: Domain controller is not functioning correctly - Windows Server | Microsoft Learn
Hello Marian,
There is no VM robot, it is in my main machine, the whoami is: centralad\msoriano.
My setup is:
How can i show u the Login To Console setup?
Hello Marian,
If I cannot open port 3389 for business reasons, could I open and configure another port so the connection can be made?
Thank you,
All the best
Port 3389 is the only one supported for RDP automation, which is needed for HD Robots access. Choosing a custom port is not currently possible.
The path is HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp\PortNumber
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.