Bug #2626 | Bad Handshake returned when trying to connect to 4.1.1 using Navicat | ||
---|---|---|---|
Submitted: | 3 Feb 2004 7:08 | Modified: | 9 Feb 2004 7:48 |
Reporter: | Scott Hansen | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server | Severity: | S3 (Non-critical) |
Version: | 4.1.1 | OS: | Windows (Windows 2000) |
Assigned to: | CPU Architecture: | Any |
[3 Feb 2004 7:08]
Scott Hansen
[8 Feb 2004 12:13]
MySQL Verification Team
Please verify if you are getting the below message starting the server with --standalone --console at the command prompt: 040208 18:07:49 mysql.user table is not updated to new password format; Disabling new password usage until mysql_fix_privilege_tables is run d:\arquivos de programas\4.1.1a\bin\mysqld-nt: ready for connections. if yes try to update the grant tables for 4.1.1 format.
[9 Feb 2004 7:28]
MySQL Verification Team
Now I was able for to download the trial version of Navicat and to test the behavior reported. That message error happens due to version of libmysql.dll which is installed on system32 directory. Please change that library by the one shipped by 4.1.1a and you will have the issue resolved like I did. Thanks.
[9 Feb 2004 7:48]
Sergei Golubchik
The reason is that the new protocol that was added in 4.1.0 contained a flaw, so a release 4.1.1 employs a new client-server protocol which is not compatible with 4.1.0 (it is ok, as 4.1.0 is alpha, and not recommended for production use, and we don't want to encourage the usage of a flawed protocol). Of course both 4.1.0 and 4.1.1 support older 4.0 protocol, but the new protocol of 4.1.0 is not supported in 4.1.1. Navicat 5.3.12 is built with libmysql.dll as of MySQL-4.1.0. Thus you need to upgrade mysql client library. You may also report a bug to PremiumSoft, so that new Navicat release won't be based on an unsopported mysql client library.