Windows 10: DHCP client doesnt make a new DHCPREQUEST within lease time

HiI have some routers with a short DHCP lease time of 15 to 30seconds which is valid according to RFC2131.With most of my previous laptops this has not been an issue, but now I'm trying out some new Dell Latitudes where the network connection is lost multiple times within just a 10 minute test. The network adapter is still visible to the system, it is just the connection that drops. From the trace we see that the DHCP client just fails to send a new DHCPREQUEST within the leasetime and then it tears down the connection and initialises DHCP DORA again.Laptop modelNIC DeviceIDNIC NameLatitude

:)

 

windows 10 dhcp client never issues dhcprequest in response to dhcpoffer

i have around 100 local devices. only one windows 10 client is having a dhcp problem. wire shark shows dhcpdiscover followed by dhcpoffer...but the client never responds with dhcprequest. i have disabled the firewall, disabled malwarebytes, reset the stack,
rebooted... obviously dhcp client is running as it does issue the dhcpdiscover. dhcp server is isc dhcpd running on linux. there are no dhcp errors logged in the system event viewer. the system date/time is correct. the ipv4/ipv6 adapter settings are both
set to acquire the ip address automatically. the dhcp lease time is 86400 seconds or one day. the weird thing is, it does get an ip address at system boot, which has the correct lease obtained and expires times. however the system keeps issuing dhcpdiscover
and when the lease it up, fails to renew the ip address.

 

DHCP lease time

Read this
DHCP lease time: What it is, how it works, and how to change it

 

DHCP lease time

If there is an active connection to the router then the lease time should be irrelevant.

The lease only comes into effect when the device stops transferring data to or from the Router, once this occurs the Clock Starts and when the lease time is reached the allocated DHCP address for the device is returned to the pool for reuse.

Basically if you have a long lease set then the likelihood of a particular device getting the same address every time is increased, if the lease time is short then this is less likely but you will have moore addresses in the available pool.

DHCP leases are important in locations where many devices connect to the network through the router such as business premises, or coffee shops, they are less important in a home situation and so leaving at default is just as good as any other lease time.

It should not affect gaming servers and other services outside of the home network as the IP address and lease for the home address is set by your ISP and they also set the DHCP lease, if you need to keep the same IP address seen on the net most ISPs will, for a charge, assign you a fixed Address

The internal address lease on your local network, can effect the availability of fixed items :- Printers, NAS servers, to the network but this should only be an issue if you only use direct IP access to access these devices, Windows naming conventions will be automatically updated by the Router so should work without issue