What you are describing sounds rather convoluted. If you could provide more detail as to why this needs to be, perhaps a more elegant solution could be worked out.
I'm pretty sure it can't be done that way. With DHCP enabled, you don't have the option to add another IP address. The ADD button is greyed out in the Advanced properties.
You can add a static address through the alternate configuration, but I'm making a guess that you want the NIC to use both addresses at the same time.
Basically we are migrating to Windows Server 2003 and we will still need to access some of our legacy servers during the migration.
Ideally we would set the client PC's with two IP addresses until we had fully changed over. The old system is all static IP addressing, the new stuff uses DHCP.
Even though the new stuff uses DHCP, you can still assign a static address to the NIC. The DHCP server shouldn't try to assign an address that's being used. You could also set the DHCP server to not assign that particular address while you're using it for a static address.
What I mean is statically assign both addresses for now. On the DHCP side you can assign static addresses (big pain on a large network, I know) and the DHCP server shouldn't try to issue those addresses while they are being used. You could always exclude those static addresses from the DHCP list for the time being.
Then add the second network's IP address to the NIC. I've tried to find a way to have DHCP on one side of the NIC and static addressing on the other side and I can't find a way to do it. It's a good idea though if we could get it to work. I'm already seeing an area I could use it.
Not wanting to be redundant, you are migrating to winserv 2003 from a "Legacy Server platform"?? What is it? Win NT X.X or NetWare? or ???
Can you establish the "legacy stuf" in a distributed environment? or are there applications that must be run?
If only data, this should be workable. The legacy stuff can be set to DHCP also and included in the entire network and accessed. No requrement for client side to have both Static and DCHP assignments (clients 1 to 1k's) servers = 1 to several.
If you add a second NIC card, you can assign different IP addresses, a differnt one to each card. They're not that expensive. I presume you're asking about the server(s). If you're asking for each workstation, this suggestion wouldn't be practical.
We are migrating from a mixed NT4/Netware 3.2 environment, the problem is we have a big site and the rollout is going to be phased over a few months. People will need to access both the New 2K3 servers and still login to the old Netware servers for a while until everything has been changed over fully.
An interesting statement at the bottom in Note 2 :
Note 2:
If you need to use DHCP for one of you IP addresses, set the adapter up first to use DHCP as normal. Follow the all the steps listed above and append the "0.0.0.0" with the fixed IP address you wish to assign to it.(ie. "0.0.0.0,169.254.254.1")
The article relates to Windows 98, I have just tried this in XP and it didn't seem to work , but seems to be possible!?!
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.