MySQL Forums
Forum List  »  Install & Repo

Re: SOLUTION: "mysql_connect(): Client does not support authentication protocol requested by server; consider upgrading MySQL client"
Posted by: flamtriplets_2000
Date: February 12, 2005 12:56PM

Thanks for the response, mglatts.

I was using a previous version of mySQL, which didn't allow me to make any root admin database changes (priviliges, create databases etc). I upgraded and ran into problems configuring the MySQL instance and security settings (resolved after deleting the previous service fromt the command line). Then I had the #1045 error message connecting to MySQL from PHP/Apache or JSP/Tomcat. However, I found this on another message board, and it worked right away for me (I changed the default phpMyAdmin user to root also, for more privileges and a nice GUI)


1. Login as root to mysql at the command prompt (in windows XP sp2 select from menu start->programs->mysql->mysql command line)

2. create new account for example ‘zoooz:
mysql> GRANT ALL PRIVILEGES ON *.* TO root@localhost;

3. set password in old format:
mysql> SET PASSWORD FOR root@localhost = OLD_PASSWORD('mypass');

if you are running postnuke on local machine use ‘localhost’ as host name
And that’s all.

The reason you get the error message is that MySQL 4.1 uses an authentication protocal based on a new password hashing algorithm that is not apparently supportet by php (or apache?). Command old_password assigns password with old algorithm

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
Re: SOLUTION: "mysql_connect(): Client does not support authentication protocol requested by server; consider upgrading MySQL client"
February 12, 2005 12:56PM
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


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.