Hi Jim,
On 10/31/2018 7:12 PM, Halaasz Saandor wrote:
2018/10/31 15:15 ... Jim:
Given the following bug report, what I am trying to do does not sound
hopeful:
https://bugs.mysql.com/bug.php?id=90994
...
Any thoughts or do I need to accept that what I'm attempting just
isn't going to work?
2018/10/31 15:15 ... Jim:
Given the following bug report, what I am trying to do does not sound
hopeful:
https://bugs.mysql.com/bug.php?id=90994
...
Any thoughts or do I need to accept that what I'm attempting just isn't
going to work?
From the same bug report, id=90994:
[24 Oct 20:17] B
llows.
As run from the mysql8.0 server:
$ mysql -h db5.1server.mydomain.com -u my_user -p
Enter password:
ERROR 1043 (08S01): Bad handshake
Given the following bug report, what I am trying to do does not sound
hopeful:
https://bugs.mysql.com/bug.php?id=90994
I'm in the middle of a transiti
I'm using MySQL 4.1.7 Production binary version and try to connect it
from mysql 4.1.0 client.
I get "ERROR 1043: Bad handshake" error on the console.
I don't have problem in connecting using same version of mysql client
(MySQL 4.1.7)
Is there a way to fix it, please help m
Hi all,
I'm using MySQL 4.1.7 Production binary version and try to connect it
from mysql 4.1.0 client.
I get "ERROR 1043: Bad handshake" error on the console.
I don't have problem in connecting using same version of mysql client
(MySQL 4.1.7)
Is there a way to fix it,
sing MySQL Administrator, I get the following error:
Could not connect to host 'hostname'.
MySQL Error Nr. 1043
Bad handshake
I have UPDATED the database password as suggested using the OLD_PASSWORD()
function. Still not able to establish a connection.
Any suggestions?
Thanks for your time
I get:
> bash-2.05$ mysql landfill -u root -p -h 192.168.1.100
> Enter password:
> ERROR 1043: Bad handshake
> bash-2.05$
>
> Any idea what I am doing wrong?
>
> --ja
--
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is
27;t
> > that just for migrated data?) I can connect to it via local host just fine
> > but if I try to connect from another machine running 4.1.? I get:
> > bash-2.05$ mysql landfill -u root -p -h 192.168.1.100
> > Enter password:
> > ERROR 1043: Bad handshake
&
st for migrated data?) I can connect to it via local host just fine but if
> I try to connect from another machine running 4.1.? I get:
> bash-2.05$ mysql landfill -u root -p -h 192.168.1.100
> Enter password:
> ERROR 1043: Bad handshake
> bash-2.05$
>
> Any idea what
't that just
for migrated data?) I can connect to it via local host just fine but if I try
to connect from another machine running 4.1.? I get:
bash-2.05$ mysql landfill -u root -p -h 192.168.1.100
Enter password:
ERROR 1043: Bad handshake
bash-2.05$
Any idea what I am doing wrong?
-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday 06 February 2004 11:45, Harrison Fisk wrote:
> The issue is that 4.1.0 used a different authentication handshake with a
> different form of password encoding. Due to the fact that 4.1.0 was
> alpha, it was decided not to support the authenti
line (-p without a password), mysql returns a "Bad
> handshake" error message.
>
> I'm trying to connect on the machine running mysql
> The server version is 4.1.1-1
> The client software is 4.1.0-0 (which is, I believe, the latest for download)
> The user is not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I still have the problem with being unable to logon to a database with a
password. When the password is entered - either on the command line (-p???)
or on the following line (-p without a password), mysql returns a "Bad
handshake" err
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday 05 February 2004 16:52, [EMAIL PROTECTED] wrote:
> What version is the MySQL client? Is the user logging on remotely?
4.1.0-0 on the client.
The user is logging on on the machine running MySQL. I'll check out remote
login after I have it
What version is the MySQL client? Is the user logging on remotely?
>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<
On 2/5/04, 4:22:37 PM, Michael Satterwhite <[EMAIL PROTEC
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday 05 February 2004 14:31, [EMAIL PROTECTED] wrote:
> What about if the user enters
> mysql -u -p
MySQL fails to start with the error message "Bad Handshake"
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.2-rc1
What about if the user enters
mysql -u -p
>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<
On 2/5/04, 2:22:29 PM, Michael Satterwhite <[EMAIL PROTECTED]> wrote
regarding Re
unning MySQL and enters the command
mysql -p
MySQL queries the password, then issues the "Bad handshake" error.
If there is no password associated with the user, the connection is fine.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.2-rc1
Was the user created under MySQL 4.1 or a previous version? How are you
connecting? MySQL monitor, ODBC, JDBC, etc. ?
>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<
On 2/5/04, 1
e user, he receives the message "Bad handshake" when
he enters the password.
Can anyone tell me what this means and how to fix it?
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux)
iD8DBQFAIpwkjeziQOokQnARAr77AJ4ymdzq/nAigVnzGzRCmrrzCxw7+ACffrJg
P8CJLgWYX4sLwioX+2A
Hi
i need to access a MySQL Server via socket programming to check if it is alive.
My script works fine but the mysql server blocks the host that is running the script
after 10 connects because I get the bad handshake error.
Is there any way to connect and cleanly disconnect to port 3306
Hi
I am using resin-1.2.3 and mysql at backend on windows 2000...I am trying to connect
to mysql thru my JSP's but gotta bad handshake...I am using mysql-jdbc driver...
My JSP code is like this..
%@ page language="java" import=" java.sql.*, java.util.*" %>
Serveur d'application JBossI got a problem with my connection to a Mysql Database. (
am
programming with JSP, using a JDBC driver...)
The problem is that I got an Error 500 when I am trying to
connect to my database ... Actually, There is a "Bad Handshake"
error ...
I don&#x
23 matches
Mail list logo
