0

I have a customer who has a Dell Server running Win 2003 R2 Server. This is an existing machine that we had setup with a static IP. Now they want to change it to another static IP.

When they go and change it, hit ok, then reboot. The config is back to the old IP #.

The user is the administrator.

My guess is it has to do with AD & GP, a virus, an already in use IP#, or something else?

Anyone have any ideas what else could cause this behavior?

MDMarra
  • 100,183
  • 32
  • 195
  • 326
shaiss
  • 337
  • 2
  • 6
  • 20

3 Answers3

1

I had a similar problem on a Dell PowerEdge 1950 with Broadcom NIC's installed. Running "netsh reset int ip" from a command line fixed it.

joeqwerty
  • 108,377
  • 6
  • 80
  • 171
0

Does it work after changing the IP, before rebooting? Rebooting is not required to change an IP address.

Is there any anti-virus or security software that may be overzealous in protecting network settings?

DrStalker
  • 6,676
  • 24
  • 76
  • 106
0

Broadcom NICs? Its a known issue. I can't remember the solution exactly, but if you call Dell support, they should be able to help you in a few minutes.

Basically this is due to a package not installed properly during Dell automated install (or maybe vice versa - you HAVE to use the OMSA CD to install the OS)

Just call support - it's a well documented issue, easy to solve

dyasny
  • 18,482
  • 6
  • 48
  • 63
  • still looking in to this. Our user is going through upgrading their nics. We'll see if that helps at all, then I'll mark this as answered. Thank you – shaiss Sep 16 '09 at 20:44
  • This is why we don't use the broadcom NICs, we always get Intel NIC cards to save us any trouble. – Hondalex Nov 02 '09 at 17:04
  • Hondalex, b-coms are OK when you know their quirks, and this issue has been around for years now - there's an easy and well documented solution available, only one support call to Dell away – dyasny Nov 03 '09 at 10:21