There could be some low-possibility scenarios where the client did not renew. Maybe the DHCP client service was stopped (or crashed) so it did not renew. Maybe the DHCP server's usable IP addresses have all be used, and another client grabbed the IP before the original client got a chance to renew. If a lot of leases were issued at the same time (i.e. cluster startup), maybe the server was flooded with renewals and dropped some.
There are a lot of other even-less-likely things: the client being in the process of shutting down, network interface turns off, etc.
In this case, we believe the network interface was being turned off. Still not completely sure, but we should see in a couple of days. Bless the patience of the campus networking guy.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
There could be some low-possibility scenarios where the client did not renew. Maybe the DHCP client service was stopped (or crashed) so it did not renew. Maybe the DHCP server's usable IP addresses have all be used, and another client grabbed the IP before the original client got a chance to renew. If a lot of leases were issued at the same time (i.e. cluster startup), maybe the server was flooded with renewals and dropped some.
There are a lot of other even-less-likely things: the client being in the process of shutting down, network interface turns off, etc.
In this case, we believe the network interface was being turned off. Still not completely sure, but we should see in a couple of days. Bless the patience of the campus networking guy.