DHCP shows for Static IP in Network properties

I inherited a Dell Poweredge T620 server with an odd problem. There are several symptoms:
- If I configure a static IP address in the Network properties dialog, exit and go back in, "acquire" (DHCP) is selected. The static IP appears to stick, however.
- Strangely enough, if I enter a different static IP and, then go to status, all previously configured IPs show along with the current one (see picture).
- Even more bizarre, I can ping the previously configured IP addresses, even if I had them entered as a momentary test (like 172.16.22.4).
- DHCP service is not servicing requests, though it appears to be working properly OK.


Here are the details:
I needed to change the server's Ip address, from 192.168.1.2. I did that, reconfigured the DHCP scope, DNS zone. It was at the end of this process that DNS worked, but DHCP didn't. I ended up removing the DHCP role, then readded. I did get an error message that the authorization of the DHCP server failed with error 20079 (the specified servers are already present). BUT, I can go and deauthorize, then authorize the server just fine, and no further such error messages are being logged. In fact, when I reboot, the log states that the DHCP server is servicing requests (it is NOT). For now, I'm using the router as a DHCP server.

On the attached image, you'll see the Intel Gigabit network adapter, and 3 IP addresses (some masks), of which only 172.16.22.3 is current and legitimate. Yes, I can ping all of them on the server.

Any thoughts?
IMG-8118.jpg
LVL 1
btm02sfAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Lahiru NanayakkaraManager - Technical Services Commented:
Try this command,

netsh int ip reset c:\ipresetlog.txt

This will rewrite registry values of TCP/IP / DHCP Parameters
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
btm02sfAuthor Commented:
Thank you - will try this Friday and I'll let you know.
0
btm02sfAuthor Commented:
That didn't really work. After restarting, the server didn't have any IP address (169....) and though the properties page was set to automatically acquire, that didn't happen.

I set the IP manually, but at least one of the symptoms is persisting: if I close all dialogs and go back in, it doesn't show the IP as set to "static", but rather still "dynamic". At this point rebooting the system is OK, the pseudo-static IP remains when I log back in.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
DHCP

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.