I'm having a frustrating issue with DHCP at the office. One of our clients reported that DHCP isn't working for them, and when I went onsite to check, I ran into the same problem. However, everyone else in the office can connect just fine. The DHCP server is running on a 2019 server, and I've gone through the logs without finding any clues. I even tried moving the DHCP service to a Fortinet device, but the problem persists. It's just this one client and me who can't connect. I've plugged directly into the switch and the firewall, but no luck. Any ideas on what could be causing this?
5 Answers
You've confirmed that other devices are configured to use DHCP and aren't assigned static IPs, right? If everything else can connect fine, it might be a cabling or switch port issue causing this odd behavior.
Make sure you’re not out of IP addresses! Sometimes, it’s as simple as that. Though you mentioned it seems unlikely, it's worth verifying!
I’d suggest using Wireshark to diagnose this. I'm guessing something might be blocking the broadcast from reaching the DHCP server. You mentioned you moved it to Fortinet; there might be a filter that's still affecting it. Have you checked to see if requests are hitting the server?
It sounds like "not working" might be too vague. Are you able to check if those clients are getting an IP assigned? If they're getting something like 169.x.x.x, then they’re not connecting properly. Also, double-check whether the client is on the same subnet as the DHCP server. If not, make sure you have boots-relay options configured. A bit more detail would definitely help!
Don't forget to check for any DHCP snooping configurations on your switches—they can cause issues. Also, running a packet capture would really help you to see the traffic flow.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures