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

Help About Sja & Named Pipe …

forums forums SQLyog Sync tools, Migration, Scheduled Backup and Notifications Help About Sja & Named Pipe …

  • This topic is empty.
Viewing 1 reply thread
  • Author
    Posts
    • #22189
      peterlaursen
      Participant

      SQLyog and SJA only connects to MySQL using TCP-IP and neither 'named pipes' (on Windows) or 'socket' (on *nix)

      You have some other software using a 'named pipe' on port 3301. However that should not prevent you from using TCP-IP too on (typically) port 3306.

      Is the Server configured not to used TCP-IP? Any particular reason for that? You can cooment-out 'disable-networking' in MySQL cofiguration then (you will need to retart the server).

      BTW: I think that it is well known that 'named pipes' on Windows are less efficient that TCP. On some *nix systems 'socket' is most efficient.

    • #22190
      MuphoOx
      Member

      thx for your answer, Peter;

      i was writing an update of this situation …

      actually, i've changed the parameters; i've commented-out 'disable-networking' in MySQL and used a tcp port, and have put a 'bind-address=127.0.0.1' clause to keep my server secure.

      I was using the “named pipe” 'cause our clients when they have a firewall, it block the communication port of mysql, so no more connexion to the data base is possible; then the software is not working… and the client complain … 😡 . The named pipe was used cause it doesn't use any communication port …

      Anyway, with the bind-address, the sync job works well; but i have to find a solution to avoid the firewall… or to add a rule on every well knwon firewall…. but it's an other task…

Viewing 1 reply thread
  • You must be logged in to reply to this topic.