opensource/teleport
3
0
Fork 0
mirror of https://github.com/gravitational/teleport.git synced 2026-09-24 16:17:11 +08:00
Code Issues Packages Projects Releases Wiki Activity

Add "RDP connection fail" section to desktop access troubleshooting docs (#13059)

Browse Source
This commit is contained in:
Łukasz Kozłowski
2022-08-08 21:03:23 +00:00
committed by GitHub
parent 299d1c8301
commit d5a968adfe
1 changed files with 25 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/pages/desktop-access/troubleshooting.mdx
+25 -8
View File
@@ -7,7 +7,7 @@ Common issues and resolution steps.
## Auto-login does not work
### Smart Card Service Not Running
### Smart card service not running
You connect to a Windows host from the Teleport UI, land on the Windows login
screen and nothing happens.
@@ -32,7 +32,7 @@ If the "Smart Card" service is not running, open PowerShell and run
`gpupdate.exe /force`. This forces a Group Policy sync and should pick up the
service changes.
### Smart Card Certificate Not Trusted
### Smart card certificate not trusted
You connect to a Windows host from the Teleport UI, land on the Windows login
screen and see an error message: **"The smartcard certificate used for
@@ -74,9 +74,9 @@ the new CA.
## New session "hangs"
### Host Unreachable
### Host unreachable
You click `CONNECT` on a Windows host from the Teleport UI, a new tab opens but
You click `CONNECT` on a Windows host from the Teleport UI, and a new tab opens, but
nothing is displayed other than the top bar. After a while, an error is
displayed about a failed connection.
@@ -95,7 +95,7 @@ from the Linux server that runs `windows_desktop_service`. If the host is
online but not reachable, there is some other networking barrier in the way,
specific to your infrastructure.
### Hostname Does Not Resolve
### Hostname does not resolve
Connections to Windows Desktops hang during connection establishment, or the
Teleport debug logs show errors of the form
@@ -111,9 +111,26 @@ Ensure that your firewalls allow inbound DNS traffic on port `53` from the
instance(s) running Teleport's Windows Desktop Service to the LDAP server
(Active Directory Domain Controller).
### RDP connection failed
You click `CONNECT` on a Windows host from the Teleport UI, a new tab opens but
nothing is displayed other than the top bar. You see an error that refers to a
failed RDP connection. You may also see errors similar to:
```text
Rdp(Io(Os { code: 54, kind: ConnectionReset, message: "Connection reset by peer" }))
```
**Solution:** Configure a certificate for RDP connections
This means that the desktop does not support secure cipher suites for TLS
connections.
Make sure that you [configure a certificate for RDP connections](./getting-started.mdx#step-47-configure-a-certificate-for-rdp-connections).
## Teleport fails to start
### Incorrect Domain
### Incorrect domain
Teleport fails to start with an error similar to:
@@ -128,7 +145,7 @@ LDAP Result Code 10 "Referral": 0000202B: RefErr: DSID-0310082F, data 0, 1 acces
This means that your domain name is likely wrong. Double-check the `domain`
field in the `ldap` section of `windows_desktop_service`.
### Domain Controller Unreachable
### Domain controller unreachable
Teleport fails to start with an error similar to:
@@ -143,7 +160,7 @@ This means that your Domain Controller is down or unreachable. Double-check the
correct, check that the Domain Controller is up and reachable from the server
that runs `windows_desktop_service`.
### Cannot Initialize LDAP over TLS
### Cannot initialize LDAP over TLS
Teleport fails to connect to LDAP on startup. You may see errors similar to: