cant connect to rdp or vnc via ssh tunnel in version 8.0

[exquest]

Binary package hint: remmina

I've been using Remmina for a while to remote into various computers. Up to this point it's worked great but this past weekend I upgraded my laptop to Ubuntu 10.10 which comes with Remmina 0.8.0.

When I try to connect to a remote RDP server via a ssh tunnel I get a message that says "Unable to connect to RDP server 127.0.0.1" even though I specified the server:port as I'm supposed to. Using the exact same settings I'm able to connect on my Ubuntu 10.04 desktop with Remmina 0.7.4.

the output of 'apt-cache policy remmina'
remmina:
  Installed: 0.8.0-1
  Candidate: 0.8.0-1
  Version table:
 *** 0.8.0-1 0
        500 http://mirrors.ecvps.com/ubuntu/ maverick/universe i386 Packages
        100 /var/lib/dpkg/status

If I can provide any further information let me know.

[Nick Booker (nmbooker)]

Ditto under Ubuntu 10.10, with Remmina 0.8.0. apt-cache policy remmina produces exactly the same as exquest posted.

I've clicked the 'yes it affects me' button.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[useResa (rdrijsen)]

I recently upgraded to Ubuntu 12.04 and, as the OP, have been using Remmina for several releases now to connect to remote servers. With the latest upgrade I have been faced with the issue as described: Unable to connect to RDP via ssh while the settings are identical to before the upgrade.

$ apt-cache policy remmina
remmina:
  Installed: 1.0.0-1ubuntu6
  Candidate: 1.0.0-1ubuntu6
  Version table:
 *** 1.0.0-1ubuntu6 0
        500 http://nl.archive.ubuntu.com/ubuntu/ precise-updates/main i386 Packages
        100 /var/lib/dpkg/status
     1.0.0-1ubuntu5 0
        500 http://nl.archive.ubuntu.com/ubuntu/ precise/main i386 Packages

$ apt-cache policy remmina-plugin-rdp
remmina-plugin-rdp:
  Installed: 1.0.0-1ubuntu6
  Candidate: 1.0.0-1ubuntu6
  Version table:
 *** 1.0.0-1ubuntu6 0
        500 http://nl.archive.ubuntu.com/ubuntu/ precise-updates/main i386 Packages
        100 /var/lib/dpkg/status
     1.0.0-1ubuntu5 0
        500 http://nl.archive.ubuntu.com/ubuntu/ precise/main i386 Packages

$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=12.04
DISTRIB_CODENAME=precise
DISTRIB_DESCRIPTION="Ubuntu 12.04 LTS"

$ uname -r
3.2.0-24-generic-pae

[useResa (rdrijsen)]

Update to my previous comment:
In my case it turned out that an expired password was the cause for the error message.
Once changed: By connecting to the server by another way and changing the password in the remmina connection properties it connects without issues

[Miklos Juhasz (mjuhasz)]

In my case there was a certificate validation error because of the tunneling: the certificate was issue for <hostname> and not <localhost> so the connection was refused. On the advanced tab I had to change the Security from Negotiate to RDP or TLS and then it worked.
I also had to delete my known_hosts file in .freerdp because of an offending key. I only learnt about this when I started remmina from commandline.

[Runar Ingebrigtsen (ringe)]

I removed the line for 127.0.0.1 in the .freerdp/known_hosts file and the problem disappeared. Thanks.

[penalvch (penalvch)]

exquest, thank you for reporting this bug to Ubuntu. Mavericks reached EOL on April 10, 2012.
See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases

Is this an issue on a supported release? If so, please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal:
cd /var/crash && sudo rm * ; sudo apt-get update && sudo apt-get -y upgrade && sudo service apport start force_start=1

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

Now reproduce the crash, then open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'. If you run the command against the crash report and a window pops up asking you to report this, but then never opens a new report, you would be affected by https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 . In order to WORKAROUND this, one would need to open the following file via a command line:
sudo nano /etc/apport/crashdb.conf

and comment out the line:
'problem_types': ['Bug', 'Package'],

by changing it to:
# 'problem_types': ['Bug', 'Package'],

Save, close, and try to file the crash report again via:
ubuntu-bug /var/crash/_my_crash_report.crash

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently.

Please do not attach your crash report manually to this report and reopen it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs