Xrdp vnc error problem connecting some problem

I am running into another issue where the XRDP is not working. I have been at it for quite some time now and I think that I need help. I believe that it is an issue of the Ubuntu machine not listen...

It’s not worth it — there is a better & less painful solution:

X11VNC

I spent at least 8 hours fighting the battle to connect from Windows 10 to Ubuntu 16 via xrpd and Windows rdp. I tried endless «solutions» that I found posted all over the web. I made progress, but never managed to fully solve it. Even if I had, though, it seems that this is weak setup anyway, because:

  • You can’t use the Unity Desktop, so your rdp has connect you to a completely different OS UI than what you would use as the Ubuntu standard.
  • You can’t be logged on already with that account. So if you were have a scenerio where sometimes you work directly on the Ubuntu machine, and sometimes you connect remotely, you’d have to be sure to log out to allow for that remote connection.
  • From what’ve read, once you have this, you have also fight a battle to get a «re-connection» mechanism working to re-enter an rdp session you left.
  • You have to manually enter credentials every time you log on. There is no way to save them on the client end and just connect instantly.

I’ve used a pile of different remote connection interfaces, and overall nothing beats the ease and quality of Windows RDP yet to my mind. A such, I was pretty fixated on using that. After fighting this long enough though, and finally throwing in the towel, I found that VNC pretty much works just as well in this context.

As I said initially, on the Ubuntu side I used «x11vnc». Refer to these directions for details on getting that fully setup:

How to setup x11vnc to access with graphical login screen?

On the Windows side, I used RealVNC Viewer: https://www.realvnc.com/en/connect/download/viewer/, which I already had installed and setup for a remote connection to a Mac on my LAN as well.

With this setup, I have NONE of the weaknesses outlined above. Further, in full screen mode, the display is just as good as it would be naturally. I see 0 lag, 0 blurring. I have a bi-directional clipboard working without any effort to get that…

In theory, you are supposed to be able to stack xrpd and x11vnc. See: http://c-nergy.be/blog/?p=5956
I tried that too, just to see if I could get it to work. I had no luck with that either. So I just said the hell with xrpd in the end, uninstalled it, and rolled back all the changes I made to my machine fighting with it (or least so of them).

Unless you have a major reason that you NEED RDP instead of VNC, I strongly recommend going this route I’ve described instead.

Источник

Thanks for letting us know — I’m glad we got there between us.

I’ll just summarize and expand on this thread for anyone else reading this, who is trying to get an alternative desktop working on a fresh install of the latest CentOS 7. The webpage you linked to is pretty good, but it’s missing some small details like SELinux support and the need for xorgxrdp. I’ve also added some of my own sysadmin experiences.

At the time of writing, the following versions apply:-

Software Version
CentOS 7.7
xrdp RPM 0.9.11-5
xorgxrdp RPM 0.2.11-1

  • Ensure the OS is up to date with sudo yum update

  • Install EPEL repository with sudo yum install epel-release

  • Install and enable XRDP with:-

    sudo yum install xrdp
sudo systemctl enable --now xrdp
sudo systemctl enable --now xrdp-sesman

  • If you’re using the firewall, allow external access to TCP port 3389 with:-

    sudo firewall-cmd --add-port=3389/tcp --permanent
sudo firewall-cmd --reload

  • If you’re using SELinux, sudo yum install xrdp-selinux

  • If you want to use the Xorg backend in addition to (or instead of) the Xvnc backend, do the following. The differences between the two backends are covered elsewhere.

    • sudo yum install xorgxrdp
    • Edit /etc/xrdp/xrdp.ini. If the [Xorg] section is commented out, uncomment it.
    • If you changed xrdp.ini, sudo systemctl restart xrdp to pick up the changes.

  • Install your desktop(s), making sure that you use a command to install the whole desktop rather than a subset of it. This will probably be a yum groupinstall command. For example, for MATE, use sudo yum groupinstall "MATE Desktop".

  • The default desktop for XRDP on CentOS 7 is GNOME. If you want the default desktop for all XRDP users to be something else, create the file /etc/sysconfig/desktop and set the PREFERRED variable to the command to start the desktop. For example, this /etc/sysconfig/desktop sets the default desktop to MATE for all XRDP users:-

    # This file is read by /etc/X11/xinit/Xclients if the user does not
# override it - see /etc/X11/xinit/Xsession for details

# Set the default desktop for all users
PREFERRED=mate-session

  • XRDP users who want to use a desktop other than the default will need to soft-link the command to start the correct session in to ~/.xsession or ~/.Xclients . For MATE, this command is adequate:-

    ln -sf /usr/bin/mate-session ~/.xsession

    As an aside, some websites suggest creating a vanilla file ~/.xsession containing the command to start the desktop. That’s OK too, but you have to remember to make the file executable. The soft-link method avoids this pitfall.

That should get the desktop running. Here are a couple of gotchas:-

  • Some desktops expect GDM to be running to provide some of their functionality over DBUS. For example, the GNOME lock screen is implemented in GDM. If you’re using one of these desktops you may need to enable GDM on the machine console (if it isn’t enabled already):- 
    sudo yum install gdm
sudo systemctl set-default graphical
sudo systemctl isolate graphical
  • When using the Xvnc backend, you may need to set the colour depth on the client to 24 or 32 if the desktop, or the applications require mesa 3D support. The Xorg backend always runs at a suitable colour depth.

I think that’s it, but please let me know if I’ve left anything out.

Does anyone think this would be useful as a Wiki page by the way?

Источник

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.

Already on GitHub?
Sign in
to your account

Comments

@kristiandrucker

Hi, I have xrdp 0.9.1 on ubuntu 16.04 and I want to connect to kvm vm via vnc using xrdp. When I’m connecting I get

VNC error - problem connecting
some error

Here is the log:

[20170531-09:28:33] [DEBUG] xrdp_wm_log_msg: VNC started connecting
[20170531-09:28:33] [DEBUG] xrdp_wm_log_msg: VNC connecting to localhost 5901
[20170531-09:28:36] [DEBUG] VNC error 1 after security negotiation
[20170531-09:28:36] [DEBUG] VNC error before sending share flag
[20170531-09:28:36] [DEBUG] VNC error before receiving server init
[20170531-09:28:36] [DEBUG] VNC error before receiving pixel format
[20170531-09:28:36] [DEBUG] VNC error before receiving name length
[20170531-09:28:36] [DEBUG] VNC error before receiving name
[20170531-09:28:36] [DEBUG] xrdp_wm_log_msg: VNC error - problem connecting
[20170531-09:28:36] [DEBUG] Closed socket 16 (AF_INET6 :: port 33870)
[20170531-09:28:36] [DEBUG] xrdp_wm_log_msg: some problem
[20170531-09:28:36] [ERROR] xrdp_wm_log_msg: Error connecting to: localhost
[20170531-09:28:36] [DEBUG] xrdp_mm_module_cleanup
[20170531-09:28:36] [DEBUG] VNC mod_exit
[20170531-09:28:36] [DEBUG] return value from xrdp_mm_connect 1

The vnc server should be working, because I was able to connect to it via vnc client.

Please may you help me?

@metalefty

Can you try uncomment delay_ms in xrdp.ini?

@kristiandrucker

@metalefty I did and the same error. This is the section, everything else should be default.

[Xvnc]
name=Xvnc
lib=libvnc.so
username=
password=ask
ip=127.0.0.1
port=ask
#xserverbpp=24
delay_ms=2000

@dean-hunter

I am getting the same error on Fedora 24, 25 and 26 beta.

@metalefty

@dean-hunter

Regarding xorgxrdp, there is no such file /etc/X11/Xwrapper.config.

Regarding SELinux, xrdp-selinux had not been installed. However, the problem persists after installing and restarting the machine.

Regarding #755, I never see a desktop so there is no opportunity to use the clipboard.

…

@dean-hunter

I did update sesman.ini as recommended by #755, but the problem persists.

@dean-hunter

I guess I should mention that I have these versions installed:
tigervnc-server-minimal.x86_64 1.8.0-1.fc26
xorgxrdp.x86_64 0.2.2-1.fc26
xrdp.x86_64 1:0.9.2-12.fc26
xrdp-selinux.x86_64 1:0.9.2-12.fc26

@metalefty

I meant VNC part of README.Fedora. You can ignore other parts. Thanks for version info.

@dean-hunter

I did update the Xvnc stanza of /etc/xrdp/sesman.ini, but the problem persists.

[Xvnc]
param=Xvnc
param=-bs
param=-nolisten
param=tcp
param=-localhost
param=-dpi
param=96
param=-AcceptCutText=0
param=-SendCutText=0
param=-SendPrimary=0
param=-SetPrimary=0

@siepkes

Same as above on CentOS 7.3 (fully patched).

TigerVNC’s version is 1.3.1 on CentOS 7 so the above fixes don’y apply since the Fedora readme indicates it’s for TigerVNC >= 1.8.0. Trying to use them results in a Unrecognized option: -SendPrimary=0.

@metalefty

OK, it turned out that this issue is not identical to #755. Let’s forget everything about #755.

@dean-hunter

Is there any other information you need to help resolve this issue?

@grishin-a

Ubuntu 16.04.2 LTS xrdp 0.9.2

[20170714-15:47:21] [INFO ] xrdp_wm_log_msg: login successful for display 12
[20170714-15:47:21] [DEBUG] xrdp_wm_log_msg: VNC started connecting
[20170714-15:47:21] [DEBUG] xrdp_wm_log_msg: VNC connecting to 127.0.0.1 5912
[20170714-15:47:24] [DEBUG] VNC error 1 after security negotiation
[20170714-15:47:24] [DEBUG] VNC error before sending share flag
[20170714-15:47:24] [DEBUG] VNC error before receiving server init
[20170714-15:47:24] [DEBUG] VNC error before receiving pixel format
[20170714-15:47:24] [DEBUG] VNC error before receiving name length
[20170714-15:47:24] [DEBUG] VNC error before receiving name
[20170714-15:47:24] [DEBUG] xrdp_wm_log_msg: VNC error - problem connecting
[20170714-15:47:24] [DEBUG] Closed socket 25 (AF_INET 0.0.0.0:42388)
[20170714-15:47:24] [DEBUG] xrdp_wm_log_msg: some problem
[20170714-15:47:24] [DEBUG] xrdp_mm_module_cleanup
[20170714-15:47:24] [DEBUG] VNC mod_exit
[20170714-15:47:24] [DEBUG] Closed socket 24 (AF_INET 127.0.0.1:40894)
[20170714-15:47:31] [DEBUG] Closed socket 12 (AF_INET 192.168.125.18:3389)
[20170714-15:47:31] [DEBUG] xrdp_mm_module_cleanup
[20170714-15:47:32] [ERROR] Listening socket is in wrong state, terminating list
ener

https://pastebin.com/u54NN1Wp
Fedora 26 xrdp 0.9.3
firewall/selinux disabled

[20170714-15:39:06] [INFO ] xrdp_wm_log_msg: login successful for display 10
[20170714-15:39:06] [DEBUG] xrdp_wm_log_msg: VNC started connecting
[20170714-15:39:06] [DEBUG] xrdp_wm_log_msg: VNC connecting to 127.0.0.1 5910
[20170714-15:39:09] [DEBUG] VNC error 1 after security negotiation
[20170714-15:39:09] [DEBUG] VNC error before sending share flag
[20170714-15:39:09] [DEBUG] VNC error before receiving server init
[20170714-15:39:09] [DEBUG] VNC error before receiving pixel format
[20170714-15:39:09] [DEBUG] VNC error before receiving name length
[20170714-15:39:09] [DEBUG] VNC error before receiving name
[20170714-15:39:09] [DEBUG] xrdp_wm_log_msg: VNC error - problem connecting
[20170714-15:39:09] [DEBUG] Closed socket 25 (AF_INET 0.0.0.0:50184)
[20170714-15:39:09] [DEBUG] xrdp_wm_log_msg: some problem
[20170714-15:39:09] [DEBUG] xrdp_mm_module_cleanup
[20170714-15:39:09] [DEBUG] VNC mod_exit
[20170714-15:39:09] [DEBUG] Closed socket 24 (AF_INET 127.0.0.1:56708)

https://pastebin.com/fSSJgc9f
On Ubuntu at least Xorg session is working
On Fedora 26 i unsuccessfully tried xrdp 0.9.1, 0.9.2, 0.9.3 — Xorg or Xvnc sessions not working, at least for me.
UPD:
After some more experimenting I’ve found what causing this errors.
Steps to reproduce(I’m using Fedora with «clean» MATE+Lightdm setup):
Install fresh fedora server w/o GUI.
$ sudo dnf groupinstall ‘base-x’ ‘fonts’
$ sudo dnf install mate-desktop mate-control-center mate-terminal mate-settings-daemon caja caja-open-terminal mate-polkit mate-session-manager lightdm-gtk lightdm mate-menus mate-themes mate-panel marco oddjob-mkhomedir xrdp xrdp-selinux
$ sudo authconfig —enablemkhomedir —update
With this setup I stumbled upon:

  • old bug with xrdp mkhomedir and selinux(fast check: nonexisting homedir and setenforce 0)
  • /etc/X11/xinit/Xclients is not spawning mate-session properly

It is not sufficient to install xrdp-selinux package, you should patch, recompile and reinstall xrdp policy:
$ cd /usr/share/doc/xrdp-selinux/
$ sudo cp xrdp.te{,.old}
$ sudo cat << EOF > xrdp.patch

+++ xrdp.te	2017-07-18 12:52:23.413395457 +0300
@@ -4,6 +4,8 @@
         type unconfined_service_t;
         type unconfined_t;
         type xserver_exec_t;
