Network cards switching to DHCP from static addresses

[ctjohnson]

We're having a bit of a weird problem. We've rebuilt two domain controllers. Both have dual nics, one for the production network, one for the backup network. After setting static IPs on both nics, we reboot the machine.

The card that has the static ip configured on it most recently reverts to dhcp, and the other card keeps a static ip. We're only experiencing this on two servers, but its becoming a major problem. Any advice? These machines both had two static ip addresses, one on each card before with no problems.

 

[ashleym]

Does it happen if you log out and log back in?

Are you using the most up to date drivers for the NIC?

Have you tried setting one nic to static and the other to dynamic to narrow it down to see if the problem is with one nic?

Just some ideas.

AM

 

[ctjohnson]

Thanks for the response...

we're using up to date nic drivers.

the problem occurs even without logging out and logging back in - - for example, we change the ip address, look at ipconfig, and it displays the static address. then, we click on properties for the nick card, and it reverts back to dhcp.

the problem occurs on either card, which ever happens to be set last.

any more ideas?

thanks

 

[FilthPig]

Do you have any services running (IIS, Exchange, SQL) that might be listening on specified IPs? For example, you can tell your virtual servers in Exchange to either listen on all IPs, or you can tell it which IPs to listen on. I've had problems with ports in IIS because of similar setups, and I imagine the same could happen to IPs. Marc Creviere

 

[GlenJohnson]

Is DHCP disabled in services or are these handing out dhcp ip's? Glen A. Johnson
Microsoft Certified Professional
gjohn76351@msn.com
"Accident is the name of the greatest of all inventors."
Mark Twain (1835-1910), U.S. author.

 

[ctjohnson]

Glenn-
One of the boxes is a DHCP server, the other is not. I tried disabling the DHCP client service, but the machine wouldn't boot then...

 

[GlenJohnson]

Do you have a conflict? Is one of the nics set for dhcp, so when you disable it, it won't boot? You didn't try and disable dhcp on the dhcp server? (Sorry, I know it sounds stupid, but I've done some stupid things in my life.) Glen A. Johnson
Microsoft Certified Professional
gjohn76351@msn.com
"Accident is the name of the greatest of all inventors."
Mark Twain (1835-1910), U.S. author.

 

[ctjohnson]

heh, thanks for the help. let me try putting this a different way. the machine has two nic cards. we set static ips on both, and ipconfig lists the static ips.

when you click on the properties of the nic card, it reverts to dhcp. the same thing happens when you restart the computer, it reverts to dhcp on the last card configured.

just for fun, we disabled the dhcp client service, so it couldn't get an address. the machine wouldn't boot up at that point. this happens on a box that's a dhcp server, and on that isn't so i'm confident the problem isn't related to that.

thanks!

 

[Guest_imported]

There is no mention of IP Addressing. Are both IP's on the same IP subnet? You are multihoming, and it may be because they are on the same subnet, and W2K will not allow this.
Just my visisting .02.

 

[ctjohnson]

They are on different subnets, one is a network used soley for backup, one is the production network.

 

[david817]

I have exactly the same problem with my pdc. If I use ipconfig /all it shows all the correct settings but when I go to network neighbourhood properties it is set as DHCP no matter what I do. I have changed the DHCP server to my bdc, I have gone into the registry and set dhcp clent to disabled and every time I boot up it is still set to DHCP. I have also tried removing file and print sharing (be carefull if you try that and back up your shares first) removing tcp/ip and reinstalling it (the check box is all you can remove) but to no avail. It is driving me nuts as it is effecting exchange server users and computers etc.
Hope somebody can help
David

 

[david817]

Reboot the machine and go into directory restore mode, uninstall tcp/ip reboot to drm and reinstall tcp/ip roboot to normal.

Dave