Using XRDP without local VNC server
Clash Royale CLAN TAG#URR8PPP
up vote
4
down vote
favorite
According to xrdp docs it should be possible to connect remotely without using a local VNC server:
xrdp can connect to a locally created X.org session
with the xorgxrdp drivers [my emphasis], to a VNC X11 server, and forward to
another RDP server.
I can connect with RDP from Windows:
Then I select Xorg session and supply username and password. After some timeout an error pops up about an unknown connection problem.
This is tail /var/log/xrdp.log and tail /var/log/xrdp-sesman.log output:
[DEBUG] Closed socket 17 (AF_UNIX)
...
[DEBUG] Closed socket 17 (AF_UNIX)
[DEBUG] xrdp_wm_log_msg: some problem
[DEBUG] xrdp_mm_module_cleanup
[DEBUG] Closed socket 16 (AF_INET6 ::1 port 38094)
dmesg doesn't show any problems nor references to Xorg or similar. ps -A | grep rdp shows xrdp and xrdp-sesman processes running. Tried connecting with Windows 7 to Debian: same problem. xrdp.ini and sasman.ini:
In sesman.ini the AlwaysGroupCheck=false. The startwm.sh:
Any ideas? Running on a virtualized minimal, clean Debian 9.1 installation. Only only lxde-core and xrdp installed with apt-get. (No errors during installation.) xorgxrdp drivers installed (since they depend on xrdp).
debian lxde xrdp
asked Aug 29 '17 at 8:11
Davor Josipovic
206210
 |Â
show 13 more comments
up vote
4
down vote
favorite
According to xrdp docs it should be possible to connect remotely without using a local VNC server:
xrdp can connect to a locally created X.org session
with the xorgxrdp drivers [my emphasis], to a VNC X11 server, and forward to
another RDP server.
I can connect with RDP from Windows:
Then I select Xorg session and supply username and password. After some timeout an error pops up about an unknown connection problem.
This is tail /var/log/xrdp.log and tail /var/log/xrdp-sesman.log output:
[DEBUG] Closed socket 17 (AF_UNIX)
...
[DEBUG] Closed socket 17 (AF_UNIX)
[DEBUG] xrdp_wm_log_msg: some problem
[DEBUG] xrdp_mm_module_cleanup
[DEBUG] Closed socket 16 (AF_INET6 ::1 port 38094)
dmesg doesn't show any problems nor references to Xorg or similar. ps -A | grep rdp shows xrdp and xrdp-sesman processes running. Tried connecting with Windows 7 to Debian: same problem. xrdp.ini and sasman.ini:
In sesman.ini the AlwaysGroupCheck=false. The startwm.sh:
Any ideas? Running on a virtualized minimal, clean Debian 9.1 installation. Only only lxde-core and xrdp installed with apt-get. (No errors during installation.) xorgxrdp drivers installed (since they depend on xrdp).
debian lxde xrdp
asked Aug 29 '17 at 8:11
Davor Josipovic
206210
Did you compile xrdp and xorgxrdp from source? xrdp must be compiled and installed before xorgxrdp. If not what versions? What desktop are you using? You may want to install lxde desktop to help with debugging.xrdp.iniandsesman.iniusing default settings? What aboutvar/log/xrdp-sesman.logStrange error in xrdp log "some problem"... Does dmesg have any useful info?
– jc__
Aug 29 '17 at 14:40
@jc__, I didn't compile. I first installedlxde-core. Then, once logged in, installedxrdpwhich has a dependency onxorgxrdp. I'll update the question with other logs.
– Davor Josipovic
Aug 29 '17 at 15:27
Lets do some background checking: Verify the services are runningps -A | grep rdp. You should see bothxrdpandxrdp-sesman. You are using the selection Xorg, so check the Xorg inxrdp.ini. Should belibxup.solibrary,ip=127.0.0.1port=-1then check the Xorg section insesman.inithese are the parameters passed to Xorg. Note the log name.param=.xorgxrdp.%s.log. see your home directory for that log.
– jc__
Aug 29 '17 at 17:44
Insesman.iniverify theAlwaysGroupCheck=iffalsethe login user does not need to be in the group assigned byTerminalServerUsers=
– jc__
Aug 29 '17 at 17:46
Oh yeah, What version of windows are you connecting with? If its above 7.. might be a problem. I had to compile with the--enable-painteroption to make work with Win10.
– jc__
Aug 29 '17 at 17:53
 |Â
