Windows 10: Windows 10 Pro - DHCP not working, getting APIPA

I am using Windows 10 Pro, I had no issues getting an IP address from my DHCP server, but now the server is unreachable after I simply moved the machine to a different switch port.


I have tried re-connecting to the old switch port, but I get the same symptoms still. Using DHCP for my Ethernet adapter, the interface quickly changes between receiving an APIPA address, and then no address. Looking in the Adapters dialog, it shows the port goes from Not Connected, to Unidentified Network, and back and forth.


I have tried the netsh tcp stack reset, and I am unable to execute ipconfig /release or /renew, as it either does not see the media connected, or it says it does not have an IP address assigned.


Even if I use a static IP in the same subnet as the router, I cannot ping it. Not sure whats wrong here.

:)

 

Windows 10 Ethernet gets a valid DHCP Adress but does not communicate afterwards

Hello Don,

I think the Problem is your router. Windows gets the DHCP-Information about the router. It creates an APIPA, if it gets no Information from router. Please check the DHCP-Setting for the LAN-Ports.

Regards Michael

 

Windows 10 Ethernet gets a valid DHCP Adress but does not communicate afterwards

Hello Michael,

Thanks for your response.

The DHCP settings for the LAN is working, since the computer gets a valid adress from the pool with a correct lease in the first place. Just afterwards it stops communicating.

Correct me if I'm wrong but I think the normal APIPA is like 169.254.x.x and the laptop gets an adress like 192.168.0.x from the router. I can verify that he gets the DHCP adress on exact that time he is first connected to the router because the starting
lease time is exact the time he is connected.

I can also see the computer in the routers list of DHCP clients.

Best Regards,

Don

 

W10 - losing ip connection to ISP, drops DHCP and defaults to APIPA IP address

DHCP and DNS clients are set to automatic and are running, but after a shutdown and restart there is no internet connection and a APIPA default IP address is given. The IPv4 has to be set from Auto to manual and the DHCP server addr input. Then after running
the network trouble twice and having it 'fix' DHCP, the internet is usually accessible again. Using ATT uverse router and if it is deleted to remake, Networking & Sharing's Make a New Network Connection does not see the ATT router. It is a wired connection,
not using wireless. Mcafee firewall was turned off to troubleshoot but this did not make a difference. HP P2 computer originally on W8.1, upgraded the network card driver but there is not a W10 version available.

Everything was working perfect until sometime in early December 2016 and hasn't working since. No additions except windows and Mcafee updates.