I've been using Toad for some time now and have a problem. I have a MySQL database on the web that I am trying to connect to but I keep getting 10061 errors. Sometime I get the message "Can't connect to SSH server on 'nnn.nnn.nn.nnn': Server did not respond within the specified timeout interval" (where nnn etc is the IP address of the server) I can connect via PuTTY and even execute commands on the db server, but when I try and connect using Toad I get nowhere.
Yes, if I set up the tunnel manually with PuTTY it works. Not if I use Toad. I have Toad version 184.108.40.2061 installed on one computer, version 220.127.116.115 on another.
The MySQL databases that I'm trying to connect to have the following versions: 5.0.92 - this is the one I can connect using PuTTY but not Toad (both Toad versions as above) 5.0.51 - I can connect to this via Toad (version 18.104.22.1681, don't have the connection set up for 22.214.171.1245)
I get this in Toad 6.3, as well. It is a Toad issue. It took me some time to come up with a reasonable workaround (e.g. I couldn't use two applications, like PUTTY to tunnel first before using Toad. And, I did not want to open port 3306 to the world to use direct TCP connection).
The quick answer - use the server's IP address instead of 'localhost' or '127.0.0.1'. For whatever reason, TOAD is broken if you try to use 'localhost' or '127.0.0.1' as the mysql server IP address via SSH.
So, just configure your connection using all of the 'correct' SSH and MYSQL information you normally would, but instead of 'localhost' or '127.0.0.1' for the database server name/IP, use the server's IP address (use the internal IP address when using an AWS EC2 instance).
You will have to grant priveleges to the local host IP address, which is not a security issue, at all.