Version: (using KDE KDE 3.5.0) Installed from: SuSE RPMs I have several suse workstations and several win2k3 servers. All the servers and desktops are connected via 100Mbps switch. Usually, the first time I connect from krdc to the server, it will work (although not always), however, if I logout, and try again 5 minutes later, krdc will hang at 'establishing connection...'. If I try to connect from a windows XP machine to the same server, it always succeeds. I have tried connecting from home with krdc to the servers at work and it always succeeds (much higher latency). So, I am guessing that with the very fast network, the server is responding before krdc is listening and misses some initial handshake. I'd be happy to troubleshoot further with some guidance. Also, this problem occurs with both SuSE 9.3 and SuSE 10 (kde 3.4.2) Regards, John
KRDC is not currently maintained, and until someone takes over no further development is likely. Your bug will remain here in case someone decides to work on it, or until the future of KRDC is determined. If this is a problem with RDP (not VNC) you should determine if the behaviour happens when you call the program from the command line, to verify it is a problem with KRDC and not the client itself.
Jaison, Thanks for the status. I am trying to connect with RDP. As you suggest, I think the problem is with RDP because I get the same error when calling from the command line. Here is hoping someone will pickup development as KRDC is very useful! Thanks, John
Also seeing same problem on x86_64 (as well as x86) and kde 3.5
Since the problem is exhibited in rdesktop, there isn't likely to be anything KRDC could do about it anyway. :( You should poke around at the rdesktop site http://sourceforge.net/projects/rdesktop/ and see if they are aware of the problem. They may even already have a fix for it. I'm closing this bug for now; but we can reopen it if there is some sort of command-line workaround for this bug that could be implemented in KRDC.
Hi Jason, Sorry, I didn't understand that you wanted me to run rdesktop from the command line (because I didn't realize that krdc was a wrapper for rdesktop). I was simply running krdc from the command-line, duh! Anyway, rdesktop works fine and does not exhibit any problems, so I am sure that the problem is somewhere in krdc. I am reopening this bug. Thanks, John
I'm not able to duplicate to a local Windows XP server across a gigabit switch (nor to my 2K3 box, but that is on the other end of the DSL line). John: can you test this against a windows xp server? I'm trying to figure out how I can duplicate the problem.
Brad, Yep, I tested krdc (rdp) connection to a windows XP machine repetitively, and krdc connects without error every time, so it seems that the problem is limited to win2k3. John
John: thanks. I'll try to do some testing in the office.
I am on SUSE 10 (all updates) connecting to Win2k3 Ent Ed Server (all updates) & I see it hang also, across our managed gigabit LinkSys switch LAN. I did not notice difference between LAN & WAN. "rdesktop" seems to work OK for me to all our Windohs machines. Let me know if I can help in any way.
I see this in a Debian system too connecting to both W2000 and W2003 servers. I am using KDE 3.5.2. I can connect fine once - and then not a second time to the same server, even if I close and reconnect. Sometimes it is to a different server that I hang on. If I hang and run "pkill rdesktop" and try krdc again I connect fine. Using rdesktop from command line works everytime - and I have had to resort to using command line since krdc hangs too often. This doesn't happen with a VNC connection, only RDP.
Cade: are you on a very fast link?
I am on a 100Mb LAN.
I can confirm this bug on an up-to-date Gentoo box. Connecting to a Win2k3 server randomly hangs at "Establishing connection", running rdesktop from the command line works fine. I'm on a 100Mbit LAN with a gigabit backbone.
Dennis: can you explain what you mean by "randomly hangs"?
Whenever I try to access one of our Win2k3 Terminal Servers via RDP, I've got a chance of about, I don't know, 50% when it will work flawlessly. The other times I get the "Establishing connection" window and nothing else; I can't even close the window properly if I don't kill it manually. This happens on all of our servers (all with different hardware) seemingly randomly. Let me know if I can provide some more information to help track this down. Thanks. Dennis
This happens for me as well on OpenSuse 10.2 (I also had the problem on SLED 10). I am running 64bit OpenSuse. This message suggest maybe it's a 64 bit thing: http://www.archivesat.com/openSUSE_help/thread2811494.htm But I can't confirm that as I only run it on 64bit. So I run krdc and connect to an rdp server (win2k3) 50+% of the time it will just hang at the establishing connection and the close button doesn't work. Now the weird thing is if I ps and grab the rdesktop command (including the -X parameter) and run it from a command line while the window is hanging it all just works - the original rdesktop command closes, the one I just ran connects and krdc takes over that rdesktop.
In addition to my last comment the KDE version is 3.5.6
I might be able to add sth to this. I get similar behaviour with a Kubuntu Edgy machine. First login no problem, 2nd login never works. I see the rdesktop command that it is issuing, and if I execute that without the -X option and argument, I can log in. See below, there is a fialed login followed by a succeful login. To me it appears to be the -X option borking it. I am on a 1G ethernet network with client and server on same subnet. pq@picturequote:~$ rdesktop -g 800x600 -k en-us -X 0x1e0015b -a 8 beavis.commercecorp.com:3389 X Error of failed request: BadWindow (invalid Window parameter) Major opcode of failed request: 7 (X_ReparentWindow) Resource id in failed request: 0x1e0015b Serial number of failed request: 44 Current serial number in output stream: 46 pq@picturequote:~$ rdesktop -g 800x600 -k en-us -X 0x1e0015b -a 8 beavis.commercecorp.com:3389 X Error of failed request: BadWindow (invalid Window parameter) Major opcode of failed request: 7 (X_ReparentWindow) Resource id in failed request: 0x1e0015b Serial number of failed request: 44 Current serial number in output stream: 46 pq@picturequote:~$ rdesktop -g 800x600 -k en-us -a 8 beavis.commercecorp.com:3389 pq@picturequote:~$
Steve: are you on 64 bit?
I can confirm this for kubuntu 7.04 32bit 100 Mb/s lan.
*** This bug has been confirmed by popular vote. ***
Can you test if rdesktop (command line) has the same problem?
Brad - I can say that rdesktop on command line works every time. That is the only way I can reliably do any Remote Desktop connections. VNC connections work fine with krdc.
rdesktop doesn't have this problem, it works everytime, as Cade said. BTW: w2k3 was only tested.
I cannot reproduce this problem. Please reopen this report, if you still have the same issue with the KRDC in trunk (KDE 4).