Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

So, I have a server that I have RDC (Remote Desktop Connection) set up on, and I am looking at making it globally available on the internet so that I can access it from anywhere. I am currently in the process of changing the password so that it's more secure now that it's going to be visible on the web, but I'm running into a bit of a snag.

I'll use some example passwords here.

  • Before I changed my password, I had full access using RDC and my previous password: abc123.

  • I used passwd to change my password from abc123 to d4f5g6. The change was successful, but is only fully recognized when I type it at the machine itself, but not from RDC

When I try to connect using RDC and use my new password, I get the following error:

connecting to sesman ip port 3350
sesman connect ok
sending login info to sesman
xrdp_mm_process_login_response: login successful for display
started connecting
connecting to
tcp connected
security level is 2 (1 = none, 2 = standard)
password failed
error - problem connecting

Note that the password is currently d4f5g6, and I only get this error when I use d4f5g6. If I use any other password including abc123, I get this error:

connecting to sesman ip port 3350
sesman connect ok
sending login info to sesman
xrdp_mm_process_login_response: login failed

Also note that I am typing these credentials within the connection, and they are not cached within RDC, so RDC doesn't seem to be playing into this at all.

So, it seems my correct password is getting through a first check just fine, but not through a second check? Here's the kicker; If I change my password back to abc123 directly on my server, then I can successfully connect to the server with RDC using abc123...

share|improve this question
Have you restarted the RDC server after the password change? – Zelda Dec 29 '13 at 7:06
I have restarted the RDC program, but not the actual server yet, no. I must try it in the morning though, and it will be silly if that's all there is to it. – MrMusAddict Dec 29 '13 at 7:09

I had a user with the same problem and after trying Sjaak's solution he still couldn't log in so on a whim I did a ps -ef|grep vnc and found a process with the users UID so I killed that process and had the user try again and login was successful.

share|improve this answer
Thx, Akers Your answer saved my ass – zeusakm Dec 2 '14 at 17:29
Awesome, this is also useful when U want to kick the f off the GUI to let the server breathe. – zeusakm Dec 22 '14 at 19:42
Did also solved my problem, but what can I do so those old processes is closed by itself? – Jesper Grann Laursen Mar 13 '15 at 11:27

On the Ubuntu server you can delete the (contents of) the .vnc hidden folder in your home directory. That caches your old password. It will be recreated the next time you login and will then use your new password.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.