network connections keep reverting to DHCP!

hey averyone i have a node in a cluster that i am building, that normally has
a static IP manually entered into its network connection, but the damndest
thing started happening to it the other day, as soon as i enter the static ip
and relevant information in and hit ok and close the network connection, if i
go back into the connection it is set to gets its ip automatically via dhcp!
and has wiped the static ip out, in the server subnet it resides in there is
no DHCP either so it gets a 169. autoconfiguration address.

i will note the following details, it is a windows 2003 enterprise server,
dell 2950 with broadcom nic's i dont have any teaming going on or any
configuraiton assiged from the broadcom software(yet) and one of the network
interfaces is connected to the other windows 2003 server node in the cluster
via a crossover cable

has anyone seen this before? bizzare!

thanks guys!

anybody?

"Jammer" wrote:

> hey averyone i have a node in a cluster that i am building, that normally has
> a static IP manually entered into its network connection, but the damndest
> thing started happening to it the other day, as soon as i enter the static ip
> and relevant information in and hit ok and close the network connection, if i
> go back into the connection it is set to gets its ip automatically via dhcp!
> and has wiped the static ip out, in the server subnet it resides in there is
> no DHCP either so it gets a 169. autoconfiguration address.
>
> i will note the following details, it is a windows 2003 enterprise server,
> dell 2950 with broadcom nic's i dont have any teaming going on or any
> configuraiton assiged from the broadcom software(yet) and one of the network
> interfaces is connected to the other windows 2003 server node in the cluster
> via a crossover cable
>
> has anyone seen this before? bizzare!
>
> thanks guys!

I have heard of it happening a few times. But I don't know remeber the
solution so I didn't reply,...I was waiting to see what others might have to
say.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------

"Jammer" <(E-Mail Removed)> wrote in message
news:71E00E75-2A82-4B27-9028-(E-Mail Removed)...
> anybody?
>
> "Jammer" wrote:
>
>> hey averyone i have a node in a cluster that i am building, that normally
>> has
>> a static IP manually entered into its network connection, but the
>> damndest
>> thing started happening to it the other day, as soon as i enter the
>> static ip
>> and relevant information in and hit ok and close the network connection,
>> if i
>> go back into the connection it is set to gets its ip automatically via
>> dhcp!
>> and has wiped the static ip out, in the server subnet it resides in there
>> is
>> no DHCP either so it gets a 169. autoconfiguration address.
>>
>> i will note the following details, it is a windows 2003 enterprise
>> server,
>> dell 2950 with broadcom nic's i dont have any teaming going on or any
>> configuraiton assiged from the broadcom software(yet) and one of the
>> network
>> interfaces is connected to the other windows 2003 server node in the
>> cluster
>> via a crossover cable
>>
>> has anyone seen this before? bizzare!
>>
>> thanks guys!

I am experiencing a very similar scenario on a 2003 R2 server with SP2. This
is in a small business environment and this is the only server. Interestingly
it saves the information, if I run “ipconfig /all� it displays exactly what I
entered but the settings page displays that the NIC is set for DHCP. The
server is functioning with the address I assigned. Any solutions?

"Phillip Windell" wrote:

> I have heard of it happening a few times. But I don't know remeber the
> solution so I didn't reply,...I was waiting to see what others might have to
> say.
>
> --
> Phillip Windell
> www.wandtv.com
>
> The views expressed, are my own and not those of my employer, or Microsoft,
> or anyone else associated with me, including my cats.
> -----------------------------------------------------
>
> "Jammer" <(E-Mail Removed)> wrote in message
> news:71E00E75-2A82-4B27-9028-(E-Mail Removed)...
> > anybody?
> >
> > "Jammer" wrote:
> >
> >> hey averyone i have a node in a cluster that i am building, that normally
> >> has
> >> a static IP manually entered into its network connection, but the
> >> damndest
> >> thing started happening to it the other day, as soon as i enter the
> >> static ip
> >> and relevant information in and hit ok and close the network connection,
> >> if i
> >> go back into the connection it is set to gets its ip automatically via
> >> dhcp!
> >> and has wiped the static ip out, in the server subnet it resides in there
> >> is
> >> no DHCP either so it gets a 169. autoconfiguration address.
> >>
> >> i will note the following details, it is a windows 2003 enterprise
> >> server,
> >> dell 2950 with broadcom nic's i dont have any teaming going on or any
> >> configuraiton assiged from the broadcom software(yet) and one of the
> >> network
> >> interfaces is connected to the other windows 2003 server node in the
> >> cluster
> >> via a crossover cable
> >>
> >> has anyone seen this before? bizzare!
> >>
> >> thanks guys!
>
>
>

did anyone fine a fix. I have the same problem.

"Chester Brown" wrote:

> I am experiencing a very similar scenario on a 2003 R2 server with SP2. This
> is in a small business environment and this is the only server. Interestingly
> it saves the information, if I run “ipconfig /all� it displays exactly what I
> entered but the settings page displays that the NIC is set for DHCP. The
> server is functioning with the address I assigned. Any solutions?
>
> "Phillip Windell" wrote:
>
> > I have heard of it happening a few times. But I don't know remeber the
> > solution so I didn't reply,...I was waiting to see what others might have to
> > say.
> >
> > --
> > Phillip Windell
> > www.wandtv.com
> >
> > The views expressed, are my own and not those of my employer, or Microsoft,
> > or anyone else associated with me, including my cats.
> > -----------------------------------------------------
> >
> > "Jammer" <(E-Mail Removed)> wrote in message
> > news:71E00E75-2A82-4B27-9028-(E-Mail Removed)...
> > > anybody?
> > >
> > > "Jammer" wrote:
> > >
> > >> hey averyone i have a node in a cluster that i am building, that normally
> > >> has
> > >> a static IP manually entered into its network connection, but the
> > >> damndest
> > >> thing started happening to it the other day, as soon as i enter the
> > >> static ip
> > >> and relevant information in and hit ok and close the network connection,
> > >> if i
> > >> go back into the connection it is set to gets its ip automatically via
> > >> dhcp!
> > >> and has wiped the static ip out, in the server subnet it resides in there
> > >> is
> > >> no DHCP either so it gets a 169. autoconfiguration address.
> > >>
> > >> i will note the following details, it is a windows 2003 enterprise
> > >> server,
> > >> dell 2950 with broadcom nic's i dont have any teaming going on or any
> > >> configuraiton assiged from the broadcom software(yet) and one of the
> > >> network
> > >> interfaces is connected to the other windows 2003 server node in the
> > >> cluster
> > >> via a crossover cable
> > >>
> > >> has anyone seen this before? bizzare!
> > >>
> > >> thanks guys!
> >
> >
> >

Has anyone got a solution to this??

I am also having the same problem; it may be connected to ISA 2004 being
removed from our 2003 R2 setup. We have 4 nics which all need to be setup
when ever there is a reboot. It is a real pain, especially as the server is
in a rack 50 miles from us!!!!.

MacPad,
Multiple NICs is only for teaming of RRAS. If you are not doing either of
those you will nee to disable the ones you are not using,
Anthony,
http://www.airdesk.co.uk

"MacPad" <(E-Mail Removed)> wrote in message
news:3DB96BFD-8655-4A4A-9746-(E-Mail Removed)...
> Has anyone got a solution to this??
>
> I am also having the same problem; it may be connected to ISA 2004 being
> removed from our 2003 R2 setup. We have 4 nics which all need to be setup
> when ever there is a reboot. It is a real pain, especially as the server
> is
> in a rack 50 miles from us!!!!.
>
>
>