You could also leave the password blank if you don't
want to force MySQL to revert to the old password
encryption on start-up. This should be fine if your
server is in the DMZ and you control all the processes
that have access to the server.
Unfortunately, 4.2.x breaks backward compatibility
with ODBC and many other old clients, including major
open source PHP projects.
--- Mechain Marc <Marc.Mechain@stripped> wrote:
>
> Have a look at:
>
> http://dev.mysql.com/doc/mysql/en/Old_client.html
>
> Marc.
>
> -----Message d'origine-----
> De : nikos [mailto:nikos@stripped]
> Envoy> > Objet : MyODBC 3.5.9 and MySQL 4.1.8
>
>
>
> Hello list and happy new year.
>
> Recently I've install mysql 4.1 on win 2000 with IIS
> 5 and works
> perfect. My problem is that when i'm trying to make
> a connection with
> myodbc (latest release) as localhost I got the
> following message:
> "Client does not support authentication protocol
> requestet by server.
> Consider upgrading mysql client".
>
> MyODBC whorks fine because I 've allready make
> connection throw lan on a
> Linux RH-9 with apache and mysql 4.0.22
>
> Any suggestions?
> Thanky you
>
>
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe:
>
http://lists.mysql.com/mysql?unsub=1
>
>
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe:
>
http://lists.mysql.com/mysql?unsub=1
>
>
__________________________________
Do you Yahoo!?
The all-new My Yahoo! - Get yours free!
http://my.yahoo.com
