Problem Summary
If you are trying to access a machine via RDP and the error message above appears, it means that your connection arrived at the VaultOne connector, but the connector could not find the destination machine
Solution
To solve this error, follow the steps below, if you have any questions, please contact our support team.
First step:
Access the machine where the connector is installed and type the command below, using the ROOT user. The status of the 4 containers must be “Up” as shown in the print below.
docker ps -a
If any container down appears, please contact us via email: [email protected]
Second step:
Do a TELNET to the target machine from the Linux server where the connector is installed. This command validates whether there is communication between the Connector server and the machine that will be accessed. On the machine where the connector is installed, type the command below.
telnet (IP or target machine name, as registered in VaultOne) (Port)
An example of a successful TELNET:
Third step:
If the connection via telnet was made, but the error still persists, you must validate the information below within your platform.
- Check if the credential was registered with the correct user and password.
- On the “Edit Credential” screen, as shown in the image below, check whether it is necessary to register the domain user for this credential.
- On the “Edit server” screen, validate which security protocol is being used for that connection.
Note: Some Windows OS accept the NLA protocol by default, if you are using another one, try connecting via the NLA protocol. Remembering that to use the NLA, that resource needs to have a credential registered within VaultOne.
How to extract logs from the Connector
If all these validations were done and the error still persists, then you must send the connections logs to our support team.
In the Linux server where the Connector is installed, activate the DEBUG mode, to enable this mode type these commands below:
docker rm -f vo-core >/dev/null
docker run -e GUACD_LOG_LEVEL=debug --restart unless-stopped --name vo-core -v vostore:/mntstorage -v /tmp:/mnttemp -d voconnect/core:v6
Done! With the DEBUG mode on, you can extract the connections logs, to do that enter the command below:
docker logs --details -n 200 vo-core |& tee (WRITE FILE NAME AND EXTENSION)
For example:
docker logs --details -n 200 vo-core |& tee log_server.txt
Send the generated file to [email protected], informing us of the problem you are facing, shortly the technical team will contact you.