CalEvans wrote on Apr 19 2004, 02:01 AM:
Is your server listening on ip addresses other than localhost? (127.0.0.1)
You shouldn't have to do port forwarding, however, if the server is on the Internet then I recommend limiting mysql to localhost and use an ssh tunnel to get to it. Â It's a little more secure.
HTH,
=C=
Cal,
my.cnf is empty, so I presume mySQLis not just listening on the localhost (???)
Should I add this?
bind-address=127.0.0.1, 10.0.0.%
My LAN is subnet 10.0.0.x (i am not sure if I have to use comma-seperation in my.cnf)
The server will be on the internet, so I should set it to localhost only.
But for now I wish I could get SQLyog working whatsoever!!
http://dev.mysql.com/doc/mysql/en/Error-returns.html.
Thanks for that! I dind't know where to look for the return codes, It may help demystifying the problem.
On that page I also found something about Debian specific problems in regards to connecting to mySQL over tcp/3306. It might have to do with this problem as I also got error 2013.
I have to sort this out and do some testing (next week) before blaming SQLyog, hahaha!
I am not a mySQL expert (that is a trivial statement , hihihi)
Piotr
