If you are using an ODBC driver or some other pre-4.1 library to connect to a post-4.1 MySQL server you can get the message you describe.
Here is some reading about cross-version authentication issues: http://dev.mysql.com/doc/mysql/en/Problems.html (esp section A.2) http://dev.mysql.com/doc/mysql/en/Access_denied.html http://dev.mysql.com/doc/mysql/en/Application_password_use.html http://dev.mysql.com/doc/mysql/en/Password_hashing.html What it boils down to is that your pre-4.1 client is trying to validate a much longer password hash from the server against a locally created hash built from the password you are using to login with. Solve this by doing any one of these three things: 1) force your post-4.1 server to always use the old-style hashes (less secure) 2) update certain records in the mysql.user table using the OLD_PASSWORD() function (preferred) 3) upgrade your client (not always possible) The reading describes how to do all of those suggestions. Shawn Green Database Administrator Unimin Corporation - Spruce Pine Claire Lee <[EMAIL PROTECTED]> wrote on 10/05/2004 11:27:43 AM: > Hi, > I have a perl script that connect to mysql using the > following: > > my $dbh = > DBI->connect("DBI:mysql:$dbname;host=$host","$dblogin", > "$dbpasswd") or die "Cannot connect to $dbname: " . > $DBI::errstr; > > But after I upgraded to 4.1.5 I get the following > error message: > DBI->connect(dbname;host=host) failed: Client does not > support authentication protocol requested by server; > consider upgrading MySQL client > > What shall I do? Please help. Thanks. > > Claire > > > > __________________________________ > Do you Yahoo!? > Yahoo! Mail is new and improved - Check it out! > http://promotions.yahoo.com/new_mail > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] >
