Avatar of AriesUpNorth
AriesUpNorth
Flag for United States of America asked on

DHCP Not Acquiring Address after Windows 8 Upgrade

I have a client who completed (without my awareness) an upgrade to Windows 8 on a Dell Inspiron.  Since that time, the computer will not pick up a DHCP address from her ATT U-Verse Modem/Router on either the wired or wireless connections.

Here's a recap.

If I set a static IP on the wired and wireless connections within the router's scope, the connections work fine.

If I use another system with DHCP, it gets an address from the router (both wired and wireless) via DHCP without issues (so that rules out the router as I see it).

I have tried DHCP without IPV6...had to try something!  And same result.

When connections are set to DHCP, all the settings seem correct, but it ends up with the 169.x.x.x. address.

...I must be missing something.

While I didn't do the upgrade, the client states the issue began after that change to Windows 8.  Tried a few searches on the issue to no avail.

I could leave it as is, but she does travel with the laptop and leaving her set up as static will cause the obvious issues for a low-level user.  besides...it's supposed to work! ;)

I have not yet been able to do any Dell Driver Updates...have that planned for later today.

Thanks in advance for any advice.

-Kurt
Windows NetworkingDHCPDell

Avatar of undefined
Last Comment
AriesUpNorth

8/22/2022 - Mon
SOLUTION
Patrick Bogers

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
SOLUTION
andrew1812

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
ASKER CERTIFIED SOLUTION
Darr247

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
⚡ FREE TRIAL OFFER
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.
SOLUTION
vivigatt

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
⚡ FREE TRIAL OFFER
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.
AriesUpNorth

ASKER
Sorry for the delay in responding to all the helpful advice!  My client was unavailable for the last two weeks.  I will be trying these suggestions and updating the results before the end of the month.
AriesUpNorth

ASKER
Thanks to all who shared ideas!  I decided to spread the points across all responses as they were all similar and valuable...and I tried them all except the Wireshark suggestion.  In the end, it appears that the systems's firewall was somehow altered in the migration to Windows 8.  Once that was rebuilt, normal DHCP functions were restored.   Thanks again for the help!
I started with Experts Exchange in 2004 and it's been a mainstay of my professional computing life since. It helped me launch a career as a programmer / Oracle data analyst
William Peck