ado connection string error through vb

[TLowder]

I'm using mysql-5.0.1-alpha-snapshot-win & VB 6.0

I'm having trouble connecting to the database server over a lan.

When I use the following connection string from the server it works fine. -

adoCon.ConnectionString = "Driver={MySQL ODBC 3.51 Driver};SERVER=localhost;DATABASE=MyDatabase;uid=root;"

When I use the the following connection string from another computer I get this error -

adoCon.ConnectionString = "Driver={MySQL ODBC 3.51 Driver};SERVER=192.168.0.2;DATABASE=MyDatabase;uid=Tom;pwd=X12;"

Run-time error '-2147467259(80004005)'

[MySQL][ODBC 3.51 Driver]Can't connect to MySQL server on '192.168.0.2' (10060)

Also when I try the last connection from the database server and in vb (not compiled) I get the following error -

Run-time error '-2147467259(80004005)'

[MySQL][ODBC 3.51 Driver]Client does not support authentication protocol requested by server; consider upgrading MySQL client

In MySQL CC under users -
Username = Tom
Host = %
Password=X12

Global privileges and MyDatabase are checked with All Privileges

Thanks,
Tom

 

[ericbrunson]

Your client doesn't understand the post 4.1 encryption. In mysql do

UPDATE mysql.user SET Password = OLD_PASSWORD('newpwd')
where user = 'Tom' and host = '%';

If you'd googled for the error message you would have found that answer in the mysql manual.

 

[TLowder]

Thank you for the response-

The first error was caused by my xp firewall on the server. I allowed an exception to c:\mysql\bin\mysqld-nt.exe then it worked fine.

Your right about the second error. I did a search and found the manual after I posted the question. It was helpful and what led to me fixing the first error. At first I didn't think it was the password encription due to my version (mysql-5.0.1-alpha-snapshot-win). But it fixed it.

I also did more reading and now I'm unsure if I should be using this version. Anyone have an opinion on which version one should use?

Thank you,
Tom

 

[ericbrunson]

If you're doing new development that doesn't need to be rock-stable for several months I'd say go ahead and use 5.

If you're doing production code, but need the new features of 4.1, use it.

If you require rock solid stability, I would suggest 4.0.

I personally use 4.1 in a production environment and have not had any problems. Your milage may vary.