Unable to connect to RDP if Windows Desktop Service node name is different from its FQDN about teleport

[zmb3]

This is working as intended, though the error is a bit difficult to interpret because Teleport is trying both direct dial and reverse tunnel connection methods.

In this case, because you've set listen_addr, the desktop service is going to open a port to listen for incoming connections rather than reaching out to establish a reverse tunnel with the proxy.

You haven't set a public_addr to tell the proxy what address to connect to, so the proxy's only choice is to try to dial the node name and hope that it's valid DNS and reachable. This is why things work when you make the node name match the actual hostname.

windows_desktop_service:
  enabled: yes
  listen_addr: 0.0.0.0:3028
  public_addr: 127.0.0.1:3028 # CAREFUL, this only works for single-node clusters