PROBLEM

I use for remote desktop connection script rdesktop. On some machines I get common error without any value.

What can I do after "Connection reset by peer" error?

share|improve this question
up vote 16 down vote accepted

SOLUTION

From time to time I forget this setting. The vast majority of it means "Turn off Remote Desktop with NLA".

Set on target "Microsoft Windows (WIN)"

  1. run SystemPropertiesRemote.exe
  2. deselect "Allow connections only from computers running Remote Desktop with NLA"
  3. try to connect from linux client

REF

Thanks to Maccu Falchi

http://marcofalchi.blogspot.sk/2013/03/linux-rdesktop-windows-8-linux-error.html

share|improve this answer
1  
Worked for me while trying to connect from Linux Mint client to Windows 2012 R2 Server. – fuzzyanalysis Mar 30 '14 at 3:57

If you don't have that level of control over the server you are trying to connect to (or having a bit of chicken/egg situation), then use FreeRDP which support NLA.

On debian do

sudo apt-get install xfreerdp-x11

On Ubuntu do

sudo apt-get install freerdp-x11

On Fedora 22 do

sudo dnf install -y freerdp

Check here for more details

share|improve this answer
    
I needed to do sudo apt-get install freerdp-x11 on ubuntu 14.04 – Chris Snow Jul 6 '15 at 10:53
    
Note, the executable is called xfreerdp. – luckydonald Sep 26 '17 at 16:06

I've been dealing with the same issue. The cursor is there - you just can't see it.

So, instead of grabbing some cursors from Windows and hacking your way around this - just use the "-C" flag to use your current custom color map.

e.g. rdesktop -C -u -d xx.xx.xx.xx

This fixed it just fine for me, and needed no other workarounds.

share|improve this answer
    
Thank you for valuable info about colors - but you know that article is about connection right? :-) – BG Bruno Aug 19 '16 at 22:51
    
This worked. However, -u -d appears to mean "log in as user -d". Perhaps -d should be replaced with username. – John McGehee May 31 '17 at 0:50

Well, in my case it was not the NLA authentication setting on the server. What has changed -- the operating system on the server was re-installed and so the fingerprint (or the host key) has changed. The freerdp on linux stored the previous fingerprint in a file under your home folder ~/.freerdp/known_hosts.

The error comes from the fact that the server IP address is the same but the fingerprints don't match.

The solution is to clear or delete the ~/.freerdp/known_hosts file on the linux guest.

share|improve this answer

Your Answer

 
discard

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.