By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,952 Members | 1,725 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,952 IT Pros & Developers. It's quick & easy.

Connection Failure on Mysql Server 5.1

P: 2

I just migrated a MySQL database from my test server to my production Server with success. This database ia a backend for a .net application Im running. Now the problem is that when I try to connect to the database on the server(new one) I get the following error:
Connection Failed: [HY000] [MySQL][ODBC 5.1 Driver] Can't connect to MySQL server on 'localhost' (10060)

Another strange thing is that from this new production server I can connect to other remote databases(e.g on a different computer on the same network) but those very same computers cannot connect to this production server.

Iv already tried the firewall option, disabling the firewall, allowing the default port 3306 permission etc...
Im really at a loss as to what the problem could be.

Extra information about my problem:
MySQL server version running on the production server: MySQL server 5.1
ODBC Connector Ive installed: MySQL ODBC driver 5.1
Operating System: windows server 2008

Please help!
Jun 16 '11 #1
Share this Question
Share on Google+
2 Replies

Expert 5K+
P: 5,058

Try using the localhost IP, "", instead of "localhost". I remember there being a weird bug in early versions of Windows 7 about that, and if I remember correctly Win Server 2008 is in that same batch of Windows systems.

Also, keep in mind that MySQL doesn't allow remote connections by default. To allow that, you need to edit the MySQL config file. Comment out skip_networking and add bind_address = 192.168.X.Y line.
Jun 17 '11 #2

P: 2
Success at last!

Hi everyone, thanks for the reply Atli, it came a bit late, I had success first thing in the morning.

The problem was with my initial MySQL server config settings I think, trying to explicitly set the defualt port on Windows Firewall while not doing so on the server was the problem. After doing that, not only could I telnet from other machines, but my databases held locally were displayed in the ODBC system DSN configurations!
Now all I have to do is to include this in my documentation...
Jun 17 '11 #3

Post your reply

Sign in to post your reply or Sign up for a free account.