You are not logged in.

#1 2016-12-06 19:59:57

zanshin
Member
Registered: 2016-12-06
Posts: 1

xrdp + VNC not working

I have a fresh Arch Linux installation,

    [0s] $ uname -a
    Linux fermata 4.8.11-1-ARCH #1 SMP PREEMPT Sun Nov 27 09:26:14 CET 2016 x86_64 GNU/Linux
   

on to which I've installed, enabled, and started xrdp:

    systemctl --type="server"
    ...
    xrdp-sesman.service     loaded active running xrdp session manager
    xrdp.service            loaded active running xrdp daemon

I also have vncserver running on :0

    [0s] $ vncserver -list

    TigerVNC server sessions:

    X DISPLAY # PROCESS ID
    :0          615

Here are the ports that are being listened to:

    [0s] $ sudo lsof -Pi | grep LISTEN
    ...
    sshd       361 root    3u  IPv4  15595      0t0  TCP *:22 (LISTEN)
    sshd       361 root    4u  IPv6  15597      0t0  TCP *:22 (LISTEN)
    xrdp-sesm  370 root    7u  IPv4  15228      0t0  TCP localhost.localdomain:3350 (LISTEN)
    xrdp       375 root    7u  IPv4  16056      0t0  TCP *:3389 (LISTEN)
    Xvnc       615 mark    4u  IPv4  14285      0t0  TCP *:5900 (LISTEN)
    Xvnc       615 mark    5u  IPv6  14286      0t0  TCP *:5900 (LISTEN)
    ...

I'm trying to connect to the Arch box from macOS Sierra, so I downloaded and installed Microsoft Remote Desktop (Version 8.0.36 (Build 27228)) and created a profile that specifies the IP address of the Arch box, and has my Arch user account and password.

When I try to connect I get a grey box with the following messages:

    connecting to sesman ip 127.0.0.1 port 3350
    sesman connect ok
    sending login info to session manager, please wait...
    xrdp_mm_process_login_response: login successful for display 10
    VNC started connecting
    VNC connecting to 127.0.0.1 5910
    VNC error - problem connecting

I noted that the login was successful for display 10, and thinking that I needed to have VNC operating on :10 rather than :0, I killed the :0 session and stated a new on on :10. I get the same error as above with the line

    ...
    xrdp_mm_process_login_response: login successful for display 11
    ...

Here is the output from the journal:

    [0s] $ journalctl -f -u xrdp
    -- Logs begin at Sat 2016-12-03 20:28:10 CST. --
    Dec 06 08:05:25 fermata XRDP[4451]: (4451)(139899817027328)[DEBUG] VNC Error after security negotiation
    Dec 06 08:05:25 fermata XRDP[4451]: (4451)(139899817027328)[DEBUG] VNC error before sending share flag
    Dec 06 08:05:25 fermata XRDP[4451]: (4451)(139899817027328)[DEBUG] VNC error before receiving server init
    Dec 06 08:05:25 fermata XRDP[4451]: (4451)(139899817027328)[DEBUG] VNC error before receiving pixel format
    Dec 06 08:05:25 fermata XRDP[4451]: (4451)(139899817027328)[DEBUG] VNC error before receiving name length
    Dec 06 08:05:25 fermata XRDP[4451]: (4451)(139899817027328)[DEBUG] VNC error before receiving name
    Dec 06 08:05:25 fermata XRDP[4451]: (4451)(139899817027328)[DEBUG] xrdp_mm_module_cleanup
    Dec 06 08:05:25 fermata XRDP[4451]: (4451)(139899817027328)[DEBUG] VNC mod_exit
    Dec 06 08:05:25 fermata XRDP[4451]: (4451)(139899817027328)[INFO ] An established connection closed to endpoint: NULL:NULL - socket: 12
    Dec 06 08:05:25 fermata XRDP[4451]: (4451)(139899817027328)[INFO ] An established connection closed to endpoint: 127.0.0.1:3350 - socket: 11

iptables is empty:

    [3s] $ sudo iptables -L
    Chain INPUT (policy ACCEPT)
    target     prot opt source               destination

    Chain FORWARD (policy ACCEPT)
    target     prot opt source               destination

    Chain OUTPUT (policy ACCEPT)
    target     prot opt source               destination

Along the way I have added both a .Xclient and a .xsession file to my home directory, and tried gnome-session and i3-session in those files. Eventually I renamed `.xsession` to `.xsessionrc`.

I also made a backup copy of /etc/xrdp/startwm and changed the original to have just

    #!/bin/sh
    gnome-session

I've also tried i3-session and xfce-session here, those being the other environments installed. To simplify things I'm currently just trying to get xterm to start in the VNC session.

When I tail `.vnc/fermata:10.log` I see this:

    ** (nm-applet:4314): WARNING **: atk-bridge: GetRegisteredEvents returned message with unknown signature
    ** (nm-applet:4314): WARNING **: AT-SPI: Could not obtain desktop path or name
    ** (nm-applet:4314): WARNING **: AT-SPI: Could not obtain desktop path or name

    polybars launched...
    polybar|error  Monitor "HDMI2" not found or disconnected
    polybar|error  Monitor "HDMI2" not found or disconnected
 

   
polybar is part of my i3 setup, so VNC at least is pointing to the session I ultimately want.

After reading about xrdp on the Arch Wiki, I installed vino and added it's configuration to the xrdp.ini file. That made no difference.

Further reading showed me that I probably don't want or need to start vncserver, that xrdp will do that on its own, so I stopped the vncserver session and tried again, with the same results.

I am getting from my remote machine to the Arch machine, but xrdp and VNC aren't speaking to one another.

What do I need to configure to couple the two together?

Offline

Board footer

Powered by FluxBB