Cannot connect with mstsc

[jaroklima]

When I install xrdp-init on a clean Ubuntu 18.04 LTS or Xubuntu 18.04 and connect with the Hyper-V client, everything works fine (resolution, clipboard) except for some error dialogs shortly after gnome (or xfce) starts. But I'm not able to connect using MSTSC - there is nothing listening on port 3389. Is this supposed to work or is RDP server on port 3389 a different problem?

Error dialog after XFCE starts:

light-locker crashed with signal 5 in g_type_create_instance()

From xrdp.log:

[20180506-16:27:26] [DEBUG] Testing if xrdp can listen on 0.0.0.0 port 3389.
[20180506-16:27:26] [DEBUG] Closed socket 7 (AF_INET6 :: port 3389)
[20180506-16:27:28] [INFO ] starting xrdp with pid 764
[20180506-16:27:28] [INFO ] listening to port 3389 on 0.0.0.0
[20180506-16:29:28] [INFO ] Socket 12: AF_VSOCK connection received from cid: -1 port: -2147483648
[20180506-16:29:28] [DEBUG] Closed socket 12 (AF_VSOCK cid -1 port 3389)
[20180506-16:29:28] [DEBUG] Closed socket 11 (AF_VSOCK cid -1 port 3389)
[20180506-16:29:28] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[20180506-16:29:28] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[20180506-16:29:28] [ERROR] Cannot read private key file /etc/xrdp/key.pem: Permission denied
[20180506-16:29:28] [DEBUG] TLSv1.2 enabled
[20180506-16:29:28] [DEBUG] TLSv1.1 enabled
[20180506-16:29:28] [DEBUG] TLSv1 enabled
[20180506-16:29:28] [DEBUG] Security layer: requested 11, selected 0
[20180506-16:29:28] [DEBUG] Closed socket 12 (AF_VSOCK cid -1 port 3389)
[20180506-16:29:28] [INFO ] Socket 12: AF_VSOCK connection received from cid: -1 port: -2147483647
[20180506-16:29:28] [DEBUG] Closed socket 12 (AF_VSOCK cid -1 port 3389)
[20180506-16:29:28] [DEBUG] Closed socket 11 (AF_VSOCK cid -1 port 3389)

I can fix the [ERROR] by adding user xrdp to group ssl-cert but it doesn't seem to matter.

Open ports:

$ sudo netstat -tulpn
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    
tcp        0      0 127.0.0.53:53           0.0.0.0:*               LISTEN      517/systemd-resolve 
tcp        0      0 127.0.0.1:631           0.0.0.0:*               LISTEN      664/cupsd           
tcp6       0      0 ::1:3350                :::*                    LISTEN      739/xrdp-sesman     
tcp6       0      0 ::1:631                 :::*                    LISTEN      664/cupsd           
udp    48384      0 127.0.0.53:53           0.0.0.0:*                           517/systemd-resolve 
udp     1024      0 0.0.0.0:68              0.0.0.0:*                           757/dhclient        
udp        0      0 0.0.0.0:43467           0.0.0.0:*                           633/avahi-daemon: r 
udp        0      0 0.0.0.0:631             0.0.0.0:*                           672/cups-browsed    
udp    42752      0 0.0.0.0:5353            0.0.0.0:*                           633/avahi-daemon: r 
udp6       0      0 :::49530                :::*                                633/avahi-daemon: r 
udp6   19200      0 :::5353                 :::*                                633/avahi-daemon: r 

[jterry75]

Unfortunately, xrdp does not bind to multiple endpoints at the same time like TermSrv. So when the script changes the config to use hv_socket for the transport you can no longer make a tcp connection to this guest. I will open an issue on xrdp and ask about adding support for multiple endpoints.

[jterry75]

xrdp Ref: 1124

[jwgmeligmeyling]

@jterry75 If you disable vsock again, will you still be able use enhanced mode or Remote FX through a plain RDP client? (See also https://c-nergy.be/blog/?p=12429 as referenced by neutrinolabs/xrdp#1260 (comment) )