Issues with connecting servers in various ways

I have to get the following done but am not sure of the best way to do it or issues involved.

We have a web server.  We have a network with a database server.  There is a need to have the web server to connect and talk to the database server.  

Proposed solution is to have a second ethernet card in the web server and a second card in the db server and connect them directly via a cross over cable.  The ip/subnet would then be set up different than the intranet.

If we do this, we will set up an odbc to connect to the database.  This would connect via a user that only has read only to the db.  

Obiously we want to limit security issues if we can.  What other things must we do or think about to try to keep someone from getting to the db server via the web server but still allow the odbc connection to exist?
mindarchAsked:
Who is Participating?
 
jhanceConnect With a Mentor Commented:
In general that's a good solution and is widely used.  Since the web server to DB server link is private there is no exposure risk since the DB server is not accessible by any system other than the web server.  If no IP forwarding or routing services are setup on the web server, no web traffic will be getting to the DB server.  This also keeps the web server to DB traffic from getting bogged down with other network traffic that may exist.
0
 
mindarchAuthor Commented:
Thanks jhance.  Do we need to set up anything other than the odbc?  

Stephen
0
All Courses

From novice to tech pro — start learning today.