The manual's often a friend, but not always, a case in point being the suggestion on that manual page to "Upgrade all client programs to use a 4.1.1 or newer client library"--you will correct me if I am mistaken on this, I hope, that one's only option now using ODBC and MySQL 4.1 or later is to revert to the old password protocol and thus create problems of the sort ODBC was meant to solve.
PB ----- Original Message ----- From: [EMAIL PROTECTED] To: Danesh Daroui Cc: [EMAIL PROTECTED] Sent: Thursday, September 09, 2004 9:01 AM Subject: Re: ODBC problem Even the most recent version of the ODBC drivers act as though they are pre-4.1 clients. Now that you know that, what you read in this article should make better sense: http://dev.mysql.com/doc/mysql/en/Old_client.html It contains links to other details on the issue and some suggestions to work around your problem. Let's all say it together: "The manual is your friend" ;-D Shawn Green Database Administrator Unimin Corporation - Spruce Pine "Danesh Daroui" <[EMAIL PROTECTED]> wrote on 09/08/2004 07:59:04 PM: > Hi all, > > I have a Linux Database Server which runs MySQL 4.1 and a Windows > Client machine which runs MySQL 4.1 too. I have installed the latest > version of MyODBC on both machines and they have been installed > successfully. Now, at the Administrative Tools in the Control Panel > on my Windows system (Client) when I try to connect to my Linux > system by using a valid user it doesn't connect and returns an error > message which is: > > [MySQL][ODBC 3.51 Driver] Client does not supportauthentication > protocol requested by server; consider upgrade MySQL client. > > What is the problem ? What should I do now ? I am totaly confuse, > please help... > > Regards, > > Danesh Daroui >
