Ok, so at work we have two different networks, one internal for our test group, and one external network. The database we use to store code for our systems is accessed through the external network and cannot be reached by systems hooked up to the internal network. Basically we want one machine to connect to the external network, download code and do other tasks, and then switch to the internal network so that the test systems can access the code that we just downloaded. At no time can both networks be active on the same machine for security reasons so the system that is connected to both, must disconnect from one before connecting to the other. Anyone have any suggestions on how to do this? We are working on some programs here to automatically download code and update systems so something in Java or another language vs a sepparate program would be nice. Thanks.

9/26/2006 2:37:14 PM

Is it strictly a database which stores all code/metadta/etc. on the external website? Which development environement/database is this?

9/26/2006 7:36:48 PM

There are a few databases and servers that we use, all of which we do not have any control over. All we do is connect and get what we need. The two main ones that we are looking to connect to are an ftp server with new BIOS and other sytem code levels, and a defect repository database where we keep defect information for tests we write. I have written Java programs to access the ftp server, and we have a Java API for accessing the defect database, so that part is taken care of. The only thing we need to figure out how to do is have the ability for a machine to access either network at a given time, without allowing external traffic onto the internal network. We'd like to be able to control swtiching back and forth through software so we can integrate it with what we've done so far into an automation program. I'm by no means a network guru so there maybe a very simple answer to this that I am just ignorant of. After my first post I thought we might be able to use Java to execute a command line operation to change IP addresses, but we still have the physical connection to work out. Any ideas?

9/27/2006 9:40:37 AM

1) VPN tunnel from one network to the other

2) poor man's solution: have two ethernet ports, one for one network, and one for the other, and move cable as needed.

9/27/2006 9:44:24 AM

I'll look into the VPN tunnel, but the idea is to have everything automated so we wouldn't have someone there to physically move the cable.

9/27/2006 10:05:47 AM