+        type oddjob_t;
+        type oddjob_mkhomedir_exec_t;
         class process transition;
         class file entrypoint;
 }
@@ -11,7 +13,12 @@
 #============= unconfined_service_t ==============
 
 allow unconfined_service_t unconfined_t:process transition;
+allow unconfined_service_t oddjob_mkhomedir_exec_t:file entrypoint;
 
 #============= unconfined_t ==============
 
 allow unconfined_t xserver_exec_t:file entrypoint;
+
+#============= oddjob_t ==============
+
+allow oddjob_t unconfined_service_t:process transition;
 No newline at end of file
EOF

$ sudo patch xrdp.te xrdp.patch
$ sudo checkmodule -M -m -o xrdp.mod xrdp.te
$ sudo semodule_package -o xrdp.pp -m xrdp.mod
$ sudo semodule -i xrdp.pp
Eliminating this two conditions gives me working xrdp with Xvnc session, but much faster Xorg session still gives me [DEBUG] Closed socket 25 (AF_UNIX) errors.
To make Xorg session working properly I have to make additional Xorg.wrap rights adjustments.
After that I have fully working xrdp setup on Fedora 26:
$ sudo rpm -qa | egrep «rdp|^selin»
selinux-policy-3.13.1-260.1.fc26.noarch
selinux-policy-targeted-3.13.1-260.1.fc26.noarch
xrdp-0.9.2-12.fc26.x86_64
xrdp-selinux-0.9.2-12.fc26.x86_64
selinux-policy-minimum-3.13.1-260.1.fc26.noarch
xorgxrdp-0.2.2-1.fc26.x86_64

@dean-hunter

@grishin-a So you started with Fedora 26 Server and added the Mate desktop and Xrdp with the above modifications and it works. I am starting with Fedora 26 Workstation with the default Gnome desktop and adding Xrdp. Do you have any suggestions on what might be missing from my installation?

It sounds like oddjob-mkhomedir creates the home directory for a user when it does not exist. It is not installed with Fedora 26 Workstation. I am only logging-in to Xrdp using local users that I know exist. Do you know whether oddjob-mkhomedir is required in this situation?

@grishin-a

@dean-hunter Sorry for late reply.
No, you don’t need oddjob-mkhomedir if you are absolutely sure your user have existing homedir.
Just tried xrdp with clean Fedora26 Worstation (Gnome desktop)install on virtual machine. It works with both Xorg and Xvnc sessions.
$ sudo rpm -qa | egrep ‘rdp|vnc’
tigervnc-server-minimal-1.8.0-1.fc26.x86_64
tigervnc-license-1.8.0-1.fc26.noarch
gvnc-0.7.1-1.fc26.x86_64
xrdp-0.9.2-12.fc26.x86_64
xorgxrdp-0.2.3-1.fc26.x86_64
gtk-vnc2-0.7.1-1.fc26.x86_64
Can you try to create a new user and connect?
$ sudo useradd -m test
$ sudo echo 123 | passwd —stdin test
$ sudo systemctl stop firewalld; iptables -F
Connect via rdp(I’m using remmina 1.1.0 client) using Xvnc session.
If you want to connect using Xorg session you need to modify Xwrapper.config

@kaustav1996

I am creating a VM in https://my.vultr.com/ . OS :- Ubuntu 17.04
image
getting this error.
the script I run after logging into the terminal of the VM is :—
sudo apt-get update; sudo apt-get -y install lxde ubuntu-gnome-desktop tightvncserver xrdp ; echo lxsession -s LXDE -e LXDE > ~/.xsession ; echo sudo /etc/init.d/xrdp restart ;
.
.
This script works fine for ubuntu 16.04 and ubuntu 14,04. can you tell me what I am doing wrong?

@metalefty

I reproduced the issue. Please wait patiently until the bug is fixed. Not to use VNC is a workaround.

@abrown

@metalefty

I haven’t been able to start work on this issue yet because VNC baked session is discouraged now.
This doesn’t mean we decided that we won’t fix the issue. Request by more users or sponsorship will raise the priority.

@abrown

Not sure if I understand «VNC baked sessions»; perhaps you could explain further? Is @grishin-a’s patch above the fix?

@metalefty

There was a typo, «VNC backed sessions».

@metalefty

His patch fixes home directory creation. It doesn’t fix the connection issue to VNC.

@Turgon-Aran-Gondolin

Any update by now? I encountered the same connection issue to VNC in Fedora 26 with default Gnome Desktop.

@abrown

@metalefty what is the connection issue to VNC? If you describe in more detail perhaps one of us could take a look

@metalefty

Something’s failing lib_mod_connect() in vnc/vnc.c. As the log says, it looks like an issue in security negotiation.I tried to reproduce the issue again but can’t reproduce for me now.

I’d appreciate if someone provides repro.

@metalefty

@abrown The error occurs in this block.

if (error == 0)
{
in_uint32_be(s, i);
g_sprintf(text, «VNC security level is %d (1 = none, 2 = standard)«, i);
v->server_msg(v, text, 0);
if (i == 1) /* none */
{
check_sec_result = 0;
}
else if (i == 2) /* dec the password and the server random */
{
init_stream(s, 8192);
error = trans_force_read_s(v->trans, s, 16);
if (error == 0)
{
init_stream(s, 8192);
if (v->got_guid)
{
char guid_str[64];
g_bytes_to_hexstr(v->guid, 16, guid_str, 64);
rfbHashEncryptBytes(s->data, guid_str);
}
else
{
rfbEncryptBytes(s->data, v->password);
}
s->p += 16;
s_mark_end(s);
error = trans_force_write_s(v->trans, s);
check_sec_result = 1; // not needed
}
}
else if (i == 0)
{
log_message(LOG_LEVEL_DEBUG, «VNC Server will disconnect«);
error = 1;
}
else
{
log_message(LOG_LEVEL_DEBUG, «VNC unsupported security level«);
error = 1;
}
}
}

@benkillin

I experience this issue.

The way I have to require the xrdp server to be configured is to have the following parameters in the config file:

crypt_level=fips
security_layer=rdp

Maybe with those parameters you can reproduce the error.

@marcospedreiro

I know I’m probably an obscure use case, but I’m getting a similar issue with Alpine Linux on Virtualbox. I hope that this info is helpful in finding the root cause of the error. It’s also possible that I’m doing something wrong in which case please let me know.

I am able to get the login prompt, but when I try to login I get the error dialogue:

xrdp_login_error

System Details

  • Host machine is Windows 10
  • Alpine Linux version: alpine-virt-3.7.0-x86_64
  • Virtualbox version: 5.2.4r119785
  • Virtualbox extensions version: 5.2.4r119785

I followed instructions here: https://wiki.alpinelinux.org/wiki/Remote_Desktop_Server

apk add xrdp
apk add xrdp-sesman
apk add vino
# cat  /etc/xrdp/xrdp.ini

[globals]
bitmap_cache=yes
bitmap_compression=yes
port=3389
crypt_level=low
channel_code=1
max_bpp=24

[xrdp1]
name=Vino
lib=libvnc.so
ip=127.0.0.1
port=5900
username=ask
password=ask

In my home directory I have tried with both files:

# cat .Xclients
#!/bin/sh
XFCE="$(which xfce4-session 2>/dev/null)"
exec "$XFCE"
# cat .xsession
xfce4-session

I used ufw to allow inbound traffic on ports 22, 3389, 3350, and 5900

In the /etc/xrdp/startwm.sh script I added:

# cat /etc/xrdp/startwm.sh
#!/bin/sh

#start the window manager
wm_start()
{
# ...removed for brevity... 
  # el
  if [ -r /etc/X11/xinit/Xsession ]; then
    xfce4-session ## <- this is what I added
    . /etc/X11/xinit/Xsession
    exit 0
  fi
# ...removed for brevity...

Logs

# cat /var/log/xrdp.log
[20171223-17:15:31] [INFO ] Socket 12: AF_INET connection received from <ip> port 61045
[20171223-17:15:31] [DEBUG] Closed socket 12 (AF_INET <ip>:3389)
[20171223-17:15:31] [DEBUG] Closed socket 11 (AF_INET 0.0.0.0:3389)
[20171223-17:15:31] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[20171223-17:15:31] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[20171223-17:15:31] [DEBUG] TLSv1.2 enabled
[20171223-17:15:31] [DEBUG] TLSv1.1 enabled
[20171223-17:15:31] [DEBUG] TLSv1 enabled
[20171223-17:15:31] [DEBUG] Security layer: requested 11, selected 1
[20171223-17:15:33] [INFO ] connected client computer name: <name>
[20171223-17:15:33] [INFO ] TLS connection established from <ip> port 61045: TLSv1.2 with cipher ECDHE-RSA-AES256-SHA
[20171223-17:15:33] [DEBUG] xrdp_00000a22_wm_login_mode_event_00000001
[20171223-17:15:33] [INFO ] Loading keymap file /etc/xrdp/km-00000409.ini
[20171223-17:15:33] [WARN ] local keymap file for 0x00000409 found and doesn't match built in keymap, using local keymap file
[20171223-17:15:33] [DEBUG] xrdp_wm_log_msg: connecting to sesman ip 127.0.0.1 port 3350
[20171223-17:15:37] [DEBUG] Closed socket 18 (AF_INET 0.0.0.0:37178)
[20171223-17:15:41] [DEBUG] Closed socket 18 (AF_INET 0.0.0.0:37184)
[20171223-17:15:45] [DEBUG] Closed socket 18 (AF_INET 0.0.0.0:37190)
[20171223-17:15:49] [ERROR] xrdp_wm_log_msg: Error connecting to sesman: 127.0.0.1 port: 3350
[20171223-17:15:49] [DEBUG] Closed socket 18 (AF_INET 0.0.0.0:37196)
[20171223-17:15:49] [DEBUG] return value from xrdp_mm_connect 1
[20171223-17:15:49] [DEBUG] Closed socket 12 (AF_INET <ip>:3389)
[20171223-17:15:49] [DEBUG] xrdp_mm_module_cleanup
[20171223-17:15:49] [ERROR] Listening socket is in wrong state, terminating listener
[20171223-17:15:49] [CORE ] shutting down log subsystem...
[20171223-17:19:01] [DEBUG] Closed socket 11 (AF_INET 0.0.0.0:3389)
[20171223-17:19:01] [CORE ] shutting down log subsystem...

There are no seemingly useful messages in /var/log/xrdp-sesman.log but I did find logs in the /sesman.log file:

[20171223-22:19:30] [DEBUG] xrdp_wm_log_msg: VNC started connecting
[20171223-22:19:30] [DEBUG] xrdp_wm_log_msg: VNC connecting to 127.0.0.1 5900
[20171223-22:19:33] [DEBUG] VNC error 1 after security negotiation
[20171223-22:19:33] [DEBUG] VNC error before sending share flag
[20171223-22:19:33] [DEBUG] VNC error before receiving server init
[20171223-22:19:33] [DEBUG] VNC error before receiving pixel format
[20171223-22:19:33] [DEBUG] VNC error before receiving name length
[20171223-22:19:33] [DEBUG] VNC error before receiving name
[20171223-22:19:33] [DEBUG] xrdp_wm_log_msg: VNC error - problem connecting
[20171223-22:19:33] [DEBUG] Closed socket 16 (AF_INET 0.0.0.0:47422)
[20171223-22:19:33] [DEBUG] xrdp_wm_log_msg: some problem
[20171223-22:19:33] [ERROR] xrdp_wm_log_msg: Error connecting to: 127.0.0.1
[20171223-22:19:33] [DEBUG] xrdp_mm_module_cleanup
[20171223-22:19:33] [DEBUG] VNC mod_exit
[20171223-22:19:33] [DEBUG] return value from xrdp_mm_connect 1
[20171223-22:19:49] [DEBUG] Closed socket 11 (AF_INET <ip>:3389)
[20171223-22:19:49] [DEBUG] xrdp_mm_module_cleanup

@Jared-Harrington-Gibbs

Seems like this is related to issue #847

I had the same error and was able to get xrdp running on kali by simply moving to lxde.

apt install lxde xrdp tigervnc-standalone-server                                                                                                               
sudo update-alternatives --config x-session-manager
  #chose lxsession
service xrdp-sesman start
service xrdp start

Not ideal but better than nothing.
Hope this helps someone like it helped me. :)

Simplified from https://forums.kali.org/showthread.php?34751-How-to-set-up-xrdp-on-the-AWS-Kali-image

@ristillu

I had the same error as the OP but the fortunate position of having two nearly identical servers, one exhibiting the problem and one not. They are both Gigabyte Brix running Centos 7. I set up my xrdp according to this article https://www.itzgeek.com/how-tos/linux/centos-how-tos/install-xrdp-on-centos-7-rhel-7.html
I narrowed my problem down (from this thread and thanks to the previous poster ^) to a Gnome issue. Working server has this list of Gnome packages:

