Michael, note here that it's been years since I used MySQL, but I think
I remember MySQL authentication being "host" based. That's not the
right term, but connecting locally with mysql user "user1" is *NOT* the
same as connecting remotely to the same server with mysql user "user1".
There is a way to specify on the server that you want to allow remote
connections as "user1" - as I remember it is very flexible in the way
that it allows you to specify a specific IP address to allow from, or a
portion (subnet) of an IP address, etc.
Sorry I can't be more help. Without my "MySQL" book by Paul Dubois I
can't get any more specific. If you don't have a book, go to the MySQL
website and read up authentication.
HTH.
Hardy Merrill
>>> "Michael David" <[EMAIL PROTECTED]> 12/02/04 12:06AM
>>>
Hello,
I have a script that is connecting to two different databases , one is
local
and the other remote.
The local Informix DBI connection works a treat but I am having trouble
getting the remote mysql connection to work.
I keep get error: Client does not support authentication protocol
requested
by server.
I have checked and upgraded, and now both local and remote machines are
running mysql 4.1, and the same client.
I have also checked and the mysql port is open on the remote server.
All the search results I could find regarding this error said to
upgrade the
the mysql server, which I have done and now
there should be no protocol barriers since they are running the same
version.....
Does anyone have any ideas what may be causing this error other than
different versions of the server. Or probably even better, some
instructions
on how to really "turn up" or "tweak" my dbh debugging so that I can
get
more details on the failed connection attempt.
this is my connection statement:
my $db2 = "dbname";
my $dbhMysql = DBI->connect("DBI:mysql:$db2:xxx.xxx.xxx.xxx", 'uname',
'pword') || die print "Could not connect to database($db2): $!\n";
this being the same as my local connection (minus the host IP address)
which
does work.
Thanks,
mike
