Bug #50690 SSH Connection to remote Windows machine throws an irritating error
Submitted: 28 Jan 2010 14:42 Modified: 29 May 2013 11:51
Reporter: Mike Lischke Email Updates:
Status: Not a Bug Impact on me:
None 
Category:MySQL Workbench: Administration Severity:S4 (Feature request)
Version:5.2.15 OS:Windows (Windows 7)
Assigned to: CPU Architecture:Any

[28 Jan 2010 14:42] Mike Lischke
Description:
WBA does not allow a remote SSH connection from a Windows 7 box (a VM actually) to a remote Windows 2008 server with a running SSH server. It works fine when doing that from OS X. The error message is

Error connecting SSH tunnel: No existing session

How to repeat:
On the home screen create a server instance to a remote Windows box using SSH with a key pair and no password. It might be important to know that I did not use the standard SSH port, but something like 22222.

Once you open it with a double click it will show the box after a couple of seconds. My SSH server shows there is an SSH connection running during that time.

Suggested fix:
n/a
[8 Feb 2010 12:53] Mike Lischke
A typical error message:

---------------------------
MySQL Workbench Error
---------------------------
Cannot Connect to Database Server

Your connection attempt failed for user 'root' from your host to server at localhost:3306:

  Error connecting SSH tunnel: No existing session

Please:

1 Check that mysql is running on server localhost

2 Check that mysql is running on port 3306 (note: 3306 is the default, but this can be changed)

3 Check the root has rights to connect to localhost from your address (mysql rights define what clients can connect to the server and from which machines) 

4 Make sure you are both providing a password if needed and using the correct password for localhost connecting from the host address you're connecting from
---------------------------
OK   
---------------------------
[10 Feb 2010 10:56] Mike Lischke
It seems my ssh keys got messed up and after I reassigned them the connection started to work. However the error message is highly irritating as it has nothing to do with the actual problem. Hence I changed this to a feature request, which is essentially:

If the server refused a connection because of wrong credentials/keys then tell the user exactly this fact.
[29 May 2013 11:51] Marcin Szalowicz
Confirmed with reporter that it's working as it should.