Inside firewall access to outside firewall MySQL server

[dstewart]

I have 2 Suse 9.1 boxes with similar configurations. I'm in the
process of moving some PHP code from one server (192.168.0.100) to
another (192.168.0.102). MySQL is running on each server, and the same
PHP code can access its respective localhost databases and make queries
with no problem.

However, the code on the old server (.100) can access a MySQL server
(12.xx.xx.50) outside the firewall (192.168.0.1), while the code on the
new server cannot.

There is NO firewall rule regarding the two servers -- they are NOT
being accessed from outside the firewall.

Give me an idea where to start looking for the cure to the problem.

Danny

[Aggro]

ds******@pcfa.org wrote:

Give me an idea where to start looking for the cure to the problem.

Have you granted access to MySQL from outside? For example by

grant all on databasename.* to username@'192.168.0.22' identified by
'password';

[Mike A]

Can your new server access the internet at all?

Is the default route, gateway, and DNS information correct?

Try pinging the destination IP (12.xx.xx.50)...
Mike Argy
Custom Office solutions
and Windows/UNIX applications

On Sat, 05 Feb 2005 18:58:41 -0800, dstewar wrote:

I have 2 Suse 9.1 boxes with similar configurations. I'm in the
process of moving some PHP code from one server (192.168.0.100) to
another (192.168.0.102). MySQL is running on each server, and the same
PHP code can access its respective localhost databases and make queries
with no problem.

However, the code on the old server (.100) can access a MySQL server
(12.xx.xx.50) outside the firewall (192.168.0.1), while the code on the
new server cannot.

There is NO firewall rule regarding the two servers -- they are NOT
being accessed from outside the firewall.

Give me an idea where to start looking for the cure to the problem.

Danny

[Mike A]

One other thing to check...

Try using a different private IP address. Your firewall may have DHCP
running, even if you are using static adresses on your lan, and may not
accept connections outside of its configured IP address range. Maybe .100
happens to be within its range and .102 isn't. Take your old server
offline for a few minutes and set the IP of the new server to 192.168.0.100.

Good luck!

Mike

On Sat, 05 Feb 2005 18:58:41 -0800, dstewar wrote:

I have 2 Suse 9.1 boxes with similar configurations. I'm in the
process of moving some PHP code from one server (192.168.0.100) to
another (192.168.0.102). MySQL is running on each server, and the same
PHP code can access its respective localhost databases and make queries
with no problem.

However, the code on the old server (.100) can access a MySQL server
(12.xx.xx.50) outside the firewall (192.168.0.1), while the code on the
new server cannot.

There is NO firewall rule regarding the two servers -- they are NOT
being accessed from outside the firewall.

Give me an idea where to start looking for the cure to the problem.

Danny

[dstewart]

Aggro wrote:

ds******@pcfa.org wrote:

Give me an idea where to start looking for the cure to the problem.

Have you granted access to MySQL from outside? For example by

grant all on databasename.* to username@'192.168.0.22' identified by
'password';

I am using the same routines, including the same user names and
passwords, from the 2nd server. The MySQL server sees the same IP
address (the firewall IP number() for the new server as the old server.
So, there is not a difference, is there?

[dstewart]

Mike A wrote:

Can your new server access the internet at all?

Is the default route, gateway, and DNS information correct?

Try pinging the destination IP (12.xx.xx.50)...

Yes, it's fine for all functions except accessing the MySQL database
server.

[dstewart]

Mike A wrote:

One other thing to check...

Try using a different private IP address. Your firewall may have DHCP running, even if you are using static adresses on your lan, and may not accept connections outside of its configured IP address range. Maybe ..100 happens to be within its range and .102 isn't. Take your old server
offline for a few minutes and set the IP of the new server to 192.168.0.100.
Good luck!

Mike

I'm sure this is not a network issue. The netmask inside the firewall
is 255.255.255.0. DHCP is handled from one box inside the firewall
(not the firewall). There are only a few DHCP addresses and all are
above .200 .