Navigation
- FAQ Home
- All categories
- About Webyog support and about this FAQ
- About the SQLyog program

- Connection issues
- Using the GUI
- Managing your MySQL Database Systems

- Database Schema Synchronization
- MySQL DATA synchronization
- SQL Scheduler and Reporting Tool
- Importing external data
- Backup/Restore
- SQLyog Job Agent (SJA)

- Working with Views, Stored Procedures and Triggers
- Character Set and Localization Issues
- MySQL bugs that affect SQLyog
- Questions on Open Source and Compiling
- Sitemap
Most popular FAQs 
- I get error 1130 "Host is not allowed to ... (169220 views)
- Error no. 2003: Can't connect... (86215 views)
- SQLyog Version History (63912 views)
- Error no. 1045: "Connection denied..." (61323 views)
- Error no. 1251: "Client does not support authentication..." (58307 views)
- Error No. 2005: Unknown MySQL server host... (50162 views)
- What is HTTP-tunneling? (42269 views)
- What Is SSH and SSH-tunneling? (38047 views)
- Can I use SQLyog with the WINE Windows emulator ... (34915 views)
- Why are Stored Procedures not created when I import ... (34260 views)
Latest FAQs 
- SQLyog Version History (2012-01-26 08:20)
- SQLyog is a client for the MySQL server - ... (2011-11-04 04:48)
- I get error 1130 "Host is not allowed to ... (2011-11-01 05:21)
- Problems on Ubuntu 11.x (2011-10-29 13:02)
- Problems creating a functional DSN on 64 bit Windows. ... (2011-09-15 14:34)
Sticky FAQs
Connection issues » Connection problems
Error no. 1251: "Client does not support authentication..."
Error no. 1251: "Client does not support authentication protocol requested by server - consider upgrading MySQL client" occurs when the hashing-method for storing password used by the client differs from the one of the server. Typically it occurs when trying to connect to MySQL 4.1 or 5.x with a client compiled for 3.x or 4.0.
MySQL explains here:
http://dev.mysql.com/doc/mysql/en/old-client.html
The "client" as far as SQLyog goes is either the sqlyog.exe and sja.exe executable files (with its compiled-in MySQL C-API) or - in case you use HTTP-tunneling - your PHP-binary.
SQLyog itself (the sqlyog.exe -executable) handles all MySQL versions from 3.23.x and upwards automatically, and the error message should not occur with direct connection. In case you experience the error when HTTP-tunneling, you can EITHER replace the PHP-binary OR "downgrade" the hash-type for the user used for tunneling (and other PHP based connections) with the command
SET PASSWORD FOR 'some_user'@'some_host' = OLD_PASSWORD('newpwd');
Note what is here UPPERCASE must be written literally as here.
At ISP's you should expect the Sys Admin there to have MySQL-installations and PHP-binaries that "fit". If you operate your own MySQL server the hashing method may or may not change when upgrading the server from 4.0 to a newer version. That depends on the upgrade method.
Tags: -
Related entries:
- Do I need PHP to use SQLyog with MySQL?
- SQLyog gives you the most options for connecting to MySQL
- Welcome to the SQLyog FAQ
- Installation and upgrading
- Buying and Licensing SQLyog
Last update: 2005-09-28 15:15
Author: Peter Laursen
Revision: 1.0
You can comment this FAQ