I have an environment where my work computer needs to be connected to two separate networks. My "lab" connection is via my ethernet NIC and I use wireless to connect to the outside world. (I have a separate machine for connecting to the corporate network.)
The wireless network consists of a basic wireless router connected to a cable modem. (my current ip on this network: 192.168.1.117)
The lab network is just a single machine running Windows Server 2003, and is a domain controller w/ DHCP enabled. (my current ip on this network: 10.1.1.1)
With default settings I can hit web pages hosted on the wired network but not on the wireless. If I disable the ethernet NIC and run
ipconfig /renew then I can use the wireless network, but obviously not the wired.
If I assign the IP address on the wired NIC manually then it works, however, the next time I plug in to a network anywhere else I will inevitably wonder what's wrong until I remember to change my settings, and then I will have to change them back again.
I imagine I need to play with the ROUTE command more but I see that
route add requires a destination network, and I want something more along the lines of "route everything on subnet 10.1.x.x through interface A, everything else through interface B."