windows 2003 servers losing static IP addresses

I have 4 Windows 2003 standard servers, all Dell PowerEdges with
different NICs. 1 is a W2K server upgrade, but the others are new or
OEM installs.
I never reboot the upgraded server, but the others I rebbot
occasionally for maintenance, updates, etc. When I reboot these servers
they lose their static IP addresses. I don't have this problem with any
of my W2K servers.
Has anyone had this problem with W2003? If installed the "fixed" TCP/IP
patch MS05-019.
I would even take a bandaid to the problem if there's a way to script
the static IP upon startup, i.e. with a netsh command.

Thanks in advance.

After they have "lost" their static IP, what IP shows up on an IPCONFIG
/ALL?

-Frank

<(E-Mail Removed)> wrote in message
news:(E-Mail Removed) oups.com...
>I have 4 Windows 2003 standard servers, all Dell PowerEdges with
> different NICs. 1 is a W2K server upgrade, but the others are new or
> OEM installs.
> I never reboot the upgraded server, but the others I rebbot
> occasionally for maintenance, updates, etc. When I reboot these servers
> they lose their static IP addresses. I don't have this problem with any
> of my W2K servers.
> Has anyone had this problem with W2003? If installed the "fixed" TCP/IP
> patch MS05-019.
> I would even take a bandaid to the problem if there's a way to script
> the static IP upon startup, i.e. with a netsh command.
>
> Thanks in advance.
>

The NICs have received an address through DHCP from the DHCP server,
and the properties of TCP/IP on the NIC have moved the radio button
choice from "Use the following address" to "Obtain an IP address
automatically." The DNS server settings remain as I've set them.
Thanks.

Here's what comes up on ipconfig /all, if it adds anything to the
conversation.

Windows IP Configuration



Host Name . . . . . . . . . . . . : mail01

Primary Dns Suffix . . . . . . . : (removed for posting)

Node Type . . . . . . . . . . . . : Unknown

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : (removed for posting)



Ethernet adapter Local Area Connection:



Connection-specific DNS Suffix . : (removed for posting)

Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit
Ethernet #2

Physical Address. . . . . . . . . : 00-0F-1F-66-2B-E0

DHCP Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.1.173

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.1.254

DHCP Server . . . . . . . . . . . : 192.168.1.254

DNS Servers . . . . . . . . . . . : 192.168.1.10

192.168.1.8

Lease Obtained. . . . . . . . . . : Tuesday, November 29, 2005
2:37:21 PM

Lease Expires . . . . . . . . . . : Wednesday, November 30, 2005
12:37:21 AM



Ethernet adapter Local Area Connection 2:



Media State . . . . . . . . . . . : Media disconnected

Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit
Ethernet

Physical Address. . . . . . . . . : 00-0F-1F-66-2B-E1

..

Well, I just wanted to see if you were getting an "autoconfigured" IP or a
true DHCP assigned IP. It's true. Any chance when you logon you are getting
the static IP config changed by a group or local policy? Sorry, I can't
think of anything else.

-Frank

<(E-Mail Removed)> wrote in message
news:(E-Mail Removed) oups.com...
> Here's what comes up on ipconfig /all, if it adds anything to the
> conversation.
>
> Windows IP Configuration
>
>
>
> Host Name . . . . . . . . . . . . : mail01
>
> Primary Dns Suffix . . . . . . . : (removed for posting)
>
> Node Type . . . . . . . . . . . . : Unknown
>
> IP Routing Enabled. . . . . . . . : No
>
> WINS Proxy Enabled. . . . . . . . : No
>
> DNS Suffix Search List. . . . . . : (removed for posting)
>
>
>
> Ethernet adapter Local Area Connection:
>
>
>
> Connection-specific DNS Suffix . : (removed for posting)
>
> Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit
> Ethernet #2
>
> Physical Address. . . . . . . . . : 00-0F-1F-66-2B-E0
>
> DHCP Enabled. . . . . . . . . . . : Yes
>
> Autoconfiguration Enabled . . . . : Yes
>
> IP Address. . . . . . . . . . . . : 192.168.1.173
>
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>
> Default Gateway . . . . . . . . . : 192.168.1.254
>
> DHCP Server . . . . . . . . . . . : 192.168.1.254
>
> DNS Servers . . . . . . . . . . . : 192.168.1.10
>
> 192.168.1.8
>
> Lease Obtained. . . . . . . . . . : Tuesday, November 29, 2005
> 2:37:21 PM
>
> Lease Expires . . . . . . . . . . : Wednesday, November 30, 2005
> 12:37:21 AM
>
>
>
> Ethernet adapter Local Area Connection 2:
>
>
>
> Media State . . . . . . . . . . . : Media disconnected
>
> Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit
> Ethernet
>
> Physical Address. . . . . . . . . : 00-0F-1F-66-2B-E1
>
> .
>

Frank,
You were right. There was a policy to set all computers to DHCP with a
startup script. A tech had put it on the servers in July when we added
a new DNS server. He had forgotten to exclude the servers from that
policy. All the other servers are Citrix servers which are in a
different group so they weren't affected so I didn't realize at first
where to look.

Thanks for your help.