Xrdp login failed
I Am trying to login to Ubuntu machine from windows using RDP. Installed xrdp
and tight vnc but while connecting am getting following error
xrdp_mm_process_login_response:login failed
Steps followed to install XRDP:
sudo apt-get update .
sudo apt-get install tightvncserver
sudo apt-get install xrdp
sudo restart
After this tried logging with RDP and getting the error. could you give a step by step guide or other alternative methods, please?
windows-7 remote-desktop vnc xrdp tightvncserver
add a comment |
I Am trying to login to Ubuntu machine from windows using RDP. Installed xrdp
and tight vnc but while connecting am getting following error
xrdp_mm_process_login_response:login failed
Steps followed to install XRDP:
sudo apt-get update .
sudo apt-get install tightvncserver
sudo apt-get install xrdp
sudo restart
After this tried logging with RDP and getting the error. could you give a step by step guide or other alternative methods, please?
windows-7 remote-desktop vnc xrdp tightvncserver
I think it may help you solver this problem. unix.stackexchange.com/questions/106974/…
– Fangxin
Nov 22 '16 at 1:28
add a comment |
I Am trying to login to Ubuntu machine from windows using RDP. Installed xrdp
and tight vnc but while connecting am getting following error
xrdp_mm_process_login_response:login failed
Steps followed to install XRDP:
sudo apt-get update .
sudo apt-get install tightvncserver
sudo apt-get install xrdp
sudo restart
After this tried logging with RDP and getting the error. could you give a step by step guide or other alternative methods, please?
windows-7 remote-desktop vnc xrdp tightvncserver
I Am trying to login to Ubuntu machine from windows using RDP. Installed xrdp
and tight vnc but while connecting am getting following error
xrdp_mm_process_login_response:login failed
Steps followed to install XRDP:
sudo apt-get update .
sudo apt-get install tightvncserver
sudo apt-get install xrdp
sudo restart
After this tried logging with RDP and getting the error. could you give a step by step guide or other alternative methods, please?
windows-7 remote-desktop vnc xrdp tightvncserver
windows-7 remote-desktop vnc xrdp tightvncserver
edited May 17 '16 at 20:31
muru
1
1
asked May 17 '16 at 10:48
user545083
I think it may help you solver this problem. unix.stackexchange.com/questions/106974/…
– Fangxin
Nov 22 '16 at 1:28
add a comment |
I think it may help you solver this problem. unix.stackexchange.com/questions/106974/…
– Fangxin
Nov 22 '16 at 1:28
I think it may help you solver this problem. unix.stackexchange.com/questions/106974/…
– Fangxin
Nov 22 '16 at 1:28
I think it may help you solver this problem. unix.stackexchange.com/questions/106974/…
– Fangxin
Nov 22 '16 at 1:28
add a comment |
5 Answers
5
active
oldest
votes
I managed to fix this problem by editing the /etc/xrdp/sesman.ini
file and commenting out the requirement to group membership. Now you can access all accounts.
[Security]
AllowRootLogin=1
MaxLoginRetry=4
#TerminalServerUsers=tsusers
#TerminalServerAdmins=tsadmins
Evidently a user must be a member of tsusers which is supposed to be created by xrdp itself. This group was not created at xrdp installation in my case. I created the group and added users to the group. But this did not help. By commenting out the following lines, all users can rdp now.
add a comment |
Usually this error means that the password used is not the valid one (or credentials are not valid ones).
You should know that the XRDP login screen will use by default the English US keyboard layout. So, if you are using a different keyboard layout, you might be typing the wrong password in the xrdp login. Check that keyboard layout is correct... Just a guess :-)
add a comment |
Your x11 sessions might be locked or orphaned.
see this article
If you encountered this error
xrdp_mm_process_login_response: login failed
when you use the remote desktop connection to connection to a vnc session.
Even if you restart
xrdp
, the error still remains, the issue could be due to locked X11 session that was created byxrdp
.
To solve the issue, go to
/tmp/.X11-unix/
and find your X session and delete the session.
cd /tmp/.X11-unix
Do a listing
ls -l
Look at the sessions owned by you which you wished to delete
.....
.....
srwxrwxrwx 1 root root 0 Jul 9 2012 X0
srwxrwxrwx 1 user1 users 0 Jan 25 09:13 X1
srwxrwxrwx 1 user2 users 0 Jul 10 2012 X10
srwxrwxrwx 1 user3 users 0 Feb 19 13:31 X11
srwxrwxrwx 1 user4 users 0 Nov 20 15:10 X12
srwxrwxrwx 1 user5 users 0 Jul 10 2012 X13
.....
Delete the session...
If
xrdp
still fails, it seems that it is due to orphaned X--. Oncexrdp
hits an orphaned X-- which may or may not be from other users, the error will still remain.
To see the orphaned X11 session, you can run
vncserver
, which will return something like this
$ vncserver
Warning: Head-Node:1 is taken because of /tmp/.X11-unix/X1
Remove this file if there is no X server Head-Node:1
Delete all the orphaned X--
Restart the
xrdp
service and try the remote connection.
service xrdp restart
add a comment |
I had this problem as well. All I had to do was to use lower case for my user name at the RDP login prompt. I have a user name which includes an upper case character.
add a comment |
A less common, but hopefully useful solution to anyone else having this problem in a tunnel server setup similar to mine:
+--------------------------+ +-------------------+ +----------------+
| Mac OS X + MS RDP client | ==[ssh]==> | Ubuntu SSH server | ==[rdp]==> | Ubuntu Desktop |
+--------------------------+ +-------------------+ +----------------+
You must put the username and password into your MS RDP client. If you try and add it later at the remote login screen, you will first get the error. And when you try to log in using the remote login screen, you get password failed
, error - problem connecting
Other info
In case you want to do RDP tunneling over an SSH like me, here is what I did:
ssh -v -N -L 3389:192.168.1.3:3389 me@mypublicsshserver.mydomain.com
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f773626%2fxrdp-login-failed%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
5 Answers
5
active
oldest
votes
5 Answers
5
active
oldest
votes
active
oldest
votes
active
oldest
votes
I managed to fix this problem by editing the /etc/xrdp/sesman.ini
file and commenting out the requirement to group membership. Now you can access all accounts.
[Security]
AllowRootLogin=1
MaxLoginRetry=4
#TerminalServerUsers=tsusers
#TerminalServerAdmins=tsadmins
Evidently a user must be a member of tsusers which is supposed to be created by xrdp itself. This group was not created at xrdp installation in my case. I created the group and added users to the group. But this did not help. By commenting out the following lines, all users can rdp now.
add a comment |
I managed to fix this problem by editing the /etc/xrdp/sesman.ini
file and commenting out the requirement to group membership. Now you can access all accounts.
[Security]
AllowRootLogin=1
MaxLoginRetry=4
#TerminalServerUsers=tsusers
#TerminalServerAdmins=tsadmins
Evidently a user must be a member of tsusers which is supposed to be created by xrdp itself. This group was not created at xrdp installation in my case. I created the group and added users to the group. But this did not help. By commenting out the following lines, all users can rdp now.
add a comment |
I managed to fix this problem by editing the /etc/xrdp/sesman.ini
file and commenting out the requirement to group membership. Now you can access all accounts.
[Security]
AllowRootLogin=1
MaxLoginRetry=4
#TerminalServerUsers=tsusers
#TerminalServerAdmins=tsadmins
Evidently a user must be a member of tsusers which is supposed to be created by xrdp itself. This group was not created at xrdp installation in my case. I created the group and added users to the group. But this did not help. By commenting out the following lines, all users can rdp now.
I managed to fix this problem by editing the /etc/xrdp/sesman.ini
file and commenting out the requirement to group membership. Now you can access all accounts.
[Security]
AllowRootLogin=1
MaxLoginRetry=4
#TerminalServerUsers=tsusers
#TerminalServerAdmins=tsadmins
Evidently a user must be a member of tsusers which is supposed to be created by xrdp itself. This group was not created at xrdp installation in my case. I created the group and added users to the group. But this did not help. By commenting out the following lines, all users can rdp now.
edited Apr 5 '17 at 15:13
Zanna
50.4k13133241
50.4k13133241
answered Apr 5 '17 at 14:46
hungrydeveloperhungrydeveloper
412
412
add a comment |
add a comment |
Usually this error means that the password used is not the valid one (or credentials are not valid ones).
You should know that the XRDP login screen will use by default the English US keyboard layout. So, if you are using a different keyboard layout, you might be typing the wrong password in the xrdp login. Check that keyboard layout is correct... Just a guess :-)
add a comment |
Usually this error means that the password used is not the valid one (or credentials are not valid ones).
You should know that the XRDP login screen will use by default the English US keyboard layout. So, if you are using a different keyboard layout, you might be typing the wrong password in the xrdp login. Check that keyboard layout is correct... Just a guess :-)
add a comment |
Usually this error means that the password used is not the valid one (or credentials are not valid ones).
You should know that the XRDP login screen will use by default the English US keyboard layout. So, if you are using a different keyboard layout, you might be typing the wrong password in the xrdp login. Check that keyboard layout is correct... Just a guess :-)
Usually this error means that the password used is not the valid one (or credentials are not valid ones).
You should know that the XRDP login screen will use by default the English US keyboard layout. So, if you are using a different keyboard layout, you might be typing the wrong password in the xrdp login. Check that keyboard layout is correct... Just a guess :-)
edited Apr 5 '17 at 15:11
Zanna
50.4k13133241
50.4k13133241
answered Oct 19 '16 at 17:30
GriffonGriffon
729411
729411
add a comment |
add a comment |
Your x11 sessions might be locked or orphaned.
see this article
If you encountered this error
xrdp_mm_process_login_response: login failed
when you use the remote desktop connection to connection to a vnc session.
Even if you restart
xrdp
, the error still remains, the issue could be due to locked X11 session that was created byxrdp
.
To solve the issue, go to
/tmp/.X11-unix/
and find your X session and delete the session.
cd /tmp/.X11-unix
Do a listing
ls -l
Look at the sessions owned by you which you wished to delete
.....
.....
srwxrwxrwx 1 root root 0 Jul 9 2012 X0
srwxrwxrwx 1 user1 users 0 Jan 25 09:13 X1
srwxrwxrwx 1 user2 users 0 Jul 10 2012 X10
srwxrwxrwx 1 user3 users 0 Feb 19 13:31 X11
srwxrwxrwx 1 user4 users 0 Nov 20 15:10 X12
srwxrwxrwx 1 user5 users 0 Jul 10 2012 X13
.....
Delete the session...
If
xrdp
still fails, it seems that it is due to orphaned X--. Oncexrdp
hits an orphaned X-- which may or may not be from other users, the error will still remain.
To see the orphaned X11 session, you can run
vncserver
, which will return something like this
$ vncserver
Warning: Head-Node:1 is taken because of /tmp/.X11-unix/X1
Remove this file if there is no X server Head-Node:1
Delete all the orphaned X--
Restart the
xrdp
service and try the remote connection.
service xrdp restart
add a comment |
Your x11 sessions might be locked or orphaned.
see this article
If you encountered this error
xrdp_mm_process_login_response: login failed
when you use the remote desktop connection to connection to a vnc session.
Even if you restart
xrdp
, the error still remains, the issue could be due to locked X11 session that was created byxrdp
.
To solve the issue, go to
/tmp/.X11-unix/
and find your X session and delete the session.
cd /tmp/.X11-unix
Do a listing
ls -l
Look at the sessions owned by you which you wished to delete
.....
.....
srwxrwxrwx 1 root root 0 Jul 9 2012 X0
srwxrwxrwx 1 user1 users 0 Jan 25 09:13 X1
srwxrwxrwx 1 user2 users 0 Jul 10 2012 X10
srwxrwxrwx 1 user3 users 0 Feb 19 13:31 X11
srwxrwxrwx 1 user4 users 0 Nov 20 15:10 X12
srwxrwxrwx 1 user5 users 0 Jul 10 2012 X13
.....
Delete the session...
If
xrdp
still fails, it seems that it is due to orphaned X--. Oncexrdp
hits an orphaned X-- which may or may not be from other users, the error will still remain.
To see the orphaned X11 session, you can run
vncserver
, which will return something like this
$ vncserver
Warning: Head-Node:1 is taken because of /tmp/.X11-unix/X1
Remove this file if there is no X server Head-Node:1
Delete all the orphaned X--
Restart the
xrdp
service and try the remote connection.
service xrdp restart
add a comment |
Your x11 sessions might be locked or orphaned.
see this article
If you encountered this error
xrdp_mm_process_login_response: login failed
when you use the remote desktop connection to connection to a vnc session.
Even if you restart
xrdp
, the error still remains, the issue could be due to locked X11 session that was created byxrdp
.
To solve the issue, go to
/tmp/.X11-unix/
and find your X session and delete the session.
cd /tmp/.X11-unix
Do a listing
ls -l
Look at the sessions owned by you which you wished to delete
.....
.....
srwxrwxrwx 1 root root 0 Jul 9 2012 X0
srwxrwxrwx 1 user1 users 0 Jan 25 09:13 X1
srwxrwxrwx 1 user2 users 0 Jul 10 2012 X10
srwxrwxrwx 1 user3 users 0 Feb 19 13:31 X11
srwxrwxrwx 1 user4 users 0 Nov 20 15:10 X12
srwxrwxrwx 1 user5 users 0 Jul 10 2012 X13
.....
Delete the session...
If
xrdp
still fails, it seems that it is due to orphaned X--. Oncexrdp
hits an orphaned X-- which may or may not be from other users, the error will still remain.
To see the orphaned X11 session, you can run
vncserver
, which will return something like this
$ vncserver
Warning: Head-Node:1 is taken because of /tmp/.X11-unix/X1
Remove this file if there is no X server Head-Node:1
Delete all the orphaned X--
Restart the
xrdp
service and try the remote connection.
service xrdp restart
Your x11 sessions might be locked or orphaned.
see this article
If you encountered this error
xrdp_mm_process_login_response: login failed
when you use the remote desktop connection to connection to a vnc session.
Even if you restart
xrdp
, the error still remains, the issue could be due to locked X11 session that was created byxrdp
.
To solve the issue, go to
/tmp/.X11-unix/
and find your X session and delete the session.
cd /tmp/.X11-unix
Do a listing
ls -l
Look at the sessions owned by you which you wished to delete
.....
.....
srwxrwxrwx 1 root root 0 Jul 9 2012 X0
srwxrwxrwx 1 user1 users 0 Jan 25 09:13 X1
srwxrwxrwx 1 user2 users 0 Jul 10 2012 X10
srwxrwxrwx 1 user3 users 0 Feb 19 13:31 X11
srwxrwxrwx 1 user4 users 0 Nov 20 15:10 X12
srwxrwxrwx 1 user5 users 0 Jul 10 2012 X13
.....
Delete the session...
If
xrdp
still fails, it seems that it is due to orphaned X--. Oncexrdp
hits an orphaned X-- which may or may not be from other users, the error will still remain.
To see the orphaned X11 session, you can run
vncserver
, which will return something like this
$ vncserver
Warning: Head-Node:1 is taken because of /tmp/.X11-unix/X1
Remove this file if there is no X server Head-Node:1
Delete all the orphaned X--
Restart the
xrdp
service and try the remote connection.
service xrdp restart
edited Sep 19 '17 at 18:25
Zanna
50.4k13133241
50.4k13133241
answered May 17 '16 at 11:41
Frank SchrijverFrank Schrijver
363315
363315
add a comment |
add a comment |
I had this problem as well. All I had to do was to use lower case for my user name at the RDP login prompt. I have a user name which includes an upper case character.
add a comment |
I had this problem as well. All I had to do was to use lower case for my user name at the RDP login prompt. I have a user name which includes an upper case character.
add a comment |
I had this problem as well. All I had to do was to use lower case for my user name at the RDP login prompt. I have a user name which includes an upper case character.
I had this problem as well. All I had to do was to use lower case for my user name at the RDP login prompt. I have a user name which includes an upper case character.
answered Jun 9 '18 at 22:24
Carey G. ButlerCarey G. Butler
112
112
add a comment |
add a comment |
A less common, but hopefully useful solution to anyone else having this problem in a tunnel server setup similar to mine:
+--------------------------+ +-------------------+ +----------------+
| Mac OS X + MS RDP client | ==[ssh]==> | Ubuntu SSH server | ==[rdp]==> | Ubuntu Desktop |
+--------------------------+ +-------------------+ +----------------+
You must put the username and password into your MS RDP client. If you try and add it later at the remote login screen, you will first get the error. And when you try to log in using the remote login screen, you get password failed
, error - problem connecting
Other info
In case you want to do RDP tunneling over an SSH like me, here is what I did:
ssh -v -N -L 3389:192.168.1.3:3389 me@mypublicsshserver.mydomain.com
add a comment |
A less common, but hopefully useful solution to anyone else having this problem in a tunnel server setup similar to mine:
+--------------------------+ +-------------------+ +----------------+
| Mac OS X + MS RDP client | ==[ssh]==> | Ubuntu SSH server | ==[rdp]==> | Ubuntu Desktop |
+--------------------------+ +-------------------+ +----------------+
You must put the username and password into your MS RDP client. If you try and add it later at the remote login screen, you will first get the error. And when you try to log in using the remote login screen, you get password failed
, error - problem connecting
Other info
In case you want to do RDP tunneling over an SSH like me, here is what I did:
ssh -v -N -L 3389:192.168.1.3:3389 me@mypublicsshserver.mydomain.com
add a comment |
A less common, but hopefully useful solution to anyone else having this problem in a tunnel server setup similar to mine:
+--------------------------+ +-------------------+ +----------------+
| Mac OS X + MS RDP client | ==[ssh]==> | Ubuntu SSH server | ==[rdp]==> | Ubuntu Desktop |
+--------------------------+ +-------------------+ +----------------+
You must put the username and password into your MS RDP client. If you try and add it later at the remote login screen, you will first get the error. And when you try to log in using the remote login screen, you get password failed
, error - problem connecting
Other info
In case you want to do RDP tunneling over an SSH like me, here is what I did:
ssh -v -N -L 3389:192.168.1.3:3389 me@mypublicsshserver.mydomain.com
A less common, but hopefully useful solution to anyone else having this problem in a tunnel server setup similar to mine:
+--------------------------+ +-------------------+ +----------------+
| Mac OS X + MS RDP client | ==[ssh]==> | Ubuntu SSH server | ==[rdp]==> | Ubuntu Desktop |
+--------------------------+ +-------------------+ +----------------+
You must put the username and password into your MS RDP client. If you try and add it later at the remote login screen, you will first get the error. And when you try to log in using the remote login screen, you get password failed
, error - problem connecting
Other info
In case you want to do RDP tunneling over an SSH like me, here is what I did:
ssh -v -N -L 3389:192.168.1.3:3389 me@mypublicsshserver.mydomain.com
answered 10 hours ago
Sridhar-SarnobatSridhar-Sarnobat
894711
894711
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f773626%2fxrdp-login-failed%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
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
Required, but never shown
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
Required, but never shown
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
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I think it may help you solver this problem. unix.stackexchange.com/questions/106974/…
– Fangxin
Nov 22 '16 at 1:28