As in summary. I have several servers bookmarked and I'm unable to connect to any of them. No error messages, just blue screen. Reproducible: Always
rdesktop switches were stored for those servers in the configuration.
I see the problem, but do not have a great idea how to resolve it... I think there is no way to automatically convert additional parameters from rdesktop to freerdp. I could only remove them after the upgrade. Do you have a better idea?
(In reply to comment #2) > I see the problem, but do not have a great idea how to resolve it... > > I think there is no way to automatically convert additional parameters from > rdesktop to freerdp. It could be done, but it's not worth the effort. > I could only remove them after the upgrade. This is the optimal solution IMHO.
I had the same problem, but only happened with, I think, my windows 2008 R2 servers. I read this, and see that it may have to do with the extra settings I had in most of my bookmarks to redirect a local folder to the server as a connected drive. I removed that, as well as having to actually use the new? dialog to enter in the user and password (I never had these saved in the bookmark) (instead of letting the server ask for this, in its own dialog) Then connection works. Fedora 19, upgraded from 18, upgraded from 17. KDE 4.11.1 currently. KRDC 4.11.1-1 fc19 freerdp 1.0.2-2 fc19
I believe newer versions/features in Windows 7/8, etc. require authentication up front. I noticed that if I do not give a username and password xfreerdp actually asks for the password on the command line. I'll see if there is a way to make it work without giving a username and password up front.
Also, when we convert to the new xfreerdp 1.1 command line we will need to clear out user-entered command lines. I think we should pop-up a message if the user had any existing ones set. Then leave the current input but don't use it until the user edits it. Or we could just do the second thing and skip the popup message.
In one of the last updates we receive "freerdp 1.2.0_beta1+android9-1" which has new set of arguments. After this krdc can't connect (at all) to any windows server. Now I'm working in a command string.
Linux xxxxxxx 3.17.4-1-ARCH
KRDC stopped working for me, too since the latest update of freerdp. ArchLinux x64 (updated) KDE 4.14.3 krdc 4.14.3 freerdp 1.2.0_beta1+android9 I use it to connect to my VirtualBox VMs on a machine also running ArchLinux (headless) and can't connect to any of them. Running freerdp from console works, also Remmina does its job. I don't get any useful information from the console when running krdc from there.
For Freerdp 1.1 / 1.2 related issues, please see #341284.
I would like to set this issue as won't fix if there is this kind of option :p I think we have no plan and no effort to add new code to handle this and this issue will fade out day by day.