TCP/IP properties disappear

I have some Dell 1950 and 2950 servers with the dual broadcomm NIC's in them.
We disable the 2nd one on every server. I set it to a static IP address and
hit apply and then okay.

Starting about a week ago when I go right back into the properties on few of
the servers the adresses do not display and it's set back on the DHCP button.
I run ipconfig and it does save the settings until I reboot then it's back on
DHCP. These servers were perfectly fine for month's up till a week ago and
not a single network change has been made. Is this the effects of a new M$
patch?

I ran that command line tool that resets the TCP/IP stack but it doesn't
help at all.

I also tried new drivers for the NIC.. removed it totally and reinstalled the
NIC.. nothing. anyone seeing anything of the like?

Thanks!



"Austin" wrote:

> I have some Dell 1950 and 2950 servers with the dual broadcomm NIC's in them.
> We disable the 2nd one on every server. I set it to a static IP address and
> hit apply and then okay.
>
> Starting about a week ago when I go right back into the properties on few of
> the servers the adresses do not display and it's set back on the DHCP button.
> I run ipconfig and it does save the settings until I reboot then it's back on
> DHCP. These servers were perfectly fine for month's up till a week ago and
> not a single network change has been made. Is this the effects of a new M$
> patch?
>
> I ran that command line tool that resets the TCP/IP stack but it doesn't
> help at all.

I'm getting the exact same thing. We're running on IBM hardware with 2
nics, one disabled. (I don't know if that's significant, but it's the
same as your situation.) This server is running DCHP, DNS, AD, and
TS. (Smallish company with one server.)

I go into TCP/IP properties on the enabled NIC, and it thinks
everything is dynamic (DHCP, auto DNS). I set it to a static address
and it takes it, but if I reopen the TCP/IP properties page, it still
says it's set on DCHP. After a reboot, it assigns itself a 169.blah
IP until I fix it to its static address again.

Any feedback or ideas would be appreciated.

Yep what you explain in the second paragraph is exactly what we have. Are the
2 NIC's you have Broadcom NetXtreme II's by chance? maybe it's a deal with
just them...

1 of our servers is very basic, just a member of the Domain with a basic
website running on IIS is all.. the second machine runs our DNS for the
company is a domain server (not the catalog or PDC though) but same problem.

I hope more people see this problem so we can get a fix.. I have scoured
every word combination I can think of on Google and you are the only other
person that seems to have seen this.






"(E-Mail Removed)" wrote:

> I'm getting the exact same thing. We're running on IBM hardware with 2
> nics, one disabled. (I don't know if that's significant, but it's the
> same as your situation.) This server is running DCHP, DNS, AD, and
> TS. (Smallish company with one server.)
>
> I go into TCP/IP properties on the enabled NIC, and it thinks
> everything is dynamic (DHCP, auto DNS). I set it to a static address
> and it takes it, but if I reopen the TCP/IP properties page, it still
> says it's set on DCHP. After a reboot, it assigns itself a 169.blah
> IP until I fix it to its static address again.
>
> Any feedback or ideas would be appreciated.
>
>

> Yep what you explain in the second paragraph is exactly what we have. Are the
> 2 NIC's you have Broadcom NetXtreme II's by chance? maybe it's a deal with
> just them...

No, the two onboard NICs I'm using are a RealTek and a VIA Rhine II.
It doesn't seem like a driver issue; rebuilding the TCP/IP stack was
more in line with the problem, to my mind. I mean, it looks like an
OS issue to me.

I'm also getting the following error in the application log (source
Userenv, ID 1000):
Windows cannot access the file gpt.ini for GPO The file must be
present at the location <>. (). Group Policy processing aborted.

It may or may not be related.