Is firewall preventing MySQL access?

[Kevin Killion]

I've recently features to a system by making use of some simple MySQL
access routines. It works fine at most test locations, correctkly
accessing a MySQL database on an internet server.

However, at certain test sites, I cannot access the database. We're
online, and I can access web files, for example. But when trying to say
hello to that MySQL database, the program fails at the
"mysql_real_connect" call. The message is "Can't connect to MySQL
server", with code "10060" and error "2003". The port is 3306, which is
the default for MySQL access.

(The problem does not seem unique to MySQL: we're having the same
problem with PostgreSQL.)

I've been told by an IT guy at one of these test sites, a very large
corporation, that their company firewall is probably what is keeping the
system from accessing that remore database. Sounds plausible, but I
haven't found much while web searching that explicitly confirms that.
More to the point, I don't have ANY clues or ideas from anywhere on how
to resolve this problem at client sites that seem to prohibit MySQL
access of a remore database.

Suggestions?

Confirmation that it's a firewall problem?

Ideas?

Encouragement?

*** THANKS! ***

Kevin Killion

[Steven Musumeche]

That does sound like a firewall problem. The easiest solution is to
have them open port 3306 on the firewall.

-Steven

Post by Kevin Killion
I've recently features to a system by making use of some simple MySQL
access routines. It works fine at most test locations, correctkly
accessing a MySQL database on an internet server.
However, at certain test sites, I cannot access the database. We're
online, and I can access web files, for example. But when trying to say
hello to that MySQL database, the program fails at the
"mysql_real_connect" call. The message is "Can't connect to MySQL
server", with code "10060" and error "2003". The port is 3306, which is
the default for MySQL access.
(The problem does not seem unique to MySQL: we're having the same
problem with PostgreSQL.)
I've been told by an IT guy at one of these test sites, a very large
corporation, that their company firewall is probably what is keeping the
system from accessing that remore database. Sounds plausible, but I
haven't found much while web searching that explicitly confirms that.
More to the point, I don't have ANY clues or ideas from anywhere on how
to resolve this problem at client sites that seem to prohibit MySQL
access of a remore database.
Suggestions?
Confirmation that it's a firewall problem?
Ideas?
Encouragement?
*** THANKS! ***
Kevin Killion

[Bill F]

"telnet MySQLServer 3306" for me returned
----
On Wed, 06 Sep 2006 09Connected to MySQLServer.
Escape character is '^]'.
0
3.23.41-Max-logg1YPc$%.V
----
The characters after log were random & 3.23.41 is my version I think.
From Galeon on Debian Linux it return a random character .exe file.

If you can't connect with either of these ways you are being blocked
somewhere.

That does sound like a firewall problem. The easiest solution is to have
them open port 3306 on the firewall.
-Steven

Post by Kevin Killion
I've recently features to a system by making use of some simple MySQL
access routines. It works fine at most test locations, correctkly
accessing a MySQL database on an internet server.
However, at certain test sites, I cannot access the database. We're
online, and I can access web files, for example. But when trying to say
hello to that MySQL database, the program fails at the
"mysql_real_connect" call. The message is "Can't connect to MySQL
server", with code "10060" and error "2003". The port is 3306, which is
the default for MySQL access.
(The problem does not seem unique to MySQL: we're having the same
problem with PostgreSQL.)
I've been told by an IT guy at one of these test sites, a very large
corporation, that their company firewall is probably what is keeping the
system from accessing that remore database. Sounds plausible, but I
haven't found much while web searching that explicitly confirms that.
More to the point, I don't have ANY clues or ideas from anywhere on how
to resolve this problem at client sites that seem to prohibit MySQL
access of a remore database.
Suggestions?
Confirmation that it's a firewall problem?
Ideas?
Encouragement?
*** THANKS! ***
Kevin Killion

[Michael Austin]

Post by Kevin Killion
I've recently features to a system by making use of some simple MySQL
access routines. It works fine at most test locations, correctkly
accessing a MySQL database on an internet server.
However, at certain test sites, I cannot access the database. We're
online, and I can access web files, for example. But when trying to say
hello to that MySQL database, the program fails at the
"mysql_real_connect" call. The message is "Can't connect to MySQL
server", with code "10060" and error "2003". The port is 3306, which is
the default for MySQL access.
(The problem does not seem unique to MySQL: we're having the same
problem with PostgreSQL.)
I've been told by an IT guy at one of these test sites, a very large
corporation, that their company firewall is probably what is keeping the
system from accessing that remore database. Sounds plausible, but I
haven't found much while web searching that explicitly confirms that.
More to the point, I don't have ANY clues or ideas from anywhere on how
to resolve this problem at client sites that seem to prohibit MySQL
access of a remore database.
Suggestions?
Confirmation that it's a firewall problem?
Ideas?
Encouragement?
*** THANKS! ***
Kevin Killion

Unless you have a business reason to do so, I block those ports as well to keep
hackers from attacking mysql databases. IMPO - Any corporation NOT blocking it
is either very stupid or very ignorant. And the difference is - one can be
cured and unfortunately the other cannot.