Unsupported Screen Size: The viewport size is too small for the theme to render properly.

Error 2003

forums forums SQLyog Using SQLyog Error 2003

  • This topic is empty.
Viewing 4 reply threads
  • Author
    Posts
    • #10418
      kbutler
      Member

      error2003.jpg

      The MySQL server is running locally and I can connect to it outside of sqlyog. MySQL is listening on 3306. I am using community edition. I'm somewhat new to all of this – any assistance would be helpful.

    • #24402
      peterlaursen
      Participant

      “is running locally …”

      do you mean on LOCAL MACHINE or LOCAL NETWORK ?

      “I can connect to it outside of sqlyog ..”

      How? With what client can you connect?  If you are connecting from the same host are you sure that the details are identical?

      This FAQ:

      http://webyog.com/faq/23_15_en.html

      .. deals with the error 2003!

      (note: this is a connection issue, not an authentication issue)

    • #24403
      kbutler
      Member
      peterlaursen wrote on Jun 27 2007, 11:22 AM:
      “is running locally …”

      do you mean on LOCAL MACHINE or LOCAL NETWORK ?

      “I can connect to it outside of sqlyog ..”

      How? With what client can you connect? If you are connecting from the same host are you sure that the details are identical?

      This FAQ:

      http://webyog.com/faq/23_15_en.html

      .. deals with the error 2003!

      (note: this is a connection issue, not an authentication issue)

      Local network, my apologies.

      I can connect to it via Putty – an SSH client.

      Quote:
      * There is no MySQL server running at the specified host

      There is…

      Quote:
      * Connection to the MySQL server is not allowed using TCP-IP. Check the 'skip-networking' setting in the MySQL configuration file (my.ini on Windows, my.cnf on Unix/Linux). It shall be commented out like '#skip-networking'. If it is not commented out, then do it and restart the MySQL server for the change to take effect. SQLyog needs to connect using TCP-IP.

      skip-networking is not even present in the my.cnf:

      Code:
      #
      # Instead of skip-networking the default is now to listen only on
      # localhost which is more compatible and is not less secure.
      bind-address = 127.0.0.1

      I am thinking that it may have something to do with this – that mysql is only listening to localhost – while I am trying to connect directly.

      Quote:
      * Some networking issue prevents connection. It could be a network malconfiguration or a firewall issue. We have experienced sometimes that some firewalls (ZoneAlarm in particular) is blocking TCP-IP connections even if it claims to be disabled. Most often it will help to uninstall and reinstall the firewall.

      The LAN is behind a firewall – I don't have any local firewalls.

      Quote:
      * When trying to connect to a MySQL server at an ISP this error message often indicates that direct connection to MySQL has been blocked. You must then use HTTP-tunnelling or SSH-tunnelling to connect.

      LAN – this is not valid in my case.

      Quote:
      * Also this FAQ may have relevant information. It describes some more special situations when connection to MySQL on Linux.

      Feel a bit lost in this post – as I said – I am somewhat new to configuring this sort of thing.

    • #24404
      kbutler
      Member

      As a follow-up to possible future visitors – it was the bind-address. I commented this out and it works great now!

    • #24405
      peterlaursen
      Participant

      Ok .. you solved this.

      i only have a single comment on Putty and SQLyog.

      When you use Putty you connect to the 'mysql' client program on the server.  This client next connects to the server.  So connection to the MySQL server is form the same computer as where the server runs.

      With SQLyog the client is SQLyog (the client code – teh mySQL C-API – is compiled into SQLyog.  SQLyog does not use the 'mysql' client on the server. So here you connect from a remote machine!

Viewing 4 reply threads
  • You must be logged in to reply to this topic.