You could also create a batchfile that uses the netsh command to change both the subnet and gateway with the click of a mouse. Have it ask for input, namely the location and it would then apply the appropriate settings.

0

I don't get what is so horribly difficult to setup a DHCP server for each segment, or setup a DHCP server and DHCP Relay Agents on the other two segments. It would be far more reliable, require far less administrative effort, and would work immediately for each additional client plugged into the network. TECH-NO-LOGICAL ROMANCE! http://www.homestarrunner.com/tgs12.html

0

You know it hero......however, a lot depends on your environment. Where I'm working, everything is static. There is no DHCP except on the WLAN. This means extra work for yours truly and my coworkers in the "Infrastructure" dept (renamed from Telecom & Networks in a recent structural change) but it's just something we have to live with. We're presently underoing some very serious changes in the infrastructure of our environment with the addition of multiple new routers to segment everything. Once this project is done we're hoping to convince the powers that be to go with a DHCP environment because it would as you well know, make our lives easier. I guess we'll just have to wait and see. The problem is this. It's been this way since the business started out in the early 80's and the big bosses just don't have a real understanding of the technology. Try explaining DHCP vs static IP's to someone who doesn't know what either means......LOL. In the end, we should be able to get what we want, it's just going to take a lot of "persuading" and explaining on our part. The real hurdle is as I mentioned, explaining it to people who's response is "Well, it's working alright now, so why change it?" I can't speak for the original poster and his environment but I know this much. If the choice were mine where I work, it would be DHCP now and would have been from the moment I could make it happen.

0

"The problem is this. It's been this way since the business started out in the early 80's and the big bosses just don't have a real understanding of the technology. Try explaining DHCP vs static IP's to someone who doesn't know what either means." They understand dollars. Show them how much money is spent in labor to maintain a list of IP's used, which node has which IP, how much it costs in downtime when accidents happen when multiple people have the same IP's, etc. Then show them how much it costs to implement DHCP. If they're stupid enough to advocate static IP's at that point, run, don't walk, to your next employer. ;-) TECH-NO-LOGICAL ROMANCE! http://www.homestarrunner.com/tgs12.html

0