show 13 more comments
up vote
4
down vote
favorite
up vote
4
down vote
favorite
According to xrdp docs it should be possible to connect remotely without using a local VNC server:
xrdp can connect to a locally created X.org session
with the xorgxrdp drivers [my emphasis], to a VNC X11 server, and forward to
another RDP server.
I can connect with RDP from Windows:
Then I select Xorg session and supply username and password. After some timeout an error pops up about an unknown connection problem.
This is tail /var/log/xrdp.log and tail /var/log/xrdp-sesman.log output:
[DEBUG] Closed socket 17 (AF_UNIX)
...
[DEBUG] Closed socket 17 (AF_UNIX)
[DEBUG] xrdp_wm_log_msg: some problem
[DEBUG] xrdp_mm_module_cleanup
[DEBUG] Closed socket 16 (AF_INET6 ::1 port 38094)
dmesg doesn't show any problems nor references to Xorg or similar. ps -A | grep rdp shows xrdp and xrdp-sesman processes running. Tried connecting with Windows 7 to Debian: same problem. xrdp.ini and sasman.ini:
In sesman.ini the AlwaysGroupCheck=false. The startwm.sh:
Any ideas? Running on a virtualized minimal, clean Debian 9.1 installation. Only only lxde-core and xrdp installed with apt-get. (No errors during installation.) xorgxrdp drivers installed (since they depend on xrdp).
debian lxde xrdp
asked Aug 29 '17 at 8:11
Davor Josipovic
206210
According to xrdp docs it should be possible to connect remotely without using a local VNC server:
xrdp can connect to a locally created X.org session
with the xorgxrdp drivers [my emphasis], to a VNC X11 server, and forward to
another RDP server.
I can connect with RDP from Windows:
Then I select Xorg session and supply username and password. After some timeout an error pops up about an unknown connection problem.
This is tail /var/log/xrdp.log and tail /var/log/xrdp-sesman.log output:
[DEBUG] Closed socket 17 (AF_UNIX)
...
[DEBUG] Closed socket 17 (AF_UNIX)
[DEBUG] xrdp_wm_log_msg: some problem
[DEBUG] xrdp_mm_module_cleanup
[DEBUG] Closed socket 16 (AF_INET6 ::1 port 38094)
dmesg doesn't show any problems nor references to Xorg or similar. ps -A | grep rdp shows xrdp and xrdp-sesman processes running. Tried connecting with Windows 7 to Debian: same problem. xrdp.ini and sasman.ini:
In sesman.ini the AlwaysGroupCheck=false. The startwm.sh:
Any ideas? Running on a virtualized minimal, clean Debian 9.1 installation. Only only lxde-core and xrdp installed with apt-get. (No errors during installation.) xorgxrdp drivers installed (since they depend on xrdp).
debian lxde xrdp
debian lxde xrdp
asked Aug 29 '17 at 8:11
Davor Josipovic
206210
asked Aug 29 '17 at 8:11
Davor Josipovic
206210
edited Aug 29 '17 at 21:13
asked Aug 29 '17 at 8:11
Davor Josipovic
206210
asked Aug 29 '17 at 8:11
Davor Josipovic
206210
asked Aug 29 '17 at 8:11
Davor Josipovic
206210
206210
Did you compile xrdp and xorgxrdp from source? xrdp must be compiled and installed before xorgxrdp. If not what versions? What desktop are you using? You may want to install lxde desktop to help with debugging.xrdp.iniandsesman.iniusing default settings? What aboutvar/log/xrdp-sesman.logStrange error in xrdp log "some problem"... Does dmesg have any useful info?
– jc__
Aug 29 '17 at 14:40
@jc__, I didn't compile. I first installedlxde-core. Then, once logged in, installedxrdpwhich has a dependency onxorgxrdp. I'll update the question with other logs.
– Davor Josipovic
Aug 29 '17 at 15:27
Lets do some background checking: Verify the services are runningps -A | grep rdp. You should see bothxrdpandxrdp-sesman. You are using the selection Xorg, so check the Xorg inxrdp.ini. Should belibxup.solibrary,ip=127.0.0.1port=-1then check the Xorg section insesman.inithese are the parameters passed to Xorg. Note the log name.param=.xorgxrdp.%s.log. see your home directory for that log.
– jc__
Aug 29 '17 at 17:44
Insesman.iniverify theAlwaysGroupCheck=iffalsethe login user does not need to be in the group assigned byTerminalServerUsers=
– jc__
Aug 29 '17 at 17:46
Oh yeah, What version of windows are you connecting with? If its above 7.. might be a problem. I had to compile with the--enable-painteroption to make work with Win10.
– jc__
Aug 29 '17 at 17:53
 |Â
