MySQL Error 10060

[Database Administrator]

I am running MySQL 4.1.12a on a Win2k Server machine.

I keep getting the 10060 error when trying to remotely log in with a user
'nick' I have set up. I can log in locally on this machine using both
'root' and 'nick'.

This server is located on another network behind a firewall. Access to port
3306 has been granted and upon checking the firewall logs, the packets are
being allowed through. I have also installed port monitor and packet
sniffing software on the server and it shows port 3306 as listening and
whilst trying to connect I can see that the packets are coming in on port
3306 from my source IP on the packet sniff.

If I try and use the mysql -u nick -h xxx.xxx.xxx.xxx -p command on my
machine then I get asked for the password, then about 20 seconds later it
says: ERROR 2003 (HY000): Can't connect to MySQL server on 'xxx.xxx.xxx.xxx'
(10060).

I've tried Telnet xxx.xxx.xxx.xxx 3306 and it just fails saying: Connecting
To xxx.xxx.xxx.xxx...Could not open a connection to host on port 3306 :
Connect failed

I have checked the mysql.user table and the host,user entries are %,nick and
localhost,root, so I should be able to login from any IP for the user 'nick'
but only that machine for root. I checked skip-networking is not in my.ini.

Is there anything I'm missing, it looks like the connection is definitely
being made to the MySQL server on the port, but MySQL is just ignoring any
requests from the outside world. It's driving me bananas.

[Database Administrator]

Mack wrote:
> I am running MySQL 4.1.12a on a Win2k Server machine.
>
> I keep getting the 10060 error when trying to remotely log in with a user
> 'nick' I have set up. I can log in locally on this machine using both
> 'root' and 'nick'.
>
> This server is located on another network behind a firewall. Access to port
> 3306 has been granted and upon checking the firewall logs, the packets are
> being allowed through. I have also installed port monitor and packet
> sniffing software on the server and it shows port 3306 as listening and
> whilst trying to connect I can see that the packets are coming in on port
> 3306 from my source IP on the packet sniff.
>
> If I try and use the mysql -u nick -h xxx.xxx.xxx.xxx -p command on my
> machine then I get asked for the password, then about 20 seconds later it
> says: ERROR 2003 (HY000): Can't connect to MySQL server on 'xxx.xxx.xxx.xxx'
> (10060).
>

is MySQL listening on 3306 at all? Und Unix, you'd use "netstat -an |
grep 3306" to check, I don't know how to do it on Windows.

You might want to make sure that the MySQL server runs *without* the
"skip-networkin" option.

> I've tried Telnet xxx.xxx.xxx.xxx 3306 and it just fails saying: Connecting
> To xxx.xxx.xxx.xxx...Could not open a connection to host on port 3306 :
> Connect failed
>

Which seems to indicate that there's nobody listening ...

> I have checked the mysql.user table and the host,user entries are %,nick and
> localhost,root, so I should be able to login from any IP for the user 'nick'
> but only that machine for root. I checked skip-networking is not in my.ini.
>

Forget about mysql.user, mysql.host etc. These are implementation
details that could change from one version to the next. Use SHOW
GRANTS instead.

skip-networking might not be in your my.ini, but it could be in the
script starting the server. Or in another my.ini that's read as well.

> Is there anything I'm missing, it looks like the connection is definitely
> being made to the MySQL server on the port, but MySQL is just ignoring any
> requests from the outside world. It's driving me bananas.
>
The error message and the rest of the description indicate that MySQL
is *not* Listening on port 3306. If I do a telnet here, it looks like
that:

ck@stargate:~> telnet held 3306
Trying 192.168.43.1...
Connected to held.
Escape character is '^]'.
9
4.1.10a-logm+->0rrf,*<.piBK3ZMQ2Connection closed by foreign host.

You can clearly see the version of the MySQL server. Since your telnet
attempt doesn't work ...

[Database Administrator]

"Christian Kirsch" wrote in message
news:dikvmj$u3j$1@news.mind.de...
> is MySQL listening on 3306 at all? Und Unix, you'd use "netstat -an |
> grep 3306" to check, I don't know how to do it on Windows.
>
> You might want to make sure that the MySQL server runs *without* the
> "skip-networkin" option.
>
> skip-networking might not be in your my.ini, but it could be in the
> script starting the server. Or in another my.ini that's read as well.

I can confirm that My SQL is definitely listening on 3306, the results of a
netstat -a prove this. Also I can log into the MySQL server on the actual
server, the problem is getting in remotely.

The MySQL is started as a system service in W2K is there a way to check in
MySQL whether it is running with the skip-networking option in case it's in
the command line or another ini file?

[pvnoronha]

any solution for this situation? I have the same issue here.
thanks,
PV