Bug #5726 ODBC could not connect

Submitted: 24 Sep 2004 4:45 Modified: 25 Oct 2004 22:01
Reporter: Nai Chin Email Updates:
Status: Not a Bug Impact on me:
None 
Category:Connector / ODBC Severity:S1 (Critical)
Version:3.51.9 OS:Windows (WindowsXP)
Assigned to: CPU Architecture:Any

[24 Sep 2004 4:45] Nai Chin
Description:
We use MSAccess as front end assessing backend MySQL server.  We have 4.0.21 server installed and are currently testing the 4.1.5-gamma.

With the current version of MyODBC 3.51.9, we could not connect to the new server.  The following error message was noted.

ODBC--call failed.
[MySQL][ODBC 3.51 Driver]Client does not support authentication protocol requested by server; consider upgradeing MYSQL client(#1251)

How to repeat:
We attempted connecting to the new server via the ODBC with no success.

Suggested fix:
No idea.
[8 Oct 2004 9:08] Lynn Prentice
Same problem on windows 2000 server, fully patched.
MySQL 4.1.5
ODBC/Connect 3.51.7 and 3.51.9
tried without success
#Use old password encryption method (needed for 4.0 and older clients).
old-passwords
Tested in the ODBC Data Source Administrator, using the Test button. It also did the same thing using ADO
Connects fine in MySQLAdministrator 1.0.1a alpha
Basically a pain in the arse - reverting back to 4.1.4 where it does work
[25 Oct 2004 22:01] MySQL Verification Team
Hi,

Thank you for the report, but this is not a bug.
Please, read carefully the following section of the manual:
http://dev.mysql.com/doc/mysql/en/Old_client.html
[3 Dec 2007 19:46] arun kumar
Try following solution

http://javasolution.blogspot.com/2007/04/mysql-couldnt-find-mysql-server-or.html

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.051 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.