Installed Packages
gnome-abrt.x86_64                                                           0.3.4-8.el7                                           @base  
gnome-bluetooth.x86_64                                                      1:3.20.1-1.el7                                        @base  
gnome-bluetooth-libs.x86_64                                                 1:3.20.1-1.el7                                        @base  
gnome-boxes.x86_64                                                          3.22.4-4.el7                                          @base  
gnome-calculator.x86_64                                                     3.22.3-1.el7                                          @base  
gnome-classic-session.noarch                                                3.26.2-3.el7                                          @base  
gnome-clocks.x86_64                                                         3.22.1-1.el7                                          @base  
gnome-color-manager.x86_64                                                  3.22.2-2.el7                                          @base  
gnome-contacts.x86_64                                                       3.22.1-1.el7                                          @base  
gnome-desktop3.x86_64                                                       3.22.2-2.el7                                          @base  
gnome-dictionary.x86_64                                                     3.20.0-1.el7                                          @base  
gnome-dictionary-libs.x86_64                                                3.20.0-1.el7                                          @base  
gnome-disk-utility.x86_64                                                   3.22.1-1.el7                                          @base  
gnome-font-viewer.x86_64                                                    3.22.0-1.el7                                          @base  
gnome-getting-started-docs.noarch                                           3.22.0-1.el7                                          @base  
gnome-icon-theme.noarch                                                     3.12.0-1.el7                                          @base  
gnome-icon-theme-extras.noarch                                              3.12.0-1.el7                                          @base  
gnome-icon-theme-legacy.noarch                                              3.12.0-1.el7                                          @base  
gnome-icon-theme-symbolic.noarch                                            3.12.0-2.el7                                          @base  
gnome-initial-setup.x86_64                                                  3.22.1-5.el7                                          @base  
gnome-keyring.x86_64                                                        3.20.0-3.el7                                          @base  
gnome-keyring-pam.x86_64                                                    3.20.0-3.el7                                          @base  
gnome-menus.x86_64                                                          3.13.3-3.el7                                          @base  
gnome-online-accounts.x86_64                                                3.26.2-1.el7                                          @base  
gnome-packagekit.x86_64                                                     3.22.1-2.el7                                          @base  
gnome-packagekit-common.x86_64                                              3.22.1-2.el7                                          @base  
gnome-packagekit-installer.x86_64                                           3.22.1-2.el7                                          @base  
gnome-packagekit-updater.x86_64                                             3.22.1-2.el7                                          @base  
gnome-python2.x86_64                                                        2.28.1-14.el7                                         @base  
gnome-python2-canvas.x86_64                                                 2.28.1-14.el7                                         @base  
gnome-screenshot.x86_64                                                     3.22.0-1.el7                                          @base  
gnome-session.x86_64                                                        3.26.1-11.el7                                         @base  
gnome-session-xsession.x86_64                                               3.26.1-11.el7                                         @base  
gnome-settings-daemon.x86_64                                                3.26.2-9.el7                                          @base  
gnome-shell.x86_64                                                          3.26.2-5.el7                                          @base  
gnome-shell-extension-alternate-tab.noarch                                  3.26.2-3.el7                                          @base  
gnome-shell-extension-apps-menu.noarch                                      3.26.2-3.el7                                          @base  
gnome-shell-extension-common.noarch                                         3.26.2-3.el7                                          @base  
gnome-shell-extension-launch-new-instance.noarch                            3.26.2-3.el7                                          @base  
gnome-shell-extension-places-menu.noarch                                    3.26.2-3.el7                                          @base  
gnome-shell-extension-top-icons.noarch                                      3.26.2-3.el7                                          @base  
gnome-shell-extension-user-theme.noarch                                     3.26.2-3.el7                                          @base  
gnome-shell-extension-window-list.noarch                                    3.26.2-3.el7                                          @base  
gnome-software.x86_64                                                       3.22.7-5.el7                                          @base  
gnome-system-log.x86_64                                                     1:3.9.90-3.el7                                        @base  
gnome-system-monitor.x86_64                                                 3.22.2-3.el7                                          @base  
gnome-terminal.x86_64                                                       3.22.1-2.el7                                          @base  
gnome-terminal-nautilus.x86_64                                              3.22.1-2.el7                                          @base  
gnome-themes-standard.x86_64                                                3.22.2-1.el7                                          @base  
gnome-tweak-tool.noarch                                                     3.22.0-1.el7                                          @base  
gnome-user-docs.noarch                                                      3.22.0-1.el7                                          @base  
gnome-video-effects.noarch                                                  0.4.3-1.el7                                           @base  
gnome-weather.noarch                                                        3.26.0-1.el7                                          @base```

and the non-working server had:

Installed Packages
gnome-bluetooth.x86_64                                                    1:3.20.1-1.el7                                      @base  
gnome-bluetooth-libs.x86_64                                               1:3.20.1-1.el7                                      @base  
gnome-desktop3.x86_64                                                     3.22.2-2.el7                                        @base  
gnome-icon-theme.noarch                                                   3.12.0-1.el7                                        @base  
gnome-icon-theme-legacy.noarch                                            3.12.0-1.el7                                        @base  
gnome-keyring.x86_64                                                      3.20.0-3.el7                                        @base  
gnome-keyring-pam.x86_64                                                  3.20.0-3.el7                                        @base  
gnome-online-accounts.x86_64                                              3.22.5-1.el7                                        @base  
gnome-session.x86_64                                                      3.22.3-4.el7                                        @base  
gnome-settings-daemon.x86_64                                              3.22.2-5.el7                                        @base  
gnome-shell.x86_64                                                        3.22.3-17.el7                                       @base  
gnome-themes-standard.x86_64                                              3.22.2-1.el7                                        @base

That must be because they are both headless and when configuring I must have installed a full Gnome group to one and just a minimal one (to configure Xfce and x2go) on the broken one.

I then thought gnome-classic-session looked like a promising omission so I installed it and the list on the broken server now looked like this, with dependencies pulled in:

Installed Packages
gnome-bluetooth.x86_64                                             1:3.20.1-1.el7                              @base  
gnome-bluetooth-libs.x86_64                                        1:3.20.1-1.el7                              @base  
gnome-classic-session.noarch                                       3.26.2-3.el7                                @base  
gnome-desktop3.x86_64                                              3.22.2-2.el7                                @base  
gnome-icon-theme.noarch                                            3.12.0-1.el7                                @base  
gnome-icon-theme-legacy.noarch                                     3.12.0-1.el7                                @base  
gnome-keyring.x86_64                                               3.20.0-3.el7                                @base  
gnome-keyring-pam.x86_64                                           3.20.0-3.el7                                @base  
gnome-menus.x86_64                                                 3.13.3-3.el7                                @base  
gnome-online-accounts.x86_64                                       3.22.5-1.el7                                @base  
gnome-session.x86_64                                               3.22.3-4.el7                                @base  
gnome-settings-daemon.x86_64                                       3.22.2-5.el7                                @base  
gnome-shell.x86_64                                                 3.26.2-5.el7                                @base  
gnome-shell-extension-alternate-tab.noarch                         3.26.2-3.el7                                @base  
gnome-shell-extension-apps-menu.noarch                             3.26.2-3.el7                                @base  
gnome-shell-extension-common.noarch                                3.26.2-3.el7                                @base  
gnome-shell-extension-launch-new-instance.noarch                   3.26.2-3.el7                                @base  
gnome-shell-extension-places-menu.noarch                           3.26.2-3.el7                                @base  
gnome-shell-extension-top-icons.noarch                             3.26.2-3.el7                                @base  
gnome-shell-extension-window-list.noarch                           3.26.2-3.el7                                @base  
gnome-themes-standard.x86_64                                       3.22.2-1.el7                                @base

Now after trying to connect (from a Windows box on the LAN) the RDP connection just died, but logging in to the broken server afterwards gave:

[user@host log]$ sudo cat xrdp.log
...
[20180522-22:43:08] [DEBUG] xrdp_wm_log_msg: VNC started connecting
[20180522-22:43:08] [DEBUG] xrdp_wm_log_msg: VNC connecting to 127.0.0.1 5910
[20180522-22:43:10] [DEBUG] xrdp_wm_log_msg: VNC tcp connected
[20180522-22:43:10] [DEBUG] xrdp_wm_log_msg: VNC security level is 2 (1 = none, 2 = standard)
[20180522-22:43:10] [DEBUG] xrdp_wm_log_msg: VNC password ok
[20180522-22:43:10] [DEBUG] xrdp_wm_log_msg: VNC sending share flag
[20180522-22:43:10] [DEBUG] xrdp_wm_log_msg: VNC receiving server init
[20180522-22:43:10] [DEBUG] xrdp_wm_log_msg: VNC receiving pixel format
[20180522-22:43:10] [DEBUG] xrdp_wm_log_msg: VNC receiving name length
[20180522-22:43:10] [DEBUG] xrdp_wm_log_msg: VNC receiving name
[20180522-22:43:10] [DEBUG] xrdp_wm_log_msg: VNC sending pixel format
[20180522-22:43:10] [DEBUG] xrdp_wm_log_msg: VNC sending encodings
[20180522-22:43:10] [DEBUG] xrdp_wm_log_msg: VNC sending framebuffer update request
[20180522-22:43:10] [DEBUG] xrdp_wm_log_msg: VNC sending cursor
[20180522-22:43:10] [DEBUG] xrdp_wm_log_msg: VNC connection complete, connected ok
[20180522-22:43:10] [INFO ] The following channel is allowed: rdpdr (0)
[20180522-22:43:10] [INFO ] The following channel is allowed: rdpsnd (1)
[20180522-22:43:10] [INFO ] The following channel is allowed: cliprdr (2)
[20180522-22:43:10] [INFO ] The following channel is allowed: drdynvc (3)
[20180522-22:43:10] [DEBUG] The allow channel list now initialized for this session
[20180522-22:43:10] [DEBUG] xrdp_wm_log_msg: connected ok
[20180522-22:43:10] [DEBUG] xrdp_mm_connect_chansrv: chansrv connect successful
[20180522-22:43:10] [DEBUG] Closed socket 18 (AF_INET 127.0.0.1:53214)
[20180522-22:43:10] [DEBUG] Closed socket 20 (AF_UNIX)
[20180522-22:43:10] [DEBUG] Closed socket 12 (AF_INET 10.11.12.55:3389)
[20180522-22:43:10] [DEBUG] xrdp_mm_module_cleanup
[20180522-22:43:10] [DEBUG] VNC mod_exit
[20180522-22:43:10] [DEBUG] Closed socket 19 (AF_INET 127.0.0.1:46278)

So now it was getting past the OP’s (and my original) security error. I upgraded/installed a few individual packages, like:

gnome-session-xsession
gnome-settings-daemon
gnome-initial-setup
gnome-themes-standard
gnome-terminal

and got it to start up but it’s got a full black background, no menus and no terminal option. I’m logging in to it via ssh and the xrdp.log is the same as above, i.e. working. I think the artifacts I’m seeing are Gnome artifacts now. I will install
sudo yum groupinstall 'Server with GUI'
on this machine and cross my fingers rather than continuing to try to piecemeal install what is required but that’ll have to wait until I can bring down the services that are running on the machine without disturbing the dependent clients too much.

@hzhu212

[SOLVED]

I got the same error in CentOS 7.5 with Xfce desktop. I had struggled for several days with no result.

1

Recently, I found a solution coincidentally. I created a CentOS 7.5 virtual machine with «minimal» installation. Then I installed xrdp and started xrdp service, without realizing that I didn’t have any desktop environment. When I attempted to connect the vm from my Windows, I got definitely the same error stated above.

Soon, I found my stupid mistake, followed by a strange thing: whether installing a desktop environment or not, xrdp always throws the same error. I realized the cause of this issue is not a bug of xrdp, tigervnc-server or Xfce, but the fact that xrdp doesn’t know what desktop environment to start, let alone how to start. It’s the real problem, and we can fix it easily.

Here were my steps:

# generate a file called .xsession in your home directory, and set default desktop
echo "xfce4-session" > ~/.xsession

# enable execute
chmod a+x ~/.xsession

# restart xrdp service
systemctl restart xrdp

# Hint: It works too if you replace `.xsession` with `.Xclients`

Now, xrdp works perfectly with Xfce and openbox.

Finally, where did I get these names? like ~/.xsession and ~/.Xclients?

Well, I found all these in the following scripts:

  • startwm.sh
  • Xsession
  • Xclients

Hint: you have to search the location of these files for different platforms

For example, the last part of /etc/X11/xinit/Xsession in CentOS 7.5 says:

# otherwise, take default action
if [ -x "$HOME/.xsession" ]; then
    exec -l $SHELL -c "$CK_XINIT_SESSION $SSH_AGENT $HOME/.xsession"
elif [ -x "$HOME/.Xclients" ]; then
    exec -l $SHELL -c "$CK_XINIT_SESSION $SSH_AGENT $HOME/.Xclients"
elif [ -x /etc/X11/xinit/Xclients ]; then
    exec -l $SHELL -c "$CK_XINIT_SESSION $SSH_AGENT /etc/X11/xinit/Xclients"
else
    # should never get here; failsafe fallback
    exec -l $SHELL -c "xsm"
fi

Apparently, X11 will search $HOME/.xsession and $HOME/.Xclients for desktop environments.

mechgt, inarighas, xiandew, juliovn, speedpacer, mervynzhang, swvajanyatek, Android0x7, berenddeboer, Birdchen, and hyj-kim reacted with thumbs up emoji
TonyApuzzo, Steffen911, qiaohaijun, myallxiami, jbeetz, sizious, inarighas, xiandew, juliovn, mervynzhang, and whbean reacted with hooray emoji

@whbean

Thank you hzhu212, not only for the fix but also for the clear explanation of what the problem was. Most helpful.

@penghzhang

Hi metalefty ,
I have followed hzhu212’s steps, but this issue still exist on my system, the log file shows below information:
[20190817-03:14:17] [INFO ] xrdp_wm_log_msg: login successful for display 13
[20190817-03:14:17] [DEBUG] xrdp_wm_log_msg: VNC started connecting
[20190817-03:14:17] [DEBUG] xrdp_wm_log_msg: VNC connecting to 127.0.0.1 5913
[20190817-03:14:20] [DEBUG] VNC error 1 after security negotiation
[20190817-03:14:20] [DEBUG] VNC error before sending share flag
[20190817-03:14:20] [DEBUG] VNC error before receiving server init
[20190817-03:14:20] [DEBUG] VNC error before receiving pixel format
[20190817-03:14:20] [DEBUG] VNC error before receiving name length
[20190817-03:14:20] [DEBUG] VNC error before receiving name
[20190817-03:14:20] [DEBUG] xrdp_wm_log_msg: VNC error — problem connecting
Could help me further?
Thanks!

@Android0x7

[SOLVED]

I got the same error in CentOS 7.5 with Xfce desktop. I had struggled for several days with no result.

1

Recently, I found a solution coincidentally. I created a CentOS 7.5 virtual machine with «minimal» installation. Then I installed xrdp and started xrdp service, without realizing that I didn’t have any desktop environment. When I attempted to connect the vm from my Windows, I got definitely the same error stated above.

Soon, I found my stupid mistake, followed by a strange thing: whether installing a desktop environment or not, xrdp always throws the same error. I realized the cause of this issue is not a bug of xrdp, tigervnc-server or Xfce, but the fact that xrdp doesn’t know what desktop environment to start, let alone how to start. It’s the real problem, and we can fix it easily.

Here were my steps:

# generate a file called .xsession in your home directory, and set default desktop
echo "xfce4-session" > ~/.xsession

# enable execute
chmod a+x ~/.xsession

# restart xrdp service
systemctl restart xrdp

# Hint: It works too if you replace `.xsession` with `.Xclients`

Now, xrdp works perfectly with Xfce and openbox.

Finally, where did I get these names? like ~/.xsession and ~/.Xclients?

Well, I found all these in the following scripts:

  • startwm.sh
  • Xsession
  • Xclients

Hint: you have to search the location of these files for different platforms

For example, the last part of /etc/X11/xinit/Xsession in CentOS 7.5 says:

# otherwise, take default action
if [ -x "$HOME/.xsession" ]; then
    exec -l $SHELL -c "$CK_XINIT_SESSION $SSH_AGENT $HOME/.xsession"
elif [ -x "$HOME/.Xclients" ]; then
    exec -l $SHELL -c "$CK_XINIT_SESSION $SSH_AGENT $HOME/.Xclients"
elif [ -x /etc/X11/xinit/Xclients ]; then
    exec -l $SHELL -c "$CK_XINIT_SESSION $SSH_AGENT /etc/X11/xinit/Xclients"
else
    # should never get here; failsafe fallback
    exec -l $SHELL -c "xsm"
fi

Apparently, X11 will search $HOME/.xsession and $HOME/.Xclients for desktop environments.

Great Man …
~/.xsession did the trick for me !

@anandbibek

Not sure if this would apply for a lot of people, but I was having the following errors is log

[20200625-23:04:05] [INFO ] A connection received from 127.0.0.1 port 52386
[20200625-23:04:05] [INFO ] ++ created session (access granted): username root, ip 195.233.142.182:65160 - socket: 12
[20200625-23:04:05] [INFO ] starting Xvnc session...
[20200625-23:04:05] [DEBUG] Closed socket 10 (AF_INET 0.0.0.0:5911)
[20200625-23:04:05] [DEBUG] Closed socket 10 (AF_INET 0.0.0.0:6011)
[20200625-23:04:05] [DEBUG] Closed socket 10 (AF_INET 0.0.0.0:6211)
[20200625-23:04:05] [DEBUG] Closed socket 10 (AF_INET 0.0.0.0:5922)
[20200625-23:04:05] [DEBUG] Closed socket 10 (AF_INET 0.0.0.0:6022)
[20200625-23:04:05] [DEBUG] Closed socket 10 (AF_INET 0.0.0.0:6222)
[20200625-23:04:05] [DEBUG] Closed socket 10 (AF_INET 0.0.0.0:5923)
[20200625-23:04:05] [DEBUG] Closed socket 10 (AF_INET 0.0.0.0:6023)
[20200625-23:04:05] [DEBUG] Closed socket 10 (AF_INET 0.0.0.0:6223)
[20200625-23:04:05] [DEBUG] Closed socket 10 (AF_INET 0.0.0.0:5933)
[20200625-23:04:05] [DEBUG] Closed socket 10 (AF_INET 0.0.0.0:6033)
[20200625-23:04:05] [DEBUG] Closed socket 10 (AF_INET 0.0.0.0:6233)
[20200625-23:04:05] [DEBUG] Closed socket 9 (AF_INET 127.0.0.1:3350)
[20200625-23:04:05] [INFO ] calling auth_start_session from pid 23121
[20200625-23:04:05] [DEBUG] Closed socket 8 (AF_INET 127.0.0.1:3350)
[20200625-23:04:05] [DEBUG] Closed socket 9 (AF_INET 127.0.0.1:3350)
[20200625-23:04:05] [INFO ] Xvnc :33 -auth .Xauthority -geometry 1920x1080 -depth 8 -rfbauth /root/.vnc/sesman_passw@Tooling-Server:33 -bs -nolisten tcp -localhost -dpi 96
[20200625-23:04:15] [ERROR] X server for display 33 startup timeout
[20200625-23:04:15] [CORE ] waiting for window manager (pid 23123) to exit
[20200625-23:04:15] [ERROR] X server for display 33 startup timeout
[20200625-23:04:15] [ERROR] another Xserver might already be active on display 33 - see log
[20200625-23:04:15] [DEBUG] aborting connection...
[20200625-23:04:15] [CORE ] window manager (pid 23123) did exit, cleaning up session
[20200625-23:04:15] [INFO ] calling auth_stop_session and auth_end from pid 23121
[20200625-23:04:15] [DEBUG] cleanup_sockets:
[20200625-23:04:15] [DEBUG] cleanup_sockets: deleting /tmp/.xrdp/xrdp_chansrv_socket_33
[20200625-23:04:15] [DEBUG] cleanup_sockets: deleting /tmp/.xrdp/xrdpapi_33
[20200625-23:04:15] [INFO ] ++ terminated session:  username root, display :33.0, session_pid 23121, ip 195.233.142.182:65160 - socket: 12

Apparently the value -depth 8 was causing the error. Found out that my Windows RDP setting was getting set to «Low Bandwidth» setting and color depth was being set at 8. Changed to default 32 and issue was solved.

@roisnir

In my case, none of the above solutions worked.
my log looked like this:

[20200905-15:23:54] [DEBUG] xrdp_wm_log_msg: VNC connecting to 127.0.0.1 5910
[20200905-15:23:57] [DEBUG] VNC error 1 after security negotiation
[20200905-15:23:57] [DEBUG] VNC error before sending share flag
[20200905-15:23:57] [DEBUG] VNC error before receiving server init
[20200905-15:23:57] [DEBUG] VNC error before receiving pixel format
[20200905-15:23:57] [DEBUG] VNC error before receiving name length
[20200905-15:23:57] [DEBUG] VNC error before receiving name
[20200905-15:23:57] [DEBUG] xrdp_wm_log_msg: VNC error - problem connecting
[20200905-15:23:57] [DEBUG] Closed socket 19 (AF_INET6 ::ffff:127.0.0.1 port 59500)
[20200905-15:23:57] [DEBUG] xrdp_wm_log_msg: some problem
[20200905-15:23:57] [DEBUG] xrdp_mm_module_cleanup
[20200905-15:23:57] [DEBUG] VNC mod_exit

Solved after changing param=Xvnc to vncserver in /etc/xrdp/sesman.ini:

[Xvnc]
param=vncserver
param=-bs
param=-nolisten
param=tcp
param=-localhost
param=-dpi
param=96

Источник

Содержание

  1. CentOS
  2. Windows Remote Desktop/Centos 7 xrdp connection fails with «some problem»
  3. Windows Remote Desktop/Centos 7 xrdp connection fails with «some problem»
  4. Re: Windows Remote Desktop/Centos 7 xrdp connection fails with «some problem»
  5. Re: Windows Remote Desktop/Centos 7 xrdp connection fails with «some problem»
  6. Vnc Error — Problem Connecting #2086
  7. Comments
  8. login successful for display 10. VNC error — problem connecting some problem #1459
  9. Comments

CentOS

The Community ENTerprise Operating System

Windows Remote Desktop/Centos 7 xrdp connection fails with «some problem»

Windows Remote Desktop/Centos 7 xrdp connection fails with «some problem»

Post by BGood » 2017/01/08 20:00:10

With the help of Centos forum resources, I added GUI (MATE Desktop) support to a dedicated Centos 7 web server (Centos 7 Live DVD — Can Gnome/GUI be installed later? viewtopic.php?f=47&t=60762).

While the MATE desktop is a convenient addition to the main server console, I would also like to provide remote GUI capability to my main workstation which is a Windows 7 desktop. I am trying to connect remotely to the MATE desktop using a Windows Remote Desktop client on the Windows side and xrdp on the Centos side, but am encountering a «some problem» VNC connection error which I think is coming from the Centos side:

Re: Windows Remote Desktop/Centos 7 xrdp connection fails with «some problem»

Post by BGood » 2017/01/09 17:21:48

Re: Windows Remote Desktop/Centos 7 xrdp connection fails with «some problem»

Post by FAB5FLAVE » 2017/08/23 15:19:27

Installed xdrp and tigervnc windows RDP connected no problem.

Installed MATE Desktop got the same «some problem» error when trying to connect.

Tried numerous things to get this working like changing port number, reinstalling xdrp and tigervnc etc.

Eventually resolved the issue by removing xrdp and tigervnc and reinstalling

yum remove xrdp
yum remove tigervnc-server.x86_64
yum remove tigervnc-server-minimal.x86_64
reboot

systemctl start xrdp

Didn’t start
systemd[1]: Started xrdp daemon.
systemd[1]: Starting xrdp daemon.
systemd[3144]: Failed at step EXEC spawning /usr/sbin/xrdp: Permission denied
systemd[1]: xrdp.service: main process exited, code=exited, status=203/EXEC
systemd[1]: Unit xrdp.service entered failed state.
systemd[1]: xrdp.service failed.

So ran the following
chcon -t bin_t /usr/sbin/xrdp
chcon -t bin_t /usr/sbin/xrdp-sesman

Источник

Vnc Error — Problem Connecting #2086

Im experiencing the following error with the tool xrdp in a suse 15 sp1 machine in azure, I just wanna know is someone has seen it before.

Please wait, we now perform access control.
Reply from access control: Sucess
connecting to sesman ip 127.0.0.01 port 3350
seman connect ok
sending login info to session manager, please wait.
login successful for display 201
VNC started connecting
waiting 2000 ms for VNC to start.
VNC connecting to 127.0.0.1 6101
VNC error — problem connecting
some problem

The text was updated successfully, but these errors were encountered:

@jsanchezzz — these two lines look odd:-

Have you changed the X11DisplayOffset=10 setting in sesman.ini? It looks like it’s set to around 200, which probably won’t work.

@jsanchezzz — do you need any more help with this?

@matt335672 yes, I reinstalled the xrdp, but it showing the same error. Also I did not change the X11DisplayOffset=10, how can i see if the X11DisplayOffset has changed somehow?

It’s in /etc/xrdp/sesman.ini :-

Hello as you said the X11DisplayOffset is set to 200, and we dont know why? could you tell us how to change it to 10, please? see the image attached.

Well, you seem to have two problems here

The first problem is solved by editing /etc/xrdp/sesman.ini , correcting the value, and restarting the xrdp-sesman service.

The second and more serious problem is that you’ve got a file on your system which needs privilege to change and something unknown has changed it. That’s not a good position to be in. Not only do we not know what else might have changed in the xrdp configuration, but there might be other files which have changed that could affect system operation. So I think it’s worth trying to figure out how this file could have changed.

We changed the parameter but it did not work, We did a deeper investigation to know why the rdp is not working and we entered the logs, we saw something about a certificate, I would like to know if you have any knowledge, because the certificate is installed but the vm does not find it.

see the images attached and the notepad.
log JS.txt

If you don’t have a certificate, xrdp will fall back on a less secure connection method, so I’d expect it still to work. I think you should leave that for now.

A couple of questions for you:-

  • What version of xrdp is installed?
  • What desktop have you installed on the machine?

What version of xrdp is installed?

What desktop have you installed on the machine?

linux suse 15 sp1

«Linux SuSE 15 sp 1» isn’t what I’d call a desktop. I mean, are you running GNOME or KDE (or similar)? You’ll need a desktop installed for xrdp to start. Do you have one installed?

As far as the certificate error goes

I’ve checked the sources for 0.9.6 and it’s telling me that either /etc/xrdp doesn’t exist on that machine, or /etc/xrdp/cert.pem doesn’t exist on that machine. What do you get on the machine for these two command when logged in as root:-

We solved the problem:

1 — Performing a clean installation of patterns-gnome-gnome_basic
2 — Allowing remote sesion with remote manager
3 — Installing xrdp xorgxrdp
4 — enabling the vm firewall and open the port 3389 ( systemctl enable firewalld, systemctl startd firewalld firewall-cmd —permanent —zone=public —add-port=3389/tcp )

Thanks for you support, it was rellay heplful to solve the issue.

Thanks for letting us know.

Did you get your certificate problem sorted out too?

Jumping into this conversation 3 years later.

I’m not asking a question here, but trying to add something to the quoted observation below:

The second and more serious problem is that you’ve got a file on your system which needs privilege to change and something unknown has changed it. That’s not a good position to be in. Not only do we not know what else might have changed in the xrdp configuration, but there might be other files which have changed that could affect system operation. So I think it’s worth trying to figure out how this file could have changed.
— matt335672

I’ve observed the same issue. The configuration at /etc/xrdp/sesman.ini says that the default is 10 but I see 200.
I’m not sure what changed this configuration.

However, I’ve observed something peculiar:

I’m running OpenSUSE Tumbleweed in a VM under Hyper-V under Windows11. Unfortunately I have to use Windows 🙁

I have GWSL, which is a Xserver with some tweaks intended to make life easier if you are using WSL. But I’m not using OpenSUSE under WSL; I’m using OpenSUSE under a VM, under Hyper-V.

Then I have two choices for opening a RDP session: (a) using GWSL or (b) using Remote Desktop Connection, which is native to Windows11.

I’ve discovered that GWSL employs/requires DISPLAY=:10.0 whilst Windows Remote Desktop Connection employs/requires DISPLAY=:200.0

I can open KDE full screen using GWSL, but I have to open first a ssh session and then run startplasma-x11 from it, which is inconvenient, but works.

However, I cannot open KDE full screen using Windows Remote Desktop Connection. But I’ve discovered that it starts to work fine if I first open a GWSL connection. In other words: if I open first a window with KDE in it via GWSL, after that, I can open another window running KDE in it via Windows Remote Desktop Connection. In this case, applications running in the first window employ DISPLAY=:10.0 whilst application in the second window employ DISPLAY=:200.0 .

Needless to say that I don’t understand why it behaves this way.

Seems like the RDP server for display 10 works like a transport layer for the RDP server for display 200. The evidence is: if I close the RDP server for display 10 (i.e.: I close GWSL), the window containing applications associated to display 200 stop working after 10 seconds and the entire KDE session dies.

I would prefer to use WIndow Remote Desktop Server, since it performs better. But, as explained, it will require GWSL for some unknown reason. which forces me to use GWSL anyway.

Trying to answer the question «who changed X11DisplayOffset=10 to X11DisplayOffset=200». my guess is package hyper-v , installed automatically on OpenSUSE when the VM is first installed. I’m not sure though. Just a guess.

Источник

login successful for display 10. VNC error — problem connecting some problem #1459

I have installed and used xrdp on a centos 7.0 + gnome. I used this resource https://draculaservers.com/tutorials/install-xrdp-centos/ for install xrdp.
I always used session Xorg for login because of xrdp never worked with Xvnc session

A few days ago I have updated a linux with command sudo yum update
After the update, the menu Xorg disappeared from Session list and when I used Xvnc session I get an error — Login successful for display 10. VNC error — problem connecting some problem

I googled a lot and read and tried a lot of solutions for the fix issue but without success.

The text was updated successfully, but these errors were encountered:

A couple of questions for you:-

  • Looking at your yum logs, you appear to be running CentOS 7.7 rather than 7.0. Can you confirm this? You can find out your minor release version with the command cat /etc/redhat-release ?
  • Is SELinux enabled on this system? If so, you will need to install the xrdp-selinux package in addition to the xrdp package.

And a few other things:-

  • The sessions which are presented to the user on the login screen are stored in the file /etc/xrdp/sesman.ini . On a fresh install, this file should contain the following sections (amongst other things):-

These sections should add Xorg and Xvnc as the options on your session list.

When using Xvnc, the sesman log indicates that the VNC server is having trouble running the Xvnc command. You could try running Xvnc :10 on the command line to see if we get any more information.

I see from the sesman log you’re trying to run with a colour depth of 15. This confuses some software as the MESA-based 3d acceleration won’t work. Try setting a depth of 32 in your RDP client.

I see from the log you’re trying to log in as root. GNOME in particular doesn’t like this. I don’t think this is the source of the problem you’re describing here, but in general things will work a bit better if you log in as a non-privileged user.

I hope that’s useful. Let us know how you get on.

The issue was not solved.

]# rpm -q centos-release
centos-release-7-7.1908.0.el7.centos.x86_64

]# getenforce
Enforcing
[root@localhost

]# sestatus
SELinux status: enabled
SELinuxfs mount: /sys/fs/selinux
SELinux root directory: /etc/selinux
Loaded policy name: targeted
Current mode: enforcing
Mode from config file: enforcing
Policy MLS status: enabled
Policy deny_unknown status: allowed
Max kernel policy version: 31
[root@localhost

I have installed:
xrdp-selinux.x86_64 1:0.9.11-5.el7

I have added the sesman.ini file to this post.
sesman.txt

Output for Xvnc :10
[root@localhost

Xvnc TigerVNC 1.8.0 — built Aug 9 2019 03:04:19
Copyright (C) 1999-2017 TigerVNC Team and many others (see README.txt)
See http://www.tigervnc.org for information on TigerVNC.
Underlying X server release 12001000, The X.Org Foundation

Tue Dec 17 11:24:38 2019
vncext: VNC extension running!
vncext: Listening for VNC connections on all interface(s), port 5910
vncext: created VNC server for screen 0

Where and how can I change the colour depth?

Xorg still is not available in the session list.

I’m using Mate desktop. Gnome desktop worked under root account without any issue till yum update.

I just realized I gave you some duff info about the session list — apologies. The session list is stored in /etc/xrdp/xrdp.ini , and not /etc/xrdp/sesman.ini .

If you look in xrdp.ini at around line 181, you should find the following commented-out section:-

Remove the ‘#’ line prefixes and restart the xrdp service. That should give you your Xorg session back.

To run Xorg, you’ll need xorgxrdp installed, but you probably already have that if it was working before.

Colour depth is available (in the Windows client) on the ‘Display’ tab:-

Let us know if that’s useful.

  1. I have edit the /etc/xrdp/xrdp.ini and uncommented this strings
    #[Xorg]
    #name=Xorg
    #lib=libxup.so
    #username=ask
    #password=ask
    #ip=127.0.0.1
    #port=-1
    #code=20

I have restarted the server

When I’m trying connect by rdp — I see an only a black screen. Doesn’t matter which color I use -15 or 32 bits.

  1. I have added the new logs.
    Xorg.0.log
    xrdp.log
    xrdp-sesman.log
    yum.log

I wasn’t familiar with MATE, so I’ve gone away and had a look at it.

Can you try the following:-

  • Make sure the whole MATE desktop is installed with yum groupinstall «MATE Desktop» . It’s possible you’ve only got the mate-desktop RPM installed which isn’t enough.
  • Issue this command as the user you’re trying to log in as to set your default session.

Then have another go.

If you’re still having problems, post the output of the file

/.xsession-errors. This file is (or should be) created when the user logs on and runs the session.

Let us know how it goes.

We have a small progress.

List of installed Groups
Installed Environment Groups:
MATE Desktop
Available Environment Groups:
Minimal Install
Compute Node
Infrastructure Server
File and Print Server
Cinnamon Desktop
Basic Web Server
Virtualization Host
Server with GUI
GNOME Desktop
KDE Plasma Workspaces
Development and Creative Workstation
Installed Groups:
MATE
Available Groups:
Cinnamon
Compatibility Libraries
Console Internet Tools
Development Tools
Educational Software
Electronic Lab
Fedora Packager
General Purpose Desktop
Graphical Administration Tools
Haskell
LXQt Desktop
Legacy UNIX Compatibility
Milkymist
PostgreSQL Database Server 10 PGDG
PostgreSQL Database Server 11 PGDG
PostgreSQL Database Server 12 PGDG
PostgreSQL Database Server 9.4 PGDG
PostgreSQL Database Server 9.5 PGDG
PostgreSQL Database Server 9.6 PGDG
Scientific Support
Security Tools
Smart Card Support
System Administration Tools
System Management
TurboGears application framework
Xfce

Sessions files
-rwxr-xr-x. 1 root root 13 Dec 18 09:42 /root/.Xclients


-rwxr-xr-x. 1 root root 13 Dec 18 09:43 /root/.xsession

After run command bellow I saw the normal RDP screen with Xvnc, Xorg. I tried to login, but the login process stuck. After a few minutes the rdp returned the error

ln -sf /usr/bin/mate-session

  1. Xsession log files
    xsession-errors.txt

The session log shows the desktop is starting. The RDP log shows that XRDP is unable to connect to the X server.

  • Does the same thing happen with both Xvnc and Xorg back ends?
  • For Xorg, have you definitely got the xorgxrdp RPM installed?
  • Xorg generates a log file in

/.xorgxrdp. .log . So for the above example where display 11 is being used, the log file is in

/.xorgxrdp.11.log . If you’re having problems with Xorg, please post the contents of this file.
On CentOS 7, the Xvnc log is stored by journalctl along with stderr from xrdp-sesman (which is not the same as /var/log/xrdp-sesman.log ). If you’re having problems with Xvnc, please post the output of the following command (run as root), which displays the last 3 minutes of this output:-

I have installed xorgxrdp and now everything works properly .
Thank you for your attention and support.

Thanks for letting us know — I’m glad we got there between us.

I’ll just summarize and expand on this thread for anyone else reading this, who is trying to get an alternative desktop working on a fresh install of the latest CentOS 7. The webpage you linked to is pretty good, but it’s missing some small details like SELinux support and the need for xorgxrdp . I’ve also added some of my own sysadmin experiences.

At the time of writing, the following versions apply:-

Software Version
CentOS 7.7
xrdp RPM 0.9.11-5
xorgxrdp RPM 0.2.11-1

Ensure the OS is up to date with sudo yum update

Install EPEL repository with sudo yum install epel-release

Install and enable XRDP with:-

If you’re using the firewall, allow external access to TCP port 3389 with:-

If you’re using SELinux, sudo yum install xrdp-selinux

If you want to use the Xorg backend in addition to (or instead of) the Xvnc backend, do the following. The differences between the two backends are covered elsewhere.

  • sudo yum install xorgxrdp
  • Edit /etc/xrdp/xrdp.ini . If the [Xorg] section is commented out, uncomment it.
  • If you changed xrdp.ini , sudo systemctl restart xrdp to pick up the changes.

Install your desktop(s), making sure that you use a command to install the whole desktop rather than a subset of it. This will probably be a yum groupinstall command. For example, for MATE, use sudo yum groupinstall «MATE Desktop» .

The default desktop for XRDP on CentOS 7 is GNOME. If you want the default desktop for all XRDP users to be something else, create the file /etc/sysconfig/desktop and set the PREFERRED variable to the command to start the desktop. For example, this /etc/sysconfig/desktop sets the default desktop to MATE for all XRDP users:-

XRDP users who want to use a desktop other than the default will need to soft-link the command to start the correct session in to

/.Xclients . For MATE, this command is adequate:-

As an aside, some websites suggest creating a vanilla file

/.xsession containing the command to start the desktop. That’s OK too, but you have to remember to make the file executable. The soft-link method avoids this pitfall.

That should get the desktop running. Here are a couple of gotchas:-

    Some desktops expect GDM to be running to provide some of their functionality over DBUS. For example, the GNOME lock screen is implemented in GDM. If you’re using one of these desktops you may need to enable GDM on the machine console (if it isn’t enabled already):-

I think that’s it, but please let me know if I’ve left anything out.

Does anyone think this would be useful as a Wiki page by the way?

What if you add this instruction into Readme file — at the paragraph troubleshooting?

I see what you mean — there are very brief instructions in the README.md which appears on the front page on Github.

What might make more sense is to link from the README.md to the Wiki, as the Wiki can be updated more easily than README.md. I’ll do some more research (after Xmas probably) and try to get something together which has instructions for all desktops.

Maybe it is interesting, but on Fedora 30/31, I am facing the same issue (exact same displayed message), but only for corporate users.
With local created users, it works.
I am using Xvnc.

Hello,
I had the same situation, Xvnc broken when rendering NVIDIA didn’t work through VNC for old technology.
I installed tigerVnc and running this command:
tigervncserver -localhost no
Viewer Vnc:
vncviewer ip:1
e.g. 192.168.1.1:1

Hello, I am facing a RDP issue from Windows 10 to RHEL8 trying both Xvnc and Xorg. Using either option, after entering credentials and selecting OK, the RDP session immediately closes. For users who were on the system previously and had their sessions time out, they can still RDP into the machine, but all other users can not start a RDP session successfully. Any ideas?

@rja1972 — please start a new thread. I can’t see any similarities between this issue and what you are describing.

Knowing what OS you are on, and what your xrdp version is would be useful.

I’m closing this thread now, as the issue raised by the OP was addressed. Please feel free to raise a new issue if you’ve posted above and you still need help getting something working.

A couple of questions for you:-

  • Looking at your yum logs, you appear to be running CentOS 7.7 rather than 7.0. Can you confirm this? You can find out your minor release version with the command cat /etc/redhat-release ?
  • Is SELinux enabled on this system? If so, you will need to install the xrdp-selinux package in addition to the xrdp package.

And a few other things:-

  • The sessions which are presented to the user on the login screen are stored in the file /etc/xrdp/sesman.ini . On a fresh install, this file should contain the following sections (amongst other things):-

These sections should add Xorg and Xvnc as the options on your session list.

  • When using Xvnc, the sesman log indicates that the VNC server is having trouble running the Xvnc command. You could try running Xvnc :10 on the command line to see if we get any more information.
  • I see from the sesman log you’re trying to run with a colour depth of 15. This confuses some software as the MESA-based 3d acceleration won’t work. Try setting a depth of 32 in your RDP client.
  • I see from the log you’re trying to log in as root. GNOME in particular doesn’t like this. I don’t think this is the source of the problem you’re describing here, but in general things will work a bit better if you log in as a non-privileged user.

I hope that’s useful. Let us know how you get on.

You are right. I am running CentOS Stream 9 and encounter the same problem. Able to connect after setting the depth to 32 in my RDP client despite the fact that I am connecting as root.

Источник

Источник

Hi,

Im trying to connect to my Debian machine from my Windows host but I cant get it to work, I have installed both xrdp and x11vnc. I don’t know the reason as to why I can’t connect. The machine is listening on the TCP ports.

xrdp.log:

Code: Select all

dave@hal9000:/var/log$ sudo cat xrdp.log
[20180219-19:34:37] [INFO ] starting xrdp with pid 2189
[20180219-19:34:37] [INFO ] listening to port 3389 on 0.0.0.0
[20180219-19:34:52] [INFO ] A connection received from: ::ffff:172.10.88.2 port 55533
[20180219-19:34:52] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.10.88.6 port 3389)
[20180219-19:34:52] [DEBUG] Closed socket 11 (AF_INET6 :: port 3389)
[20180219-19:34:52] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[20180219-19:34:53] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[20180219-19:34:53] [DEBUG] Security layer: requested 11, selected 0
[20180219-19:34:53] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.10.88.6 port 3389)
[20180219-19:34:53] [ERROR] Listening socket is in wrong state, terminating listener
[20180219-19:34:54] [INFO ] A connection received from: ::ffff:172.10.88.2 port 55534
[20180219-19:34:54] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.10.88.6 port 3389)
[20180219-19:34:54] [DEBUG] Closed socket 11 (AF_INET6 :: port 3389)
[20180219-19:34:54] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[20180219-19:34:54] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[20180219-19:34:54] [DEBUG] Security layer: requested 0, selected 0
[20180219-19:34:54] [DEBUG] xrdp_000009d7_wm_login_mode_event_00000001
[20180219-19:34:54] [INFO ] Loading keymap file /etc/xrdp/km-0000041d.ini
[20180219-19:34:54] [WARN ] local keymap file for 0x0000041d found and doesn't match built in keymap, using local keymap file
[20180219-19:35:08] [DEBUG] xrdp_wm_log_msg: connecting to sesman ip 127.0.0.1 port 3350
[20180219-19:35:08] [INFO ] xrdp_wm_log_msg: sesman connect ok
[20180219-19:35:08] [DEBUG] xrdp_wm_log_msg: sending login info to session manager, please wait...
[20180219-19:35:08] [DEBUG] return value from xrdp_mm_connect 0
[20180219-19:35:08] [INFO ] xrdp_wm_log_msg: login successful for display 10
[20180219-19:35:08] [DEBUG] xrdp_wm_log_msg: started connecting
[20180219-19:35:12] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:35:15] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:35:19] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:35:22] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:35:26] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:35:29] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:35:33] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:35:36] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:35:40] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:35:44] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:35:47] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:35:51] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:35:54] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:35:58] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:36:01] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:36:05] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:36:08] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:36:12] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:36:15] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:36:19] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:36:22] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:36:26] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:36:29] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:36:33] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:36:36] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:36:40] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:36:43] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:36:47] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:36:50] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:36:54] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:36:57] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:37:01] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:37:04] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:37:08] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:37:11] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:37:15] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:37:18] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:37:22] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:37:25] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:37:29] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:37:32] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:37:36] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:37:39] [INFO ] A connection received from: ::ffff:172.10.88.2 port 55550
[20180219-19:37:39] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.10.88.6 port 3389)
[20180219-19:37:39] [DEBUG] Closed socket 11 (AF_INET6 :: port 3389)
[20180219-19:37:39] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[20180219-19:37:39] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[20180219-19:37:39] [DEBUG] Security layer: requested 11, selected 0
[20180219-19:37:39] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.10.88.6 port 3389)
[20180219-19:37:39] [ERROR] Listening socket is in wrong state, terminating listener
[20180219-19:37:39] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:37:41] [INFO ] A connection received from: ::ffff:172.10.88.2 port 55551
[20180219-19:37:41] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.10.88.6 port 3389)
[20180219-19:37:41] [DEBUG] Closed socket 11 (AF_INET6 :: port 3389)
[20180219-19:37:41] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[20180219-19:37:41] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[20180219-19:37:41] [DEBUG] Security layer: requested 0, selected 0
[20180219-19:37:41] [DEBUG] xrdp_00000a3a_wm_login_mode_event_00000001
[20180219-19:37:41] [INFO ] Loading keymap file /etc/xrdp/km-0000041d.ini
[20180219-19:37:41] [WARN ] local keymap file for 0x0000041d found and doesn't match built in keymap, using local keymap file
[20180219-19:37:43] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:37:46] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:37:50] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:37:53] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:37:57] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:38:00] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:38:04] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:38:07] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:38:11] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:38:15] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:38:18] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:38:22] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:38:25] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:38:29] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:38:32] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:38:35] [INFO ] A connection received from: ::ffff:172.10.88.6 port 57082
[20180219-19:38:35] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.10.88.6 port 3389)
[20180219-19:38:35] [DEBUG] Closed socket 11 (AF_INET6 :: port 3389)
[20180219-19:38:35] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[20180219-19:38:35] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[20180219-19:38:35] [DEBUG] Security layer: requested 0, selected 0
[20180219-19:38:35] [DEBUG] return value from xrdp_mm_connect 0
[20180219-19:38:35] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.10.88.6 port 3389)
[20180219-19:38:35] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.10.88.6 port 3389)
[20180219-19:38:35] [ERROR] Listening socket is in wrong state, terminating listener
[20180219-19:38:35] [DEBUG] Closed socket 16 (AF_INET6 ::ffff:172.10.88.6 port 57082)
[20180219-19:38:35] [DEBUG] xrdp_mm_module_cleanup
[20180219-19:38:35] [ERROR] Listening socket is in wrong state, terminating listener
[20180219-19:38:36] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:38:39] [DEBUG] xrdp_wm_log_msg: connection problem, giving up
[20180219-19:38:39] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:38:39] [DEBUG] xrdp_wm_log_msg: some problem
[20180219-19:38:39] [DEBUG] xrdp_mm_module_cleanup
[20180219-19:38:39] [DEBUG] Closed socket 16 (AF_INET6 ::1 port 51520)
[20180219-19:38:39] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.10.88.6 port 3389)
[20180219-19:38:39] [DEBUG] xrdp_mm_module_cleanup
[20180219-19:38:39] [ERROR] Listening socket is in wrong state, terminating listener
[20180219-19:38:52] [INFO ] A connection received from: ::ffff:172.10.88.2 port 55557
[20180219-19:38:52] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.10.88.6 port 3389)
[20180219-19:38:52] [DEBUG] Closed socket 11 (AF_INET6 :: port 3389)
[20180219-19:38:52] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[20180219-19:38:52] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[20180219-19:38:52] [DEBUG] Security layer: requested 11, selected 0
[20180219-19:38:52] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.10.88.6 port 3389)
[20180219-19:38:52] [ERROR] Listening socket is in wrong state, terminating listener
[20180219-19:38:53] [INFO ] A connection received from: ::ffff:172.10.88.2 port 55558
[20180219-19:38:53] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.10.88.6 port 3389)
[20180219-19:38:53] [DEBUG] Closed socket 11 (AF_INET6 :: port 3389)
[20180219-19:38:53] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[20180219-19:38:53] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[20180219-19:38:53] [DEBUG] Security layer: requested 0, selected 0
[20180219-19:38:53] [DEBUG] xrdp_00000a62_wm_login_mode_event_00000001
[20180219-19:38:53] [INFO ] Loading keymap file /etc/xrdp/km-0000041d.ini
[20180219-19:38:53] [WARN ] local keymap file for 0x0000041d found and doesn't match built in keymap, using local keymap file
[20180219-19:43:56] [DEBUG] xrdp_wm_log_msg: connecting to sesman ip 127.0.0.1 port 3350
[20180219-19:43:57] [INFO ] xrdp_wm_log_msg: sesman connect ok
[20180219-19:43:57] [DEBUG] xrdp_wm_log_msg: sending login info to session manager, please wait...
[20180219-19:43:57] [DEBUG] return value from xrdp_mm_connect 0
[20180219-19:43:57] [INFO ] xrdp_wm_log_msg: login successful for display 10
[20180219-19:43:57] [DEBUG] xrdp_wm_log_msg: VNC started connecting
[20180219-19:43:57] [DEBUG] xrdp_wm_log_msg: VNC connecting to 127.0.0.1 5910
[20180219-19:44:00] [DEBUG] VNC error 1 after security negotiation
[20180219-19:44:00] [DEBUG] VNC error before sending share flag
[20180219-19:44:00] [DEBUG] VNC error before receiving server init
[20180219-19:44:00] [DEBUG] VNC error before receiving pixel format
[20180219-19:44:00] [DEBUG] VNC error before receiving name length
[20180219-19:44:00] [DEBUG] VNC error before receiving name
[20180219-19:44:00] [DEBUG] xrdp_wm_log_msg: VNC error - problem connecting
[20180219-19:44:00] [DEBUG] Closed socket 17 (AF_INET6 :: port 40824)
[20180219-19:44:00] [DEBUG] xrdp_wm_log_msg: some problem
[20180219-19:44:00] [DEBUG] xrdp_mm_module_cleanup
[20180219-19:44:00] [DEBUG] VNC mod_exit
[20180219-19:44:00] [DEBUG] Closed socket 16 (AF_INET6 ::1 port 51526)
[20180219-19:47:42] [DEBUG] xrdp_wm_log_msg: VNC started connecting
[20180219-19:47:42] [DEBUG] xrdp_wm_log_msg: VNC connecting to 172.10.88.6 3350
[20180219-19:47:45] [DEBUG] VNC error 1 after security negotiation
[20180219-19:47:45] [DEBUG] VNC error before sending share flag
[20180219-19:47:45] [DEBUG] VNC error before receiving server init
[20180219-19:47:45] [DEBUG] VNC error before receiving pixel format
[20180219-19:47:45] [DEBUG] VNC error before receiving name length
[20180219-19:47:45] [DEBUG] VNC error before receiving name
[20180219-19:47:45] [DEBUG] xrdp_wm_log_msg: VNC error - problem connecting
[20180219-19:47:45] [DEBUG] Closed socket 16 (AF_INET6 :: port 57536)
[20180219-19:47:45] [DEBUG] xrdp_wm_log_msg: some problem
[20180219-19:47:45] [ERROR] xrdp_wm_log_msg: Error connecting to: 172.10.88.6
[20180219-19:47:45] [DEBUG] xrdp_mm_module_cleanup
[20180219-19:47:45] [DEBUG] VNC mod_exit
[20180219-19:47:45] [DEBUG] return value from xrdp_mm_connect 1
[20180219-19:47:51] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.10.88.6 port 3389)
[20180219-19:47:51] [DEBUG] xrdp_mm_module_cleanup
[20180219-19:47:51] [ERROR] Listening socket is in wrong state, terminating listener
[20180219-19:48:07] [INFO ] A connection received from: ::ffff:172.10.88.2 port 55674
[20180219-19:48:07] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.10.88.6 port 3389)
[20180219-19:48:07] [DEBUG] Closed socket 11 (AF_INET6 :: port 3389)
[20180219-19:48:07] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[20180219-19:48:07] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[20180219-19:48:07] [DEBUG] Security layer: requested 11, selected 0
[20180219-19:48:07] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.10.88.6 port 3389)
[20180219-19:48:07] [ERROR] Listening socket is in wrong state, terminating listener
[20180219-19:48:08] [INFO ] A connection received from: ::ffff:172.10.88.2 port 55675
[20180219-19:48:08] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.10.88.6 port 3389)
[20180219-19:48:08] [DEBUG] Closed socket 11 (AF_INET6 :: port 3389)
[20180219-19:48:08] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[20180219-19:48:08] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[20180219-19:48:08] [DEBUG] Security layer: requested 0, selected 0
[20180219-19:48:08] [DEBUG] xrdp_00000cbd_wm_login_mode_event_00000001
[20180219-19:48:08] [INFO ] Loading keymap file /etc/xrdp/km-0000041d.ini
[20180219-19:48:08] [WARN ] local keymap file for 0x0000041d found and doesn't match built in keymap, using local keymap file
[20180219-19:48:30] [DEBUG] xrdp_wm_log_msg: connecting to sesman ip 127.0.0.1 port 3350
[20180219-19:48:31] [INFO ] xrdp_wm_log_msg: sesman connect ok
[20180219-19:48:31] [DEBUG] xrdp_wm_log_msg: sending login info to session manager, please wait...
[20180219-19:48:31] [DEBUG] return value from xrdp_mm_connect 0
[20180219-19:48:32] [INFO ] xrdp_wm_log_msg: login failed for display 0
[20180219-19:48:32] [DEBUG] xrdp_mm_module_cleanup
[20180219-19:48:32] [DEBUG] Closed socket 16 (AF_INET6 ::1 port 51540)
[20180219-19:48:56] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.10.88.6 port 3389)
[20180219-19:48:56] [DEBUG] xrdp_mm_module_cleanup
[20180219-19:48:56] [ERROR] Listening socket is in wrong state, terminating listener
[20180219-19:49:01] [DEBUG] Closed socket 11 (AF_INET6 :: port 3389)
[20180219-19:50:24] [INFO ] starting xrdp with pid 654
[20180219-19:50:24] [INFO ] listening to port 3389 on 0.0.0.0
[20180219-19:50:34] [INFO ] A connection received from: ::ffff:172.10.88.2 port 55696
[20180219-19:50:34] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.10.88.6 port 3389)
[20180219-19:50:34] [DEBUG] Closed socket 11 (AF_INET6 :: port 3389)
[20180219-19:50:34] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[20180219-19:50:34] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[20180219-19:50:34] [DEBUG] Security layer: requested 11, selected 0
[20180219-19:50:34] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.10.88.6 port 3389)
[20180219-19:50:34] [ERROR] Listening socket is in wrong state, terminating listener
[20180219-19:50:35] [INFO ] A connection received from: ::ffff:172.10.88.2 port 55697
[20180219-19:50:35] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.10.88.6 port 3389)
[20180219-19:50:35] [DEBUG] Closed socket 11 (AF_INET6 :: port 3389)
[20180219-19:50:35] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[20180219-19:50:35] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[20180219-19:50:35] [DEBUG] Security layer: requested 0, selected 0
[20180219-19:50:35] [DEBUG] xrdp_000004aa_wm_login_mode_event_00000001
[20180219-19:50:35] [INFO ] Loading keymap file /etc/xrdp/km-0000041d.ini
[20180219-19:50:35] [WARN ] local keymap file for 0x0000041d found and doesn't match built in keymap, using local keymap file
[20180219-19:50:51] [DEBUG] xrdp_wm_log_msg: connecting to sesman ip 127.0.0.1 port 3350
[20180219-19:50:52] [INFO ] xrdp_wm_log_msg: sesman connect ok
[20180219-19:50:52] [DEBUG] xrdp_wm_log_msg: sending login info to session manager, please wait...
[20180219-19:50:52] [DEBUG] return value from xrdp_mm_connect 0
[20180219-19:50:54] [INFO ] xrdp_wm_log_msg: login failed for display 0
[20180219-19:50:54] [DEBUG] xrdp_mm_module_cleanup
[20180219-19:50:54] [DEBUG] Closed socket 16 (AF_INET6 ::1 port 34254)
[20180219-19:51:32] [DEBUG] xrdp_wm_log_msg: connecting to sesman ip 127.0.0.1 port 3350
[20180219-19:51:32] [INFO ] xrdp_wm_log_msg: sesman connect ok
[20180219-19:51:32] [DEBUG] xrdp_wm_log_msg: sending login info to session manager, please wait...
[20180219-19:51:32] [DEBUG] return value from xrdp_mm_connect 0
[20180219-19:51:32] [INFO ] xrdp_wm_log_msg: login successful for display 10
[20180219-19:51:32] [DEBUG] xrdp_wm_log_msg: VNC started connecting
[20180219-19:51:32] [DEBUG] xrdp_wm_log_msg: VNC connecting to 127.0.0.1 5910
[20180219-19:51:35] [DEBUG] VNC error 1 after security negotiation
[20180219-19:51:35] [DEBUG] VNC error before sending share flag
[20180219-19:51:36] [DEBUG] VNC error before receiving server init
[20180219-19:51:36] [DEBUG] VNC error before receiving pixel format
[20180219-19:51:36] [DEBUG] VNC error before receiving name length
[20180219-19:51:36] [DEBUG] VNC error before receiving name
[20180219-19:51:36] [DEBUG] xrdp_wm_log_msg: VNC error - problem connecting
[20180219-19:51:36] [DEBUG] Closed socket 17 (AF_INET6 :: port 43916)
[20180219-19:51:36] [DEBUG] xrdp_wm_log_msg: some problem
[20180219-19:51:36] [DEBUG] xrdp_mm_module_cleanup
[20180219-19:51:36] [DEBUG] VNC mod_exit
[20180219-19:51:36] [DEBUG] Closed socket 16 (AF_INET6 ::1 port 34268)

xrdp-sesman.log:

Code: Select all

dave@hal9000:/var/log$ sudo cat xrdp-sesman.log
[20180219-19:34:35] [DEBUG] libscp initialized
[20180219-19:34:35] [INFO ] starting xrdp-sesman with pid 2177
[20180219-19:34:35] [INFO ] listening to port 3350 on 127.0.0.1
[20180219-19:35:08] [INFO ] A connection received from ::1 port 51520
[20180219-19:35:08] [INFO ] ++ created session (access granted): username dave, ip 0.0.0.0:55534 - socket: 12
[20180219-19:35:08] [INFO ] starting Xorg session...
[20180219-19:35:08] [DEBUG] Closed socket 9 (AF_INET6 :: port 5910)
[20180219-19:35:08] [DEBUG] Closed socket 9 (AF_INET6 :: port 6010)
[20180219-19:35:08] [DEBUG] Closed socket 9 (AF_INET6 :: port 6210)
[20180219-19:35:08] [DEBUG] Closed socket 8 (AF_INET6 ::1 port 3350)
[20180219-19:35:08] [DEBUG] Closed socket 7 (AF_INET6 ::1 port 3350)
[20180219-19:35:08] [INFO ] Xorg :10 -auth .Xauthority -config xrdp/xorg.conf -noreset -nolisten tcp
[20180219-19:35:18] [ERROR] X server for display 10 startup timeout
[20180219-19:35:18] [INFO ] starting xrdp-sessvc - xpid=2534 - wmpid=2533
[20180219-19:35:18] [ERROR] X server for display 10 startup timeout
[20180219-19:35:18] [ERROR] another Xserver might already be active on display 10 - see log
[20180219-19:35:18] [DEBUG] aborting connection...
[20180219-19:35:18] [INFO ] ++ terminated session:  username dave, display :10.0, session_pid 2532, ip 0.0.0.0:55534 - socket: 12
[20180219-19:43:56] [INFO ] A connection received from ::1 port 51526
[20180219-19:43:57] [INFO ] ++ created session (access granted): username dave, ip 0.0.0.0:55558 - socket: 12
[20180219-19:43:57] [INFO ] starting Xvnc session...
[20180219-19:43:57] [DEBUG] Closed socket 9 (AF_INET6 :: port 5910)
[20180219-19:43:57] [DEBUG] Closed socket 9 (AF_INET6 :: port 6010)
[20180219-19:43:57] [DEBUG] Closed socket 9 (AF_INET6 :: port 6210)
[20180219-19:43:57] [DEBUG] Closed socket 7 (AF_INET6 ::1 port 3350)
[20180219-19:43:57] [DEBUG] Closed socket 8 (AF_INET6 ::1 port 3350)
[20180219-19:43:57] [INFO ] Xvnc :10 -auth .Xauthority -geometry 3440x1440 -depth 32 -rfbauth /home/dave/.vnc/sesman_dave_passwd:10 -bs -nolisten tcp -localhost -dpi 96
[20180219-19:43:57] [CORE ] error starting X server - user dave - pid 3131
[20180219-19:43:57] [DEBUG] errno: 2, description: No such file or directory
[20180219-19:43:57] [DEBUG] execve parameter list size: 17
[20180219-19:43:57] [DEBUG]         argv[0] = Xvnc
[20180219-19:43:57] [DEBUG]         argv[1] = :10
[20180219-19:43:57] [DEBUG]         argv[2] = -auth
[20180219-19:43:57] [DEBUG]         argv[3] = .Xauthority
[20180219-19:43:57] [DEBUG]         argv[4] = -geometry
[20180219-19:43:57] [DEBUG]         argv[5] = 3440x1440
[20180219-19:43:57] [DEBUG]         argv[6] = -depth
[20180219-19:43:57] [DEBUG]         argv[7] = 32
[20180219-19:43:57] [DEBUG]         argv[8] = -rfbauth
[20180219-19:43:57] [DEBUG]         argv[9] = /home/dave/.vnc/sesman_dave_passwd:10
[20180219-19:43:57] [DEBUG]         argv[10] = -bs
[20180219-19:43:57] [DEBUG]         argv[11] = -nolisten
[20180219-19:43:57] [DEBUG]         argv[12] = tcp
[20180219-19:43:57] [DEBUG]         argv[13] = -localhost
[20180219-19:43:57] [DEBUG]         argv[14] = -dpi
[20180219-19:43:57] [DEBUG]         argv[15] = 96
[20180219-19:43:57] [DEBUG]         argv[16] = (null)
[20180219-19:44:07] [ERROR] X server for display 10 startup timeout
[20180219-19:44:07] [INFO ] starting xrdp-sessvc - xpid=3131 - wmpid=3130
[20180219-19:44:07] [ERROR] X server for display 10 startup timeout
[20180219-19:44:07] [ERROR] another Xserver might already be active on display 10 - see log
[20180219-19:44:07] [DEBUG] aborting connection...
[20180219-19:44:07] [INFO ] ++ terminated session:  username dave, display :10.0, session_pid 3129, ip 0.0.0.0:55558 - socket: 12
[20180219-19:48:30] [INFO ] A connection received from ::1 port 51540
[20180219-19:48:32] [DEBUG] Closed socket 8 (AF_INET6 ::1 port 3350)
[20180219-19:49:01] [INFO ] shutting down sesman 1
[20180219-19:49:01] [WARN ] receiving SIGHUP 1
[20180219-19:49:01] [CORE ] shutting down log subsystem...
[20180219-19:49:01] [INFO ] configuration reloaded, log subsystem restarted
[20180219-19:49:01] [DEBUG] Closed socket 7 (AF_INET6 ::1 port 3350)
[20180219-19:50:22] [DEBUG] libscp initialized
[20180219-19:50:22] [INFO ] starting xrdp-sesman with pid 627
[20180219-19:50:22] [INFO ] listening to port 3350 on 127.0.0.1
[20180219-19:50:51] [INFO ] A connection received from ::1 port 34254
[20180219-19:50:54] [DEBUG] Closed socket 8 (AF_INET6 ::1 port 3350)
[20180219-19:51:32] [INFO ] A connection received from ::1 port 34268
[20180219-19:51:32] [INFO ] ++ created session (access granted): username dave, ip 0.0.0.0:55697 - socket: 12
[20180219-19:51:32] [INFO ] starting Xvnc session...
[20180219-19:51:32] [DEBUG] Closed socket 9 (AF_INET6 :: port 5910)
[20180219-19:51:32] [DEBUG] Closed socket 9 (AF_INET6 :: port 6010)
[20180219-19:51:32] [DEBUG] Closed socket 9 (AF_INET6 :: port 6210)
[20180219-19:51:32] [DEBUG] Closed socket 8 (AF_INET6 ::1 port 3350)
[20180219-19:51:32] [DEBUG] Closed socket 7 (AF_INET6 ::1 port 3350)
[20180219-19:51:32] [INFO ] Xvnc :10 -auth .Xauthority -geometry 3440x1440 -depth 32 -rfbauth /home/dave/.vnc/sesman_dave_passwd:10 -bs -nolisten tcp -localhost -dpi 96
[20180219-19:51:32] [CORE ] error starting X server - user dave - pid 1600
[20180219-19:51:33] [DEBUG] errno: 2, description: No such file or directory
[20180219-19:51:33] [DEBUG] execve parameter list size: 17
[20180219-19:51:33] [DEBUG]         argv[0] = Xvnc
[20180219-19:51:33] [DEBUG]         argv[1] = :10
[20180219-19:51:33] [DEBUG]         argv[2] = -auth
[20180219-19:51:33] [DEBUG]         argv[3] = .Xauthority
[20180219-19:51:33] [DEBUG]         argv[4] = -geometry
[20180219-19:51:33] [DEBUG]         argv[5] = 3440x1440
[20180219-19:51:33] [DEBUG]         argv[6] = -depth
[20180219-19:51:33] [DEBUG]         argv[7] = 32
[20180219-19:51:33] [DEBUG]         argv[8] = -rfbauth
[20180219-19:51:33] [DEBUG]         argv[9] = /home/dave/.vnc/sesman_dave_passwd:10
[20180219-19:51:33] [DEBUG]         argv[10] = -bs
[20180219-19:51:33] [DEBUG]         argv[11] = -nolisten
[20180219-19:51:33] [DEBUG]         argv[12] = tcp
[20180219-19:51:33] [DEBUG]         argv[13] = -localhost
[20180219-19:51:33] [DEBUG]         argv[14] = -dpi
[20180219-19:51:33] [DEBUG]         argv[15] = 96
[20180219-19:51:33] [DEBUG]         argv[16] = (null)
[20180219-19:51:43] [ERROR] X server for display 10 startup timeout
[20180219-19:51:43] [ERROR] X server for display 10 startup timeout
[20180219-19:51:43] [INFO ] starting xrdp-sessvc - xpid=1600 - wmpid=1599
[20180219-19:51:43] [ERROR] another Xserver might already be active on display 10 - see log
[20180219-19:51:43] [DEBUG] aborting connection...
[20180219-19:51:43] [INFO ] ++ terminated session:  username dave, display :10.0, session_pid 1598, ip 0.0.0.0:55697 - socket: 12
dave@hal9000:/var/log$

Netstat -l:

Code: Select all

dave@hal9000:/var/log$ netstat -l
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State
tcp        0      0 localhost:smtp          0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:ssh             0.0.0.0:*               LISTEN
tcp6       0      0 localhost:smtp          [::]:*                  LISTEN
tcp6       0      0 [::]:3389               [::]:*                  LISTEN
tcp6       0      0 [::]:ssh                [::]:*                  LISTEN
tcp6       0      0 localhost:3350          [::]:*                  LISTEN
udp        0      0 0.0.0.0:43335           0.0.0.0:*
udp        0      0 0.0.0.0:mdns            0.0.0.0:*
udp        0      0 0.0.0.0:bootpc          0.0.0.0:*
udp        0      0 0.0.0.0:1900            0.0.0.0:*
udp6       0      0 [::]:53584              [::]:*
udp6       0      0 [::]:mdns               [::]:*
raw6       0      0 [::]:ipv6-icmp          [::]:*                  7
Active UNIX domain sockets (only servers)
Proto RefCnt Flags       Type       State         I-Node   Path
unix  2      [ ACC ]     STREAM     LISTENING     15104    /run/systemd/private
unix  2      [ ACC ]     STREAM     LISTENING     25192    /tmp/.X11-unix/X0
unix  2      [ ACC ]     STREAM     LISTENING     22591    /tmp/.ICE-unix/693
unix  2      [ ACC ]     STREAM     LISTENING     18395    /tmp/.X11-unix/X1024
unix  2      [ ACC ]     STREAM     LISTENING     19220    /run/user/1000/pulse/native
unix  2      [ ACC ]     STREAM     LISTENING     11186    /tmp/ssh-FBYJ1rlvvmr2/agent.1241
unix  2      [ ACC ]     STREAM     LISTENING     25238    /tmp/.ICE-unix/1241
unix  2      [ ACC ]     STREAM     LISTENING     22551    /run/user/118/systemd/private
unix  2      [ ACC ]     STREAM     LISTENING     25237    @/tmp/.ICE-unix/1241
unix  2      [ ACC ]     STREAM     LISTENING     1307     /run/lvm/lvmetad.socket
unix  2      [ ACC ]     STREAM     LISTENING     22556    /run/user/118/pulse/native
unix  2      [ ACC ]     STREAM     LISTENING     1310     /run/systemd/journal/stdout
unix  2      [ ACC ]     STREAM     LISTENING     22559    /run/user/118/bus
unix  2      [ ACC ]     STREAM     LISTENING     25191    @/tmp/.X11-unix/X0
unix  2      [ ACC ]     STREAM     LISTENING     22561    /run/user/118/gnupg/S.gpg-agent.ssh
unix  2      [ ACC ]     STREAM     LISTENING     22564    /run/user/118/gnupg/S.gpg-agent
unix  2      [ ACC ]     STREAM     LISTENING     22566    /run/user/118/gnupg/S.gpg-agent.extra
unix  2      [ ACC ]     STREAM     LISTENING     22568    /run/user/118/gnupg/S.gpg-agent.browser
unix  2      [ ACC ]     STREAM     LISTENING     25132    /var/run/minissdpd.sock
unix  2      [ ACC ]     STREAM     LISTENING     1330     /run/systemd/fsck.progress
unix  2      [ ACC ]     STREAM     LISTENING     1332     /run/lvm/lvmpolld.socket
unix  2      [ ACC ]     STREAM     LISTENING     20320    @/tmp/dbus-UfzVMsQcvB
unix  2      [ ACC ]     SEQPACKET  LISTENING     1351     /run/udev/control
unix  2      [ ACC ]     STREAM     LISTENING     25185    @/tmp/dbus-6ofjyHR1
unix  2      [ ACC ]     STREAM     LISTENING     18245    @/tmp/dbus-lxvYA6gm
unix  2      [ ACC ]     STREAM     LISTENING     11869    /var/run/avahi-daemon/socket
unix  2      [ ACC ]     STREAM     LISTENING     11872    /var/run/dbus/system_bus_socket
unix  2      [ ACC ]     STREAM     LISTENING     23907    /run/user/1000/systemd/private
unix  2      [ ACC ]     STREAM     LISTENING     18249    @/tmp/dbus-DUt4Gudv
unix  2      [ ACC ]     STREAM     LISTENING     23912    /run/user/1000/gnupg/S.gpg-agent.extra
unix  2      [ ACC ]     STREAM     LISTENING     23915    /run/user/1000/gnupg/S.gpg-agent.ssh
unix  2      [ ACC ]     STREAM     LISTENING     13163    /var/run/bumblebee.socket
unix  2      [ ACC ]     STREAM     LISTENING     23917    /run/user/1000/gnupg/S.gpg-agent
unix  2      [ ACC ]     STREAM     LISTENING     23919    /run/user/1000/gnupg/S.gpg-agent.browser
unix  2      [ ACC ]     STREAM     LISTENING     23921    /run/user/1000/bus
unix  2      [ ACC ]     STREAM     LISTENING     22590    @/tmp/.ICE-unix/693
unix  2      [ ACC ]     STREAM     LISTENING     22647    /run/user/118/wayland-0
unix  2      [ ACC ]     STREAM     LISTENING     11177    /run/user/1000/keyring/control
unix  2      [ ACC ]     STREAM     LISTENING     23750    /var/run/NetworkManager/private-dhcp
unix  2      [ ACC ]     STREAM     LISTENING     19850    @/tmp/dbus-hOFBHWJFqv
unix  2      [ ACC ]     STREAM     LISTENING     18248    @/tmp/dbus-N9OBLlTV
unix  2      [ ACC ]     STREAM     LISTENING     18394    @/tmp/.X11-unix/X1024
unix  2      [ ACC ]     STREAM     LISTENING     25186    @/tmp/dbus-7hAWJESu
unix  2      [ ACC ]     STREAM     LISTENING     22245    /run/user/1000/keyring/pkcs11
unix  2      [ ACC ]     STREAM     LISTENING     18246    @/tmp/dbus-EdXm47V8
unix  2      [ ACC ]     STREAM     LISTENING     22249    /run/user/1000/keyring/ssh

The error message upon connecting to the linux machine is just «some problem» :D

Источник

With the help of Centos forum resources, I added GUI (MATE Desktop) support to a dedicated Centos 7 web server (Centos 7 Live DVD — Can Gnome/GUI be installed later? viewtopic.php?f=47&t=60762).

While the MATE desktop is a convenient addition to the main server console, I would also like to provide remote GUI capability to my main workstation which is a Windows 7 desktop. I am trying to connect remotely to the MATE desktop using a Windows Remote Desktop client on the Windows side and xrdp on the Centos side, but am encountering a «some problem» VNC connection error which I think is coming from the Centos side:

xrdp screenshot.jpg
xrdp screenshot.jpg (72.36 KiB) Viewed 39473 times

The components I am using include:

Code: Select all

Windows:	Remote Desktop Connection Shell Version 6.3.9600 (Supports Network Level Authentication and RDP 8.1)
Linux:	CentOS Linux release 7.2.1511 (Core)
Linux:	xrdp.x86_64 version 1:0.9.0-4.el7 from @epel
Linux:	tigervnc.x86_64  version 1.3.1-9.el7  from @base
Linux:	tigervnc-server.x86_64 version 1.3.1-9.el7 from @base

My xdrp.log sequence for the failed session is as follows:

Code: Select all

[20170108-19:19:04] [INFO ] A connection received from: 10.0.0.154 port 51143
[20170108-19:19:04] [INFO ] An established connection closed to endpoint: 10.0.0.154:51143 - socket: 8
[20170108-19:19:04] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 7
[20170108-19:19:04] [CORE ] WARNING: Invalid x.509 certificate path defined, default path will be used: /etc/xrdp/cert.pem
[20170108-19:19:04] [WARN ] Invalid X.509 certificate path defined, default path will be used: /etc/xrdp/key.pem
[20170108-19:19:04] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 8
[20170108-19:19:04] [ERROR] Listening socket is in wrong state we terminate listener
[20170108-19:19:04] [INFO ] A connection received from: 10.0.0.154 port 51144
[20170108-19:19:04] [INFO ] An established connection closed to endpoint: 10.0.0.154:51144 - socket: 8
[20170108-19:19:04] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 7
[20170108-19:19:04] [CORE ] WARNING: Invalid x.509 certificate path defined, default path will be used: /etc/xrdp/cert.pem
[20170108-19:19:04] [WARN ] Invalid X.509 certificate path defined, default path will be used: /etc/xrdp/key.pem
[20170108-19:19:04] [DEBUG] xrdp_00001058_wm_login_mode_event_00000001
[20170108-19:19:04] [WARN ] local keymap file for 0x0409 found and dosen't match built in keymap, using local keymap file
[20170108-19:19:04] [DEBUG] returnvalue from xrdp_mm_connect 0
[20170108-19:19:07] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 12
[20170108-19:19:08] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 12
[20170108-19:19:09] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 12
[20170108-19:19:10] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 12
[20170108-19:19:11] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 12
[20170108-19:19:12] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 12
[20170108-19:19:13] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 12
[20170108-19:19:14] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 12
[20170108-19:19:15] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 12
[20170108-19:19:16] [DEBUG] VNC Error after security negotiation
[20170108-19:19:16] [DEBUG] VNC error before sending share flag
[20170108-19:19:16] [DEBUG] VNC error before receiving server init
[20170108-19:19:16] [DEBUG] VNC error before receiving pixel format
[20170108-19:19:16] [DEBUG] VNC error before receiving name length
[20170108-19:19:16] [DEBUG] VNC error before receiving name
[20170108-19:19:16] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 12
[20170108-19:19:16] [DEBUG] xrdp_mm_module_cleanup
[20170108-19:19:16] [DEBUG] VNC mod_exit
[20170108-19:19:16] [INFO ] An established connection closed to endpoint: 127.0.0.1:3350 - socket: 11

My xrdp-sesman.log sequence for the failed session is as follows:

Code: Select all

[20170108-19:17:18] [WARN ] [init:46] libscp initialized
[20170108-19:17:18] [CORE ] starting sesman with pid 4180
[20170108-19:17:18] [INFO ] listening...
[20170108-19:19:04] [INFO ] A connection received from: 127.0.0.1 port 38634
[20170108-19:19:04] [INFO ] scp thread on sck 8 started successfully
[20170108-19:19:04] [INFO ] ++ created session (access granted): username brian, ip 10.0.0.154:51144 - socket: 8
[20170108-19:19:04] [INFO ] starting Xvnc session...
[20170108-19:19:04] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 9
[20170108-19:19:04] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 9
[20170108-19:19:04] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 9
[20170108-19:19:04] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 9
[20170108-19:19:04] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 9
[20170108-19:19:04] [INFO ] An established connection closed to endpoint: 127.0.0.1:38634 - socket: 8
[20170108-19:19:04] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 7
[20170108-19:19:04] [INFO ] An established connection closed to endpoint: 127.0.0.1:38634 - socket: 8
[20170108-19:19:04] [ERROR] env_set_user: error creating .vnc dir
[20170108-19:19:04] [INFO ] Xvnc :11 -geometry 1280x768 -depth 24 -rfbauth /home/brian/.vnc/sesman_brian_passwd -bs -nolisten tcp -localhost -dpi 96 -depth 24  
[20170108-19:19:05] [INFO ] starting xrdp-sessvc - xpid=4188 - wmpid=4187
[20170108-19:19:05] [INFO ] ++ terminated session:  username brian, display :11.0, session_pid 4186, ip 10.0.0.154:51144 - socket: 8

I would be grateful if a community member more skilled than I (which I suspect is just about everyone) could provide some guidance in resolving this connection problem. I can provide additional .ini configuration information if that would be helpful. Thanks!

Источник

It’s not worth it — there is a better & less painful solution:

X11VNC

I spent at least 8 hours fighting the battle to connect from Windows 10 to Ubuntu 16 via xrpd and Windows rdp. I tried endless «solutions» that I found posted all over the web. I made progress, but never managed to fully solve it. Even if I had, though, it seems that this is weak setup anyway, because:

  • You can’t use the Unity Desktop, so your rdp has connect you to a completely different OS UI than what you would use as the Ubuntu standard.
  • You can’t be logged on already with that account. So if you were have a scenerio where sometimes you work directly on the Ubuntu machine, and sometimes you connect remotely, you’d have to be sure to log out to allow for that remote connection.
  • From what’ve read, once you have this, you have also fight a battle to get a «re-connection» mechanism working to re-enter an rdp session you left.
  • You have to manually enter credentials every time you log on. There is no way to save them on the client end and just connect instantly.

I’ve used a pile of different remote connection interfaces, and overall nothing beats the ease and quality of Windows RDP yet to my mind. A such, I was pretty fixated on using that. After fighting this long enough though, and finally throwing in the towel, I found that VNC pretty much works just as well in this context.

As I said initially, on the Ubuntu side I used «x11vnc». Refer to these directions for details on getting that fully setup:

How to setup x11vnc to access with graphical login screen?

On the Windows side, I used RealVNC Viewer: https://www.realvnc.com/en/connect/download/viewer/, which I already had installed and setup for a remote connection to a Mac on my LAN as well.

With this setup, I have NONE of the weaknesses outlined above. Further, in full screen mode, the display is just as good as it would be naturally. I see 0 lag, 0 blurring. I have a bi-directional clipboard working without any effort to get that…

In theory, you are supposed to be able to stack xrpd and x11vnc. See: http://c-nergy.be/blog/?p=5956
I tried that too, just to see if I could get it to work. I had no luck with that either. So I just said the hell with xrpd in the end, uninstalled it, and rolled back all the changes I made to my machine fighting with it (or least so of them).

Unless you have a major reason that you NEED RDP instead of VNC, I strongly recommend going this route I’ve described instead.

Источник

Понравилась статья? Поделить с друзьями:

Читайте также:

  • Xrdebugnew cpp как исправить ошибку
  • Xray ошибка p0504
  • Xray engine error report что это
  • Xrandr error of failed request badmatch
  • Xinit giving up xinit unable to connect to x server connection refused xinit server error

    • 0 0 голоса
    Рейтинг статьи
    Подписаться
    Уведомить о
    guest

    0 комментариев
    Старые
    Новые Популярные
    Межтекстовые Отзывы
    Посмотреть все комментарии