I just fixed the exact same problem on the exact same hardware and my OS is
Windows 2003 Enterprise R2.
I tried all of the same things everyone mentioned, but a little background
info. I just installed the OS and was trying to install the drivers for the
HP Proliant ML350 G5. The first time I was installing the network drivers I
had no idea what nic was on the motherboard so just started running NIC
driver installs for Intel and for Broadcom until one of them worked. So I am
sure that one of these attempted driver installs created my problem. Since I
had just installed the OS and the server was not in the domain yet I didn't
spend much time trying to fix and instead just reinstalled Server 2003 Prof
R2.
The trick to installing drivers on the Proliant server is to get the
Proliant Support Pack (PSP) and run it to install the drivers. (below is a
link to the PSP)
http://h20000.www2.hp.com/bizsupport...eriesId=327479
The other trick for me was not to run the wrong driver installs.
Now the IP address stays and does not revert to DHCP.
"Ray" wrote:
> I have a client, I assign a static IP, then ok my way out. Then go back into
> TCP/IP properties the network card is dynamic again. The server will hold the
> IP until the server reboots. The server reverts back to a dynamic IP.
>
> I worked with HP, we replaced all of the networking software, firmware,
> driver and HP networking software. Rebuilt the TCP/IP and Winsock stack. No
> luck, HP replaced the motherboard with no luck. I installed a USB NIC, it had
> the same problem, the IP wont stay static.
>
> It is a HP Proliant ML350 G5, Server 2003 Standard, fully patched.
>
> It must be a software issue. Any ideas?