A machine with an IP of 10.0.36.x won't be able to talk to 172.16.11.x unless routing is set up properly. When you have more than one subnet, routing between them requires a good understanding of your entire network.

A machine with an IP of 10.0.36.x won't be able to talk to 172.16.11.x unless routing is set up properly.

That's not the problem here. Box1 has two NICs, one on each network.

It's really not necessary to have physically separate NICs (unless this is a security or capacity issue), but that's neither here nor there for this problem.

You'll need to set-up box1 to route between the subnets. It doesn't do that by default.

You didn't say where the MySQL server is. Box2? So, a workstation connected to Box1 wants to access the MySQL server on Box2?

The MySQL server is on Box2. Yes, a workstation connected to Box1 wants to access the MySQL server on Box2. Box1 is a webserver and is pulling data from Box2's MySQL, but we just don't know how to get to it from a workstation that only connects to Box1. We are using an Access switchboard to input data to other databases we have in the office, but have not been able to link it to the MySQL database on Box2.

OK, as I stated previously, you will need to set-up box1 to route between the networks. It doesn't automatically do that, just because it has two NICs.

Since there are some variations between Linux versions, I'd suggest you do a search on "Linux routing".

You might be able to do it with a GUI tool. If not, you will have to use command-line tools.

Sorry about that. I was just answering the questions that were posted. I'll google Linux routing.

as some some has has you need to route between the private class A to the 172.16.11.xx adresses.

You can do this on the box but it would be better to connect both networks to a router to do this.

also out of the box mysql only acepts connections localy if you want to access from another host you will need to set up the access controls to allow this.