> side-effects on other X applications-everything continues to work except > and keypresses were being sent to the remote server. If I kill the client and reconnect, I see that the mouse clicks > responds, but I am unable to see the results of any mouse clicks or > (30sec-1min) after login, the connection freezes-the pointer still > In Gutsy and Hardy, I am able to connect to the server via RDP. > Status in “rdesktop” package in Debian: New > Status in “rdesktop” package in Ubuntu: Incomplete > You received this bug notification because you are a direct subscriber > rdesktop freezes shortly after successful connection > current top window of any application, you'll likely not encounter the > Again, if you'll keep your window maximized or just active under the > And a more interesting thing is that, this sometimes happens with other > this rdesktop behaviour but couldn't even though at one I suspected Compiz This is something I feel that Gnome/Rdesktop does and not the
#Microsoft remote desktop connection reset by peer windows#
> This occurs when you'll keep your rdesktop windows minimized for about > joebodo, I've been seeing this problem for almost two years the time since Thanks for that info - one less frustration to contend with. I do use Ubuntu but only as a server operating system and appreciate its stability for a few servers rolling tools its currently running in, just because have don't much time to do more to fix such sort of issues unfortunately which I was facing every minute when I had it. Its not just the rdesktop but other tools as well which wastes hundreds of hours of thousands of users each day battling around their ways and finding the fixes for such 'lost' bugs like this one! :P Not an average normal user would find that but if you're an advanced user and you use rdesktop regularly you'll see a lot of ill behaviours of rdesktop in all Linux distros.įor me Linux is just a server OS far away from the needs of today's power desktop users and Ubuntu needs to learn more discipline in better desktop computing cause of the proclaims it made. This is an issue with the Ubuntu and few other Linux distributions' core. I'm beginning to think this is something more deeply rooted than just rdesktop, since even running Windows XP in a virtual machine gives me the same results.Įxactly! The same issue I noticed too. I have the same thing happen in a Virtual machine running Windows XP. I have also installed Windows XP on one of the computers that was not working with Ubuntu and it worked correctly as well. The connection works flawlessly on a Windows XP machine on the same network. WARNING: Remote desktop does not support colour depth 24 falling back to 16 Here's the message I get back from rdesktop when running the above command:
I did get one laptop to work correctly, and it was not due to any additional configuration or modification, it worked directly after installing a standard Ubuntu installation however it was very very slow, to the point where it was not usable.
If I let it run for about 3 minutes I will get a response of "Connection reset by peer". I then get a window which displays as shown in the screenshot, and it completely stops. I've attached a screenshot of what I get. I have installed Ubuntu Hardy on over 6 machines with the same effect.
Maybe I'm not running something correctly, on either side. Please contact me if further information is needed to diagnose. php?p=4709775ĭiscusses what appears to be the same problem experienced by other users. However it worked fine under Dapper.ĭropping -z or -P makes the connection quit faster, as does using a higher color depth. I tried the Gutsy rdesktop package and also tried compiling the latest rdesktop cvs, all with the same results. This behavior was identical under Gutsy and on two different Hardy machines, regardless of network interface. There are no side-effects on other X applications-everything continues to work except for rdesktop. If I kill the client and reconnect, I see that the mouse clicks and keypresses were being sent to the remote server.
Shortly (30sec-1min) after login, the connection freezes-the pointer still responds, but I am unable to see the results of any mouse clicks or keypresses. In Gutsy and Hardy, I am able to connect to the server via RDP.