I connected easily to my MSSQL DBs, but they were both set up with named pipes.
This is the error given by HeidiSQL:
/* Connecting to 192.168.xx.xx via MySQL (SSH tunnel), username root, using password: Yes ... */
/* Attempt to create plink.exe process, waiting 4s for response ... */
/* SQL Error (2003): Can't connect to MySQL server on 'localhost' (10061) */
/* Closing plink.exe process #2336 ... */
So, How do I debug this? Does error 2003 indicate that MySQL is set to not accept outside connections? Or, that the password is wrong? Or, is the port wrong?
The DB does exist. Another developer built it and connects to it via command line.
Any help appreciated.
newbe question: connecting to remote MySQL via SSH
MySQL bundles a command-line utility called perror that is very handy to find a description of error messages:
In this case, the second error code looks quite relevant: it isn't a MySQL error code, it's a Windows API code that roughly translates as "Could not establish a connenction because target machine expressly rejected the connection".
Have you installed a SSH tunnel?
C:\>perror 2003
Win32 error code 2003: La operación de metarchivo solicitada no es compatible.
C:\>perror 10061
Win32 error code 10061: No se puede establecer una conexión ya que el equipo de destino denegó expresamente dicha conexión.
In this case, the second error code looks quite relevant: it isn't a MySQL error code, it's a Windows API code that roughly translates as "Could not establish a connenction because target machine expressly rejected the connection".
Have you installed a SSH tunnel?
Please login to leave a reply, or register at first.