Linux rdesktop ERROR recv Connection reset by peer

Question

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?

score 18 · Accepted Answer · answered Feb 11 '14 at 16:06

18

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)"

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

REF

Thanks to Maccu Falchi

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

answered Feb 11 '14 at 16:06

BGBRUNO

809
1
8
18

1

Worked for me while trying to connect from Linux Mint client to Windows 2012 R2 Server. – Fuzzy Analysis Mar 30 '14 at 03:57
Tried this on a windows 10 host. It does not work, at least at the time being. The freerdp-x11 works. – minghua Jan 04 '18 at 08:49
@minghua In my last experience with new instal "#win10 on aws" this was default disabled. – BGBRUNO Jan 04 '18 at 13:49

James Baxter · Answer 2 · 2018-01-11T04:47:37.337

6

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

On Debian run

sudo apt-get install xfreerdp-x11

On Ubuntu run

sudo apt-get install freerdp-x11

On Fedora 22 run

sudo dnf install -y freerdp

Check here for more details

edited Jan 11 '18 at 04:47

answered Apr 07 '15 at 16:35

James Baxter

196
1
3

1

I needed to do `sudo apt-get install freerdp-x11` on ubuntu 14.04 – Chris Snow Jul 06 '15 at 10:53
1

Note, the executable is called `xfreerdp`. – luckydonald Sep 26 '17 at 16:06

score 2 · Answer 3 · answered Aug 19 '16 at 15:26

2

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.

answered Aug 19 '16 at 15:26

oratofu

21
2

Thank you for valuable info about colors - but you know that article is about connection right? :-) – BGBRUNO 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 00:50
This does not work on a windows 10 host at this moment. The freerdp does work. – minghua Jan 04 '18 at 08:53

score 1 · Answer 4 · answered Dec 15 '16 at 01:12

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.

I haven't encountered this error but good to know. – minghua Jan 04 '18 at 08:54 — minghua, Jan 04 '18 at 08:54

Linux rdesktop ERROR recv Connection reset by peer

4 Answers4