2 NICs, one connected to production LAN, the other test LAN - how do I route?!

Hi

I have a Win XP Pro client on a  production Win 2003 SBS domain via a 100Mb wired network. I have another net connection on the same host, a wireless 54Mb connection to our test LAN.

The IP of the production NIC is 192.168.46.77 (static) and the IP of the wireless NIC is 192.168.46.3

There are 2 hosts on the test LAN with IP's 192.168.46.1 and 192.168.46.5. I would like to access both addresses, but I would settle at only being able to access the 46.1 address if both were not possible.

There are approx 50 hosts on the production LAN with addresses in the 46.x range. There is a host on the production LAN that has the address 192.168.46.5. The reason there are 2 hosts with the same IP is that I am performing a migration to new server hardware.

At the moment, I cannot access the test LAN without disabling the production NIC. I realise this is because they are on the same subnet, but I need to know how to access the test LAN without disabling the production NIC.
LVL 7
5t34lth_G33kAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

pseudocyberCommented:
The best practice is to use naming instead of IP's - then when you migrate, there's no problem and you don't have to change the IP's.

In order to do what you want you're going to either have to:

A.  Change the IP Scheme of the test LAN.  The problem is that your machine knows the IP of 192.168.46.0/24 belongs on your production NIC and not your wireless NIC.  To get the two to work to gether you'd have to set up bridging, which would be bad.  Changing the test LAN, and it really should be different if you want to be dual attached, then you need to set the test LAN to a different IP like 192.168.50.0/24.  Then, your machine will have two dual attached networks and know the difference between them and how to route.  You might have two default routes, if you do, simply delete the 0.0.0.0 default route (using the command "route delete") which is going to your test LAN.

OR

B.  Either only use one connection at a time, or set up some relatively complex equipment to NAT between your test LAN and your production LAN so that you can use the two together.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
5t34lth_G33kAuthor Commented:
Cant change the IP scheme, as I am setting up one of the test LAN's servers to be the replacement DC, mail server, DNS server etc of the production LAN, therefore the IP must be the same for consistent DNS entries.

I have added a static route on my host to use the wireless card for the 46.1 address, which means that I can now access that particular server on the test LAN. Obviously this will not work for the 46.5 address, since there are 2 of them, so I guess I am stuck with using one or the other
pseudocyberCommented:
Ok.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Networking

From novice to tech pro — start learning today.