Windows 7: DHCP and static ip simultaneously, one nic ?

Thanks for your reply mckillwashere. However, I am in the same boat as some others on this thread where that simply isn't an option. (You can't just ride roughshod over the MIS department of a large multinational corporation and assign yourself static IP addresses on the corporate network subnet).

What I'm after is a solution for using DHCP and Static "at the same time" as you could on Windows XP.

This is not an easy solution in my case, I'm working in different locations where different subnets are used (2 offices and home: 192.168.10.0/23, 172.16.202.0/23 and 192.168.1.0/24 ranges) and for work (in all locations) I use embedded devices which mainly have static IP addresses in the 10.0.0.0/8 and 192.168.0.0/24 ranges. Therefore I want to have 2 static IP address in the 10.0.0.0/8 and 192.168.0.0/24 ranges and DHCP turned on for connecting to the office/home network.

At this moment I've set 1 static IP address for each range (which means 5 static IP addresses), but I almost always get an IP conflict when I return to one of the offices after not being there for more than a few days.

I used to have XP and it worked flawlessly, why doesn't it work anymore???

Hey, i'm not sure i understand the problem completely. But just to add, my office wireless network assigns ip's dynamically while on my home network, I've assigned static ip's. Theres one machine that I use between work and home, on this I use netsetman on which i've created 2 network profiles- one with the auto-ip specs for the office and the other with my home static ip's. I just switch to the relevant profile as required.

Does that seem useful or is it way off the mark?

Well, I need to have 2 static IP addresses at any time for doing the development on the devices. Next to that, I would just like to use DHCP to always get a non-conflicting IP address for that location. Also DHCP will make sure that things like DNS servers and DNS suffixes are correct in every location.

What bugs me most is that I used Windows XP for years and I didn't need an extra nic or extra tools and now with Windows 7 I have to take a step back...

Mate you may get more help if you start a new thread rather than resurrecting a dead thread.

I know this is an old thread but THERE IS A SOLUTION, tested !

winipcfg / Win IP Config

this is the ONLY solution I have come accross in the world for this solution.

There are 2 tools to solve this Vista/Windows 7 issue, but after a dhcp refresh or cable replug settings are gone. One tool is "Win IP Config", a graphical tool to add ips. The other one is iphelpcon.exe, a commandline tool (to put into Startup folder). The second tool uses the function AddIPAddress of the M$ dll: iphlpapi.dll.


https://anonfiles.com/file/51c4fe4b6...0228bd0c1dd50b


winipcfg / Win IP Config


Cheers jona

Thank you so much for the help.

Win IP Config was the solution for me!

Win IP Config solved this hairy problem for me in Windows 7!

It seems like there are a lot of people who don't understand why having a simultaneous DHCP and static IP would be necessary or convenient.

In my case, I have to configure machine control systems that communicate over multiple subnets, between engineering computers that must do the same, while maintaining the ability to access files on the corporate servers, and access the internet for drivers, software updates, etc.

This particular project has a Siemens PLC communicating with 6 Caterpillar generators using MODBUS TCP on xxx.xxx.1.1 thru xxx.xxx.1.6, with the PLC assigned xxx.xxx.1.7, and the HMI on xxx.xxx.1.8.

My router is set to assign DHCP addresses on xxx.xxx.47.xxx, connecting me to the corporate network via NAT.

The MODBUS simulator is running on an XP machine that is assigned an address via DHCP from my router xxx.xxx.47.xxx, plus the six generator IP addresses (xxx.xxx.1.xxx), plus an additional IP address to make it accessible from the xxx.xxx.1.xxx subnet.

The HMI simulator is running on a Win 7 machine that also receives a DHCP address, but required the additional xxx.xxx.1.xxx address to make it visible to the Siemens PLC and the Win XP machine while preventing the TCP/IP stack from binding to any of the addresses reserved for the generators.

Additionally, I need DHCP addresses to be available for ease of administrating a program called "Input Director" which allows me to share clipboards and control any of eight screens, from any mouse attached to any of my 6 engineering PC's.

The registry hack made setting up dual DHCP/Static IP's easy on the XP machine, but Win 7 was a different story.

While all of the above was certainly possible by assigning static IP's across the board, the combination of applications I use requiring network access makes it impractical to manage quickly.

Win IP Config saved the day, thanks for the suggestion!!!