show 13 more comments
Did you compile xrdp and xorgxrdp from source? xrdp must be compiled and installed before xorgxrdp. If not what versions? What desktop are you using? You may want to install lxde desktop to help with debugging.xrdp.iniandsesman.iniusing default settings? What aboutvar/log/xrdp-sesman.logStrange error in xrdp log "some problem"... Does dmesg have any useful info?
– jc__
Aug 29 '17 at 14:40
@jc__, I didn't compile. I first installedlxde-core. Then, once logged in, installedxrdpwhich has a dependency onxorgxrdp. I'll update the question with other logs.
– Davor Josipovic
Aug 29 '17 at 15:27
Lets do some background checking: Verify the services are runningps -A | grep rdp. You should see bothxrdpandxrdp-sesman. You are using the selection Xorg, so check the Xorg inxrdp.ini. Should belibxup.solibrary,ip=127.0.0.1port=-1then check the Xorg section insesman.inithese are the parameters passed to Xorg. Note the log name.param=.xorgxrdp.%s.log. see your home directory for that log.
– jc__
Aug 29 '17 at 17:44
Insesman.iniverify theAlwaysGroupCheck=iffalsethe login user does not need to be in the group assigned byTerminalServerUsers=
– jc__
Aug 29 '17 at 17:46
Oh yeah, What version of windows are you connecting with? If its above 7.. might be a problem. I had to compile with the--enable-painteroption to make work with Win10.
– jc__
Aug 29 '17 at 17:53
Did you compile xrdp and xorgxrdp from source? xrdp must be compiled and installed before xorgxrdp. If not what versions? What desktop are you using? You may want to install lxde desktop to help with debugging.
xrdp.ini and sesman.ini using default settings? What about var/log/xrdp-sesman.log Strange error in xrdp log "some problem"... Does dmesg have any useful info?– jc__
Aug 29 '17 at 14:40
Did you compile xrdp and xorgxrdp from source? xrdp must be compiled and installed before xorgxrdp. If not what versions? What desktop are you using? You may want to install lxde desktop to help with debugging.
xrdp.ini and sesman.ini using default settings? What about var/log/xrdp-sesman.log Strange error in xrdp log "some problem"... Does dmesg have any useful info?– jc__
Aug 29 '17 at 14:40
@jc__, I didn't compile. I first installed
lxde-core. Then, once logged in, installed xrdp which has a dependency on xorgxrdp. I'll update the question with other logs.– Davor Josipovic
Aug 29 '17 at 15:27
@jc__, I didn't compile. I first installed
lxde-core. Then, once logged in, installed xrdp which has a dependency on xorgxrdp. I'll update the question with other logs.– Davor Josipovic
Aug 29 '17 at 15:27
Lets do some background checking: Verify the services are running
ps -A | grep rdp. You should see both xrdp and xrdp-sesman. You are using the selection Xorg, so check the Xorg in xrdp.ini. Should be libxup.so library, ip=127.0.0.1 port=-1 then check the Xorg section in sesman.ini these are the parameters passed to Xorg. Note the log name. param=.xorgxrdp.%s.log. see your home directory for that log.– jc__
Aug 29 '17 at 17:44
Lets do some background checking: Verify the services are running
ps -A | grep rdp. You should see both xrdp and xrdp-sesman. You are using the selection Xorg, so check the Xorg in xrdp.ini. Should be libxup.so library, ip=127.0.0.1 port=-1 then check the Xorg section in sesman.ini these are the parameters passed to Xorg. Note the log name. param=.xorgxrdp.%s.log. see your home directory for that log.– jc__
Aug 29 '17 at 17:44
In
sesman.ini verify the AlwaysGroupCheck= if false the login user does not need to be in the group assigned by TerminalServerUsers=– jc__
Aug 29 '17 at 17:46
In
sesman.ini verify the AlwaysGroupCheck= if false the login user does not need to be in the group assigned by TerminalServerUsers=– jc__
Aug 29 '17 at 17:46
Oh yeah, What version of windows are you connecting with? If its above 7.. might be a problem. I had to compile with the
--enable-painter option to make work with Win10.– jc__
Aug 29 '17 at 17:53
Oh yeah, What version of windows are you connecting with? If its above 7.. might be a problem. I had to compile with the
--enable-painter option to make work with Win10.– jc__
Aug 29 '17 at 17:53
 |Â
show 13 more comments
2 Answers
2
active
oldest
votes
up vote
6
down vote
accepted
This bug report has the same symptoms as described in the question. Seems xserver-xorg-legacy package is the culprit. So to make it work, it boils down to the following two commands:
apt-get purge xserver-xorg-legacy
apt-get install xrdp
The required services are started automatically after install. No need to reboot. Connecting and authenticating should automatically show the desktop.
I do not know though what the consequences are of removing xserver-xorg-legacy. In the bug report it is mentioned to remove if not needed.
answered Aug 29 '17 at 21:10
Davor Josipovic
206210
add a comment |Â
up vote
0
down vote
You can refer to the question!
Attention: you need to use
dpkg-reconfigure xserver-xorg-legacycommand to change the setting in debian 9.
answered 3 mins ago
li1234yun
1
New contributor
li1234yun is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
6
down vote
accepted
This bug report has the same symptoms as described in the question. Seems xserver-xorg-legacy package is the culprit. So to make it work, it boils down to the following two commands:
apt-get purge xserver-xorg-legacy
apt-get install xrdp
The required services are started automatically after install. No need to reboot. Connecting and authenticating should automatically show the desktop.
I do not know though what the consequences are of removing xserver-xorg-legacy. In the bug report it is mentioned to remove if not needed.
answered Aug 29 '17 at 21:10
Davor Josipovic
206210
add a comment |Â
up vote
6
down vote
accepted
This bug report has the same symptoms as described in the question. Seems xserver-xorg-legacy package is the culprit. So to make it work, it boils down to the following two commands:
apt-get purge xserver-xorg-legacy
apt-get install xrdp
The required services are started automatically after install. No need to reboot. Connecting and authenticating should automatically show the desktop.
I do not know though what the consequences are of removing xserver-xorg-legacy. In the bug report it is mentioned to remove if not needed.
answered Aug 29 '17 at 21:10
Davor Josipovic
206210
add a comment |Â
up vote
6
down vote
accepted
up vote
6
down vote
accepted
This bug report has the same symptoms as described in the question. Seems xserver-xorg-legacy package is the culprit. So to make it work, it boils down to the following two commands:
apt-get purge xserver-xorg-legacy
apt-get install xrdp
The required services are started automatically after install. No need to reboot. Connecting and authenticating should automatically show the desktop.
I do not know though what the consequences are of removing xserver-xorg-legacy. In the bug report it is mentioned to remove if not needed.
answered Aug 29 '17 at 21:10
Davor Josipovic
206210
This bug report has the same symptoms as described in the question. Seems xserver-xorg-legacy package is the culprit. So to make it work, it boils down to the following two commands:
apt-get purge xserver-xorg-legacy
apt-get install xrdp
The required services are started automatically after install. No need to reboot. Connecting and authenticating should automatically show the desktop.
I do not know though what the consequences are of removing xserver-xorg-legacy. In the bug report it is mentioned to remove if not needed.
answered Aug 29 '17 at 21:10
Davor Josipovic
206210
answered Aug 29 '17 at 21:10
Davor Josipovic
206210
answered Aug 29 '17 at 21:10
Davor Josipovic
206210
answered Aug 29 '17 at 21:10
Davor Josipovic
206210
206210
add a comment |Â
add a comment |Â
up vote
0
down vote
You can refer to the question!
Attention: you need to use
dpkg-reconfigure xserver-xorg-legacycommand to change the setting in debian 9.
answered 3 mins ago
li1234yun
1
New contributor
li1234yun is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |Â
up vote
0
down vote
You can refer to the question!
Attention: you need to use
dpkg-reconfigure xserver-xorg-legacycommand to change the setting in debian 9.
answered 3 mins ago
li1234yun
1
New contributor
li1234yun is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |Â
up vote
0
down vote
up vote
0
down vote
You can refer to the question!
Attention: you need to use
dpkg-reconfigure xserver-xorg-legacycommand to change the setting in debian 9.
answered 3 mins ago
li1234yun
1
New contributor
li1234yun is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
You can refer to the question!
Attention: you need to use
dpkg-reconfigure xserver-xorg-legacycommand to change the setting in debian 9.
answered 3 mins ago
li1234yun
1
New contributor
li1234yun is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 3 mins ago
li1234yun
1
New contributor
li1234yun is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 3 mins ago
li1234yun
1
answered 3 mins ago
li1234yun
1
1
New contributor
li1234yun is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
li1234yun is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
li1234yun is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f389005%2fusing-xrdp-without-local-vnc-server%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Did you compile xrdp and xorgxrdp from source? xrdp must be compiled and installed before xorgxrdp. If not what versions? What desktop are you using? You may want to install lxde desktop to help with debugging.
xrdp.iniandsesman.iniusing default settings? What aboutvar/log/xrdp-sesman.logStrange error in xrdp log "some problem"... Does dmesg have any useful info?– jc__
Aug 29 '17 at 14:40
@jc__, I didn't compile. I first installed
lxde-core. Then, once logged in, installedxrdpwhich has a dependency onxorgxrdp. I'll update the question with other logs.– Davor Josipovic
Aug 29 '17 at 15:27
Lets do some background checking: Verify the services are running
ps -A | grep rdp. You should see bothxrdpandxrdp-sesman. You are using the selection Xorg, so check the Xorg inxrdp.ini. Should belibxup.solibrary,ip=127.0.0.1port=-1then check the Xorg section insesman.inithese are the parameters passed to Xorg. Note the log name.param=.xorgxrdp.%s.log. see your home directory for that log.– jc__
Aug 29 '17 at 17:44
In
sesman.iniverify theAlwaysGroupCheck=iffalsethe login user does not need to be in the group assigned byTerminalServerUsers=– jc__
Aug 29 '17 at 17:46
Oh yeah, What version of windows are you connecting with? If its above 7.. might be a problem. I had to compile with the
--enable-painteroption to make work with Win10.– jc__
Aug 29 '17 at 17:53