Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 443
  • Last Modified:

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
0
AriesUpNorth
Asked:
AriesUpNorth
4 Solutions
 
Patrick BogersDatacenter platform engineer LindowsCommented:
Hi,


Try to reset Winsock and reinstall network drivers as described here.

If the issue persist, try giving System account and Administrator acount full control on hive HKLM\System\CurrentControlSet\Services\Dhcp


Hope that helps.
0
 
andrew1812Commented:
Check with a tool like wireshark, to see if the DHCP Discover packets are being triggered from the client system (Windows 8). Also check if the DHCP client service is started on the system.
0
 
Darr247Commented:
Try uninstalling one of the adapters in Device Manager, then refresh hardware there and see if the freshly reinstalled adapter picks up an IP from DHCP... if so, repeat the uninstalll/refresh with the other adapter.

If that doesn't help, try resetting the TCP stacks.
To reset the TCP stacks open an Administrator Command window and run
netsh int ipv4 reset %homepath%\resetipv4.txt
netsh int ipv6 reset %homepath%\resetipv6.txt
(even with an administrator window those commands might give an access denied message in Win8.x, but after rebooting, the IPv4 and IPv6 TCP stacks will have been reset... you'll find the resetipv#.txt logs specified in the C:\Users\[username]\ folder of the current user).
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
vivigattCommented:
Check the status of DHCP client (event log etc.... check that the DHCP Client service is running).
0
 
AriesUpNorthAuthor Commented:
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.
0
 
AriesUpNorthAuthor Commented:
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!
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now