MySQL Forums
Forum List  »  Install & Repo

Re: "mysql_connect(): Client does not support authentication protocol requested by server; consider upgrading MySQL client"
Posted by: khalid jack
Date: October 14, 2006 12:18AM

Hello to all.. I must say that this problem is so hard to solve because it's not expected at all. Morever, it shows that people who use MySQL are too smart to discover such goofs although it is a math or logic type of problem. If anyone encounters this problem, the following will solve it immediately.
1> Log in using the console and set the password for the user that you are using to connect to the server from php (or any other client) to blanks.
In MySQL/bin type mysql -u<user> -p<password> and at the mysql prompt, type : set password = '';
2> Add this line to the [mysqld] secton of your my.ini which is located in the same folder as MySQL:
old_passwords=1
3> Go back now and set the password to the user using the console again.

You are now able to connect! This is like locking the keys inside your car, but too overwhelmed to realize it.

for those who wnat to know more about this problem, read on.
The first time the wizard is creating the credentials (user and password), it is using the new authentication scheme which is not compatible with older clients. Thus, you will not be able to connect with old clients. Fortunately, MySQL is able to roll back to the old authentication scheme (for FUTURE passwords) by putting the line old_password=1 in the my.ini file. So, when a new user is created, the old clients will be able to connect.

Options: ReplyQuote


Subject
Written By
Posted
December 31, 2005 12:02AM
December 31, 2005 02:28AM
March 29, 2006 03:12AM
March 24, 2007 02:58PM
January 03, 2006 07:48AM
March 16, 2006 10:03AM
November 02, 2005 07:38AM
January 16, 2006 03:46PM
July 24, 2006 07:40AM
March 28, 2006 11:18PM
August 23, 2006 01:21PM
Re: "mysql_connect(): Client does not support authentication protocol requested by server; consider upgrading MySQL client"
October 14, 2006 12:18AM


Sorry, you can't reply to this topic. It has been closed.

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.