Symptom is as follow: the first laptop send a DHCP renew, which is accepted by the management key, but declined by the PC.
DHCP server is a Ubiquity Network management key, and periodically receive a tempest of DHCP request from two Win 10 pro laptops, both up-to-date, both My SOHO network is configured with static DHCP leases, for a 24h duration. I've updated the wireless drivers on the laptop's NIC (which were out of date), but this hasn't made any difference. To confuse matters, it isn't even able to pick up an IP Address if it's connected back to the original wireless network on the ISP's router. If the laptop is rebooted, it picks up an IP Address without any problems at all, but seems completely unable to renew an existing lease. I've resolved this now, and it's giving out 8 hour leasesĪgain, but the laptop still gets the issue at the end of the 8 hours. The DHCP server was only giving out 1 hour leases as it had DHCP failover clustering configured on it, and the second node was down. Initially, the laptop would lose connection every hour. I've tried various iterations of turning the wireless adapter off andīack on, and ipconfig /release and ipconfig /renew without luck. There are other Windows 10 clients connected wired and wirelessly on the workstation subnet. (servers all use DHCP and have static reservations configured on the DHCP server). This works perfectly well for everything else on both subnets The default gateway on the workstations subnet (where the wireless network is) has a DHCP IP Helper configured (using RRAS), and forwards the request to my servers' subnet which is 1 hop away. That ever since, the laptop really struggles to renew it's IP lease from the DHCP server. However, I recently moved it to a different Wireless Network inside my firewall, and joined it to my domain. Until recently, the laptop connected wirelessly directly to the router provided by my ISP, and didn't have issues. I have a Windows 10 laptop, which has developed an odd DHCP fault I've not seen before.
0 kommentar(er)
