You have to set a startup parameter when you start mysql so that 4.1.x understands the older password scheme being sent by MyODBC 3.51.09. Add the following to the mysql command:
--old-passwords
Note: you can modify your init scripts, manually stop and restart using the parameter, and I believe you can pass it as an option in your my.conf file. However, I'd rather someone more experienced give you the steps to doing any of these if you don't already know how to do this.
This page explains the 4.1.x server vs. 4.0.x client issue:
http://dev.mysql.com/doc/mysql/en/old-client.html
Here's details on how 4.1.x server creates longer password hashes than 4.0.x server and how to deal with it:
http://dev.mysql.com/doc/mysql/en/password-hashing.html
And here's an excellent discussion from Mike Hillyer's Personal Web Space:
http://www.openwin.org/mike/faq/faq.php/error-client-does-not-support-authentication-protocol-requested/
By the way, Mike is now employed by MySQL, created vbmysql.com, and write docs for MySQL.
Hope that helps.
jbehr wrote:
> Hi Bill,
>
> Thanks for the suggestion.
>
> I tried downgrading (upgrading?!) to 3.51.09, but
> it doesnt seem compatible with the mysql server
> (4.1.10a-nt), as I get this error msg when trying
> to set up an odbc connection:
>
> "Client does not support authentication protocol
> requested by server; consider upgrading mysql
> client"