MySQL Bugs: #50024: Workbench cannot connect over VPN (but CLI can)

Bug #50024	Workbench cannot connect over VPN (but CLI can)
Submitted:	2 Jan 2010 8:27	Modified:	19 Feb 2010 13:02
Reporter:	Jesse Pinho	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench	Severity:	S1 (Critical)
Version:	5.2.11 Beta	OS:	MacOS (10.6 (Snow Leopard))
Assigned to:		CPU Architecture:	Any
Tags:	connection problem, error 4, vpn

Description:
At our office, we are running a Microsoft VPN server (the one built into Windows Server 2003), and an Ubuntu (9.10) MySQL server.

When I connect to the VPN, I can't connect to the database server using Workbench. I have double-, triple-, quadruple-, etc.-checked my settings in Workbench, but to no avail.

HOWEVER, when I open mysql in the command line, I CAN connect to the database (and query it and everything). Furthermore, I downloaded the archived version of GUI tools, and Query Browser was able to access the server as well.

Here is the entire error I get:

Cannot Connect to Database Server
Your connection attempt failed for user 'root' from your host to server at 10.0.0.11:3306:
  Can't connect to MySQL server on '10.0.0.11' (4)

Please:
1 Check that mysql is running on server 10.0.0.11
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 10.0.0.11 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 10.0.0.11 connecting from the host address you're connecting from

How to repeat:
1. Connect to VPN
2. Set up connection to VPN server
3. Try to connect

Suggested fix:
No idea. This appears to be a bug embedded in the problem.

embedded in the program*

Please give me out from:

SHOW CREATE TABLE mysql.user;
SHOW VARIABLES LIKE '%char%';

Additionally I need to know if your user and/or password is using signs that aren't letters from English alphabet.

Susan,

I assume you meant to issue these commands via the command line, not via Workbench (since I can't even connect via Workbench)? Here's what I got:

mysql> show create table mysql.user;
ERROR 1142 (42000): SELECT command denied to user 'root'@'10.0.0.115' for table 'user'

mysql> show variables like '%char%';
+--------------------------+----------------------------+
| Variable_name            | Value                      |
+--------------------------+----------------------------+
| character_set_client     | latin1                     | 
| character_set_connection | latin1                     | 
| character_set_database   | latin1                     | 
| character_set_filesystem | binary                     | 
| character_set_results    | latin1                     | 
| character_set_server     | latin1                     | 
| character_set_system     | utf8                       | 
| character_sets_dir       | /usr/share/mysql/charsets/ | 
+--------------------------+----------------------------+

My password has only alphanumeric characters.

SELECT command denied to user 'root'@'10.0.0.115' for table 'user'

There already we have the problem.

Your root@10.0.0.115 don't has enough rights.

You need to do something like this:

GRANT ALL on *.* to root@10.0.0.115 first.

But consider, you need to do this with a root user that already has GRANT OPTIONS.

The user root@10.0.0.115 has no super user rights at all.

Consider, in MySQL root@10.0.0.115 is not the same user then root@localhost or even root@10.0.0.11. These are three different users.

Yes, but then why does GUI Tools work? Also, we had already done GRANT ALL for the user root@*.*, so I'm not sure why it's giving me that error. I tried putting root@10.0.0.11 as the username, but this didn't fix the problem.

root@10.0.0.115 isn't granted not root@10.0.0.11.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".