[RESOLVED] Database Connection Error

maco

I have this problem again when I installed to windows 2000 using MYSQL 4.1 and PHP 4.3.1

'Client does not support authentication protocol requested by server; consider upgrading MySQL client'

I have the same problem with this when I installed under Windows XP. The solution for this is to run the following command under SQL environment.

SET PASSWORD FOR user@localhost = OLD_PASSWORD('password');

But when I do this command under Windows 2000, it does not work ? the sql message says 'Query OK, 0 rows affected'

Been trying the solution all over and over again to no avail . . . .

Can someone help me on this please.

Thanks

Roger_Ramjet

Should be posted in the Install forum really. I say this because the people cruising in that forum are more likely to know the answer.

The integrated NT security in W2K was cut to pieces when they made XP - one reason why we are never likely to use it on our LAN. That will be why the XP solution does not work in W2K, XP has no security worth mentioning.
In w2k, the NTFS file system security settings will affect your access to the physical database files. Your php script will be seen as an anonymous user by ntfs and so you need to change the security settings to allow the connection for db authentication to begin.

maco

Anyone knows how to set the setting of my windows 2000 ?

gardnc

Mysql 4.1 changed the method used to validate passwords and is not compatible with PHP 4. There are work arounds.

http://dev.mysql.com/doc/refman/5.0/en/old-client.html :

Note: In older versions of PHP, the mysql extension does not support the authentication protocol in MySQL 4.1.1 and higher. This is true regardless of the PHP version being used. If you wish to use the mysql extension with MySQL 4.1 or newer, you may need to follow one of the options discussed above for configuring MySQL to work with old clients.

Larry

maco

Larry and Roger Ramjet thanks for replying my query . . .

It worked now, although the sql statement message says 'Query OK, 0 rows affected' it actually updated. I thought initially it did not update any record as the message says 0 rows affected.

Thanks . . .