Hello IT, Have you tried turning if off and back on again?
That reminds me of a story...
From Whirlwind Computing - a fictional service provider so good it will really blow your socks off
The company affected is one we can regiomize is a care-home of sorts...
Actors:
$Me - Calling the shots... remotely
$Nerds - My minions... experts in their craft
$Phone - Calling the shots... onsite
$Director - Also calling the shots... onsite
Scene:
This place started bubbling up to the top of the support queue with multiple requests of something is just really off with the network with reports of it being slow, dragging, and just being an absolute dog when it comes to being on wifi.
That's weird because wifi coverage was very good as the wire-flavoured spark wranglers made sure it passed muster and the mustard.
We sent techs multiple times to bless the creaking network and also to make an assuring presence that nothing was being a problem.
Murphy clearly had other plans as we were wrong about what was wrong the first four times they went out.
The Director got involved and told the reps to fix the network or he's replacing everything as it's impeding actual business operations and making the whole team very hot, cross, and bothered.
I grabbed the laptop and camped out staring at the all-knowing Shark of the Wires, filtering by Arp, Dns (always DNS) then Dhcp... wait a second!
Why is 192.168.4.27 sending out DHCP ACKS to DHCP requests?
I took a closer look at the Mac address which showed it was a phone, but why on earth would it be doing the DHCP thing?
I assembled the Nerd Herd^(TM) and they swept the building with the precision of a highly trained black-ops team as there were 20 of them to check, so I give them full credit for finding it within 7 minutes.
One reboot later and things started to swim back into service while the phone was off-hook and strangely, it hasn't been a problem ever since.
We have well 1500 phones deployed, this is the first and hopefully last time one of them became the embodiment of DHCP with a flair for the dramatic.
The lesson here is that if there's ever an event for what feels like a rogue DHCP server, check the phones, you never know what you might find.
PS:
If it helps, I did remember the lessons from previous stories of various laptop docks randomly becoming port mirrors and how they wreaked havoc on the network, so we covered both in that sweep.