I'm unable to fully connect to my new Debian 9 machine (which is running XRDP) using Windows Remote Desktop. As I want to use this machine as a host for virtual machines and run it without display, keyboard or a mouse, I really need the remote desktop facility.

I installed xrdp with:
# apt-get install xrdp

then rebooted the machine. When I try to connect from my Windows 7 laptop using Windows Remote Desktop, I get the following "Connection Log":
connecting to sesman ip 127.0.0.1 port 3350
sesman connect ok
sending login info to session manager, please wait...
login successful for display 10
started connecting
connection problem, giving up
some problem

On the Debian 9 machine, /var/log/xrdp-sesman.log contains the following:
[20180208-18:37:13] [DEBUG] libscp initialized
[20180208-18:37:13] [INFO ] starting xrdp-sesman with pid 1064
[20180208-18:37:13] [INFO ] listening to port 3350 on 127.0.0.1
[20180208-18:38:57] [INFO ] A connection received from ::1 port 34726
[20180208-18:38:58] [INFO ] ++ created session (access granted): username xxxxxxxx, ip 0.0.0.0:51052 - socket: 12
[20180208-18:38:58] [INFO ] starting Xorg session...
[20180208-18:38:58] [DEBUG] Closed socket 9 (AF_INET6 :: port 5910)
[20180208-18:38:58] [DEBUG] Closed socket 9 (AF_INET6 :: port 6010)
[20180208-18:38:58] [DEBUG] Closed socket 9 (AF_INET6 :: port 6210)
[20180208-18:38:58] [DEBUG] Closed socket 8 (AF_INET6 ::1 port 3350)
[20180208-18:38:58] [DEBUG] Closed socket 7 (AF_INET6 ::1 port 3350)
[20180208-18:38:58] [INFO ] Xorg :10 -auth .Xauthority -config xrdp/xorg.conf -noreset -nolisten tcp
[20180208-18:39:08] [ERROR] X server for display 10 startup timeout
[20180208-18:39:08] [INFO ] starting xrdp-sessvc - xpid=1082 - wmpid=1081
[20180208-18:39:08] [ERROR] X server for display 10 startup timeout
[20180208-18:39:08] [ERROR] another Xserver might already be active on display 10 - see log
[20180208-18:39:08] [DEBUG] aborting connection...
[20180208-18:39:08] [INFO ] ++ terminated session: username xxxxxxxx, display :10.0, session_pid 1080, ip 0.0.0.0:51052 - socket: 12

It looks to me as though XRDP is trying to use display 10 twice?

FWIW, I can connect to the Debian machine via SSH without issues.

The Debian machine is a Gigabyte GB-BXBT-2807 with 4GB RAM and a 120GB SSD drive and is running Debian 9 64-bit.

Any help will be gratefully received. Geoff

Have you tried creating a file /etc/X11/Xwrapper.config containing

1 members found this post helpful.

Many thanks -- much appreciated.

/etc/X11/Xwrapper.config contained the line "allowed_users = console". I changed the value to "anybody" and can now connect. However, I now get asked to authenticate to "create a color profile" and also to "create a color managed device". If I enter my password, I get another round of these authentication dialogs and then the session terminates. Clicking "Cancel" for both dialogs allows the session to continue and I get the same UI as I do when logged on at the physical console. I'll do some research to see if I can turn off those dialogs. In the meantime, I'd welcome any hints!

Update: turns out this is a known bug in Gnome 3 (at least in some versions of Fedora). Clicking Cancel in the color management dialogs allows the session to continue and so is a viable workaround.

Thanks again, Geoff

Hello.
Why is xrdp necessary to make the X server launch accessible to everyone? Is it possible to configure the xrdp service without allowing everyone to start X server ?

From 'man Xwrapper.config':
Who can access xrdp can be controlled by settings in etc/xrdp/sesman.ini
So you can assign allowed users to a group (tsusers) and then set AlwaysGroupCheck=true.