DHCP failed to maintain the IP Address after expired

Hi Windows Experts,

I have some wierd problems on my DHCP server. So I have a dhcp client and this client was able to get a IP Address from my DHCP Server running under Windows 2008 R2.

Now I notice that, after the DHCP Lease got expired, my DHCP client was not able to re-negotiate or extend its least. I just noticed that it changed to a 169.X.X.X.

My DHCP Client is a Windows 7.

Does anyone encountered this before? Or is this a bug or known issue?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

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.

I believe the following hot-fix is what you need. It seems to be at the root of the problem you are having.
I've encountered that kind of problem,
I just find the exact driver for the lan and removed my previous lan driver and reinstall it with the one I downloaded,  I selected not the latest driver update.

I think its a lan driver issue
ImaCircularSawTechnical LeadCommented:
looks like the 169 address is one that it's given itself.  I usually see this in the case where there is a network cable unplugged or some sort of communication error between the client and DHCP server.

Can you check that you can ping the DHCP server from the client machine and that in 'ipconfig /all' the DHCP server shows up.

If you've not disabled it, it could be that the server is getting an IPv6 address.
Active Protection takes the fight to cryptojacking

While there were several headline-grabbing ransomware attacks during in 2017, another big threat started appearing at the same time that didn’t get the same coverage – illicit cryptomining.

Launch services.msc in client computer and make sure dhcp service is started.

SandManAuthor Commented:
Hi guys, my windows 7 was able to get an IP from my DHCP server so definitely the dhcp client service is running. And no issues on the cable as all are running under Vmware ESX
ImaCircularSawTechnical LeadCommented:
Sounds like DHCP is giving out an incorrect IP range.  Could you screenshort the results of a cmd > 'ipconfig /all' and also the network settings of your DNS & DHCP server?
It sounded to me like it just fails to get an IP when it's the situation where the lease expires due to time, it then fails and Windows takes on the default 169.xx.xx.xx address since it couldn't get one. If you disable and then turn around and enable the adapter does it get an IP then? if it does, and it's just an issue when the lease's expire then it's a strong possibility that you need the hotfix which addresses a known issue which is at the heart of Vista and Win 7 machines not being able to acquire/renew IP address through DHCP in that situation. The hotfix link is in my earlier post.

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
SandManAuthor Commented:
Hi Paul, let me try that and will get back to you.
SandManAuthor Commented:
Thanks, the issue is now resolved
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

From novice to tech pro — start learning today.