Static IP reverting to DHCP in GUI interface only

Might I add that I do not believe viruses/spyware are causing this issue. I find nothing threatening with Hijack this or anti-spyware scanners and no services look out of place or strange. There are also no running programs in memory that look foreign at all.

Try unticking TCP/IP on both NICs, rebooting the server, ticking TCP/IP and rebooting again.

I will have to try that, sounds like a good idea I'll just have to wait until after hours. Right now the server is functioning but I do not want to ignore this odd TCP/IP issue. I'll get back to you, Darylx and anyone else that posts tomorrow. I'll be reading this periodically all day.

After a reboot, I reapplied the static IP and once again DOS says the is manual and states the correct IP, Windows GUI says DHCP.

Did you untick TCP/IP then reboot, re-add TCP/IP then reboot again?

Yes. Problem still persists.

I have the same problem. have you unistalled ISA installed on this machine?, are you getting the DHCP server listed as 255.255.255.255, when you look at network status?

Same issue here...anybody have any other ideas?  Tried updating all sorts of drivers and uninstall, reinstall of the drivers, including manually deleting drivers, problem still persists.  Also hacked on the registry with static IP information, and problem still exists...

Bout ready to hang myself...anyone have rope?

NGCMidget

I've having the same problem, and the following is what I've learned:

I'm guessing the network cards that you're using Broadcom BCM5708C NetXtreme II Gig E cards?
If so, from what I've read, it might be a known driver issue from Broadcom.
I'm still hunting down how to install the latest and greatest driver to the system without causing more harm than good.
I downloaded the latest and greatest firmware and ended up with a computer that wouldn't even initialize the network cards.
Fortunately, I had ghosted the machine first.

Other sites have suggested that Broadcom drivers can't be installed directly either, that one must download a driver loader from your computer manufacturer website so that the driver integrates properly.

I'll keep you posted as I find out more.

I don't have the BCM5708x, but rather mine is a NC373i.  I also flashed the firmware with no problems at all as far as errors making my machine unbootable, but it still did not fix my issue.  That driver loader from HP is exactly what put my machine in the state it's in right now.  Before I loaded the HP Network Configuration Utility (NCU), our system worked fine.  

I have since loaded a x64 bit server with the identical hardware configuration and using similar downloaded drivers and it works flawlessly as well.  I will not be loaded the NCU on this particular box.

Still clueless,
NGCMidget

If the author has found a solution that works, I'd like it posted so I can use it as well.
If not, I'd like to know so that I can go back and open up a similar question, seeing as I'm having the same problem, and it is still a problem.

Sorry about that, I do not recall seeing anything from TomPro on down the list before I posted to close this thread. I can try messing with the drivers but I have to do it after hours and at this point being that it has been so long this is no longer a terribly important issue. It definitely needs to be solved but timeliness has already been shot down. I don't know what to tell you, I will be trying to use different drivers at some point when I get to it but after 2 months I just need my coworkers to stop getting emails about this thread.

That being said I really appreciate all comments and suggestions but nothing so far has worked out, I'll have to try TomPro's suggestion but I'm not entirely sure when I will revisit the issue. It will likely be this weekend or next weekend.

What I just found out is extremely strange. We have a small tight knit group of techs here and I have just talked to all of them. No one has been troubleshooting this problem but me. I have had 0 success and always rebooted after attempting fixes and the problem persisted. I just logged in today and it looks fine. The GUI is showing the manual configuration and so is the command prompt.

Load balancing appears to be off by default - That was about the only setting I didn't take note of because I haven't touched it.

The solutions I did try were:

 1) Removing the check from the TCP/IP Protocol box for the adapter and rebooting. Then after the reboot, checking the TCP/IP box adapter and rebooting again. I checked several times at different times and the GUI still was showing "DHCP" and the command prompt had manual configuration. There are 2 network cards but only 1 has been plugged in ever, so I know I'm not confusing the cards with each other.

2) Uninstalling and re-installing the drivers for the network cards and rebooting. Once again I checked several times and on different days and still the problem existed.

So today after posting just above, I decided what the heck? I'll just give it a once over and see if maybe it'll tell me I have a DHCP server of 255.255.255.255 as MacPad suggested. To my amazement the problem is gone and everything appears normal. There is nothing that could have been done out size of some possible server reboots. How strange is that? We have to be close here to an actual solution.

Well I would say this could be closed and refunded. I did not find a clear solution and the problem disappearing is awfully strange. The only logical possibility is that someone updated their custom software without telling us and that in some way was affecting the TCP/IP stack. I would hope TomPro makes his question with the same issue and maybe the answer will be hashed out in that thread. Due to the mysterious nature of my problem and its appearance and disappearance not too much could be gained by the community from this thread. I apologize that this came to such a bad ending but I've never quite seen anything like what just happened.

I'd be more than happy to start my own thread, but what's the best way to link to this thread for the specifics of the problem.
To rewrite all steps that we've tried seems redundant.

Adendum - For safety's sake, make sure you export the reg entry to a file and saved to the disk before deleting, just in case.  ;-)

I believe that was one of the things that I tried that didn't work.
I'd have expect that uninstalling/reinstalling TCP-IP (with a reboot in between) would have accomplished all  registry changes and more than a netsh reset would have.
And I'm pretty sure that jsbush and I both tested that and that didn't work..

I also checked Microsoft's KB (http://support.microsoft.com/kb/317518) and if you look at the standard list of registry entries that it deletes/resets, and this particular entry is not in that list.

TP

This worked for me.

Thanks.

We had exactly the same problem on a Dell Poweredge 2950.. Dual Broadcom 5708C
i) Netsh int ip reset did not work
ii) Uninstalling and reinstalling the cards with new firmware and drivers did nto work
iii) Deleting TomPro's entry (the config in currentcontrolset001) DID work and thanks a lot too.. really appreciate it at 05:30am..
Mac

I used solution and successfully resolved the issue as user TomPro described it. Thank you Tom for coming back and posting!

This solution also worked for me on a system running XP 64-bit with dual NVIDIA nForce 10/100/1000 NICs. Thanks Tom!

Ok, one of those OMG moments here, it worked for me on Win8 Pro x64 so this prob has survived many versions of Windows !