Windows 10: Windows can not process properly DHCP response with the same IP for wired and wireless...

DHCP servers may return the same IP for both wired and wireless connectionThis may be useful for laptops - I can connect with wire in the main room and wireless on the other.But when I plug the ethernet cable to the laptop and turn off wifi, Windows still not able to obtain IP from DHCP serverI have found 2 workarounds:1. Reboot boring2. Open the window with network adapters and disable wifi adapter. In this case wired connection can obtain IP, and the connection to network restoring I prefer not to do such extra steps as it is boring.Microsoft, please release IP from wireless adapter if wif

:)

 

Static IP With Windows 10 and HP Zbook

Thanks for the suggestion but I'm not connecting to a router. I'm hard wired to a modem device that does not have DHCP so I need a static ip to set my IP address to the correct subnet. It works on another machine doing the exact same steps.

In my question I already checked ipconfig and it shows the correct ip/netmask on the dell machine that works and the HP that does not.

 

Ethernet doesnt have a valid IP

DHCP STATIC was suggested here: Ethernet doesnt have a valid IP

I asked why and never got a response *Confused

 

DHCP client error 0x79 on wireless only

The event viewer shows a consistent response of

Your computer was not assigned an address from the network (by the DHCP Server) for the Network Card with network address [elided]. The following error occurred: 0x79. Your computer will continue to try and obtain an address on its own from the network
address (DHCP) server.

I can see the DHCP response on the wireless access points, so I know it issues an address. All the hardware on the laptop has been replaced, with the wireless daughter board undergoing multiple replacements. The BIOS is up to date. The drivers are up
to date. I've used sfc and DISM to validate the Windows installation multiple times. IPv6 support is off because it's not in play.

This happens even when I try using a USB wireless adapter. In all cases Windows can see the available wireless networks--it just insists that there is no response to its DHCP request.

On a wired connection, it gets an address just fine--and in the case of my home network, from the same device which it claims isn't sending back an address. The laptop is the only wireless device that doesn't get an address properly--so I don't think it's
the router/access point. During the duration of this condition, the router was replaced for a different reason, and having two different routers from two manufacturers exhibit a defect versus the laptop
only defies probability. It also happens on multiple wireless networks, including the three available in my workplace.

So, the problem must be in the bits somewhere--but which bits? Where should I be looking for a timing or other configuration that might address why Windows insists that it's not receiving an IP address via wi-fi? I'll like to avoid a wipe and reinstall
because of the downtime involved. I've been all over the web with search engines looking for an answer, but everything I've found addresses a general DHCP failure, not one specific to wi-fi.

The situation has persisted since March of 2017 and I've given up trying to solve it myself. Someone with more knowledge of Windows networking internals might have some insight, though--so, if you're one of those individuals, what do you think?

Thanks,

--jbm!