When computers cannot join a business network, DHCP troubleshooting business network checks often reveal the cause. DHCP, or Dynamic Host Configuration Protocol, automatically gives devices an IP address, gateway, DNS servers, and lease period. If that process fails, users may see “no internet,” an unidentified network, or an address beginning with 169.254.
The visible symptom does not identify the fault by itself. A full DHCP scope, a wrong VLAN, a disconnected relay, or an unauthorized DHCP service can produce similar results. The safest approach compares a working device with a failing one, gathers evidence, and changes one thing at a time. Good DHCP troubleshooting business network work begins with that comparison rather than a quick restart.
Understand what DHCP must provide
A device normally discovers a DHCP server by broadcasting a request. The server offers an available address and related settings. The device then requests that offer, and the server confirms the lease. This exchange usually happens before the computer can use ordinary network services.
An IP address identifies the device on its local network. The subnet mask defines which addresses count as local. The default gateway forwards traffic to other networks, while DNS servers translate names such as websites into IP addresses. A faulty value can make the computer appear connected while applications still fail.
DHCP leases are temporary assignments. A lease has an expiration time, and the device normally renews it before that time. Lease records also help the server avoid assigning one address to multiple devices. Duplicate addresses can create confusing, intermittent failures.
Start with the failing device
First, record the exact symptom and time. Note whether one computer fails or an entire office, wireless network, or VLAN fails. Ask whether the device recently moved desks, changed from Wi-Fi to Ethernet, or received a network adapter update.
Next, inspect the device’s current network information. Windows ipconfig /all shows the address, subnet mask, gateway, DNS servers, DHCP server, and lease times. macOS users can review the active interface in Network settings. Linux users can run ip address and resolvectl status to show address and resolver details.
Do not treat every 169.254 address as proof of one specific failure. It usually means the device did not receive an IPv4 lease, but the reason could be physical, wireless, VLAN-related, or server-related. Compare the result with a nearby working device on the same network. This comparison is central to DHCP troubleshooting business network diagnosis.
- Check that the network adapter is enabled.
- Confirm the cable, switch port, or wireless connection.
- Compare the SSID, VLAN, and network location with a working device.
- Check the listed DHCP server address.
- Record the lease start and expiration times.
A renewal may help confirm the symptom, but it should not replace diagnosis. On Windows, ipconfig /release followed by ipconfig /renew requests a new lease. Use these commands only when you understand their effect, especially during an outage or on a remote session.
Check the DHCP scope and lease pool
A DHCP scope is the configured range of addresses available to a particular network. For example, a scope might serve one office subnet while another scope serves guest Wi-Fi. The scope also contains exclusions, reservations, gateway settings, DNS settings, and lease duration.
Open the DHCP management interface on the authorized server or network appliance. Confirm that the relevant scope is active and matches the subnet. Then review active leases, declined addresses, reservations, and the remaining pool. An exhausted scope cannot offer new addresses, even when the server itself is healthy. In DHCP troubleshooting business network investigations, pool capacity should be checked before deleting records.
Signs of an exhausted address pool
- Existing devices continue working, but new devices cannot connect.
- The problem affects one subnet more than others.
- The server shows little or no free address space.
- Temporary devices, phones, guests, or old equipment consume leases.
- Short outages appear after lease renewal times.
Before deleting leases, identify the devices using them. Removing an active lease can disconnect a user or create a duplicate assignment if another device still uses the address. Clean up stale records through the platform’s supported process, then confirm that the scope has enough capacity for normal growth.
Reservations deserve special care. A reservation ties a known device identifier, usually a MAC address, to a chosen IP address. A changed network adapter, docking station, or wireless interface can make a reservation stop matching. Verify the identifier and avoid relying on manually configured addresses unless the design requires them.
Look for a rogue DHCP service
A rogue DHCP service is an unauthorized device that answers address requests. It might be a consumer router, a misconfigured access point, a virtual machine, or an internet-sharing feature. It can provide the wrong gateway or DNS server, causing users to reach the wrong network or lose access to internal services.
Rogue services often affect users intermittently. DHCP uses broadcasts, so the first server response may win. Two devices connected to the same switch can therefore receive different gateways. This pattern strongly suggests multiple DHCP responders or a network segmentation problem.
Compare the DHCP server field on several affected and working devices. If they list different servers on the same segment, investigate before changing client settings. Network administrators can inspect switch forwarding information, DHCP snooping alerts, packet captures, or the device identified by the server address.
Do not simply unplug an unfamiliar device during a busy period. It could support another important service. Trace its switch port, identify its owner, and document the finding. Then disable DHCP on the unauthorized device or remove it through an approved change process.
Verify VLANs and DHCP relay settings
A VLAN is a logical network segment carried across switching equipment. Businesses often separate staff computers, phones, servers, cameras, and guest devices into different VLANs. Each routed VLAN usually needs a matching DHCP scope.
DHCP broadcasts normally stay inside their local VLAN. When the DHCP server sits on another network, a router, firewall, or Layer 3 switch must relay the request. The relay converts the local broadcast into traffic the server can reach and identifies the originating subnet.
For DHCP troubleshooting business network work, verify the following design points:
- The switch port has the intended access VLAN.
- Trunk links carry the required VLAN tags.
- The gateway interface for the VLAN is up.
- The DHCP relay points to the authorized server.
- Firewall rules allow relay traffic between the gateway and server.
- The server has a scope for the relay’s subnet.
A wrong access VLAN can place a computer in a subnet with no DHCP scope. A missing trunk tag can break an entire floor or wireless network. If only one VLAN fails, compare its gateway, relay, scope, and switch configuration with a working VLAN.
Check the DHCP server and network path
Once client, scope, and VLAN evidence points toward the server, check service health. Confirm that the DHCP service is running, the server has free disk space, and its network interface is connected to the correct network. Review DHCP event logs for rejected requests, authorization errors, database issues, or binding failures.
On a Linux-based DHCP server, service names and commands depend on the distribution and installed software. Avoid copying restart commands from an unrelated system. Use the platform’s documented service controls and preserve logs before restarting anything. The Google SRE troubleshooting guidance also emphasizes evidence, focused hypotheses, and controlled testing.
Check the path between the server and gateway. A firewall may block DHCP relay traffic, or an interface may have the wrong address. If the server serves several VLANs, one broken relay or rule can affect only one segment. For broader assistance, see the network troubleshooting service.
Packet capture can provide decisive evidence. A normal exchange shows a discover request, an offer, a request, and an acknowledgment. Missing offers point toward the server, relay, VLAN, or path. Offers from an unexpected server point toward a rogue service. Capture only with authorization because network traffic may contain sensitive information.
Use a safe recovery sequence
After identifying the likely cause, choose the smallest corrective change. Restore an exhausted scope, correct a relay target, remove an unauthorized DHCP responder, or repair the affected VLAN. Avoid changing gateway, DNS, lease duration, and firewall settings together. Multiple changes make verification difficult.
- Save the current configuration and relevant logs.
- Record affected subnets, devices, and DHCP server addresses.
- Make one approved change.
- Test a new client and a previously working client.
- Confirm internal resources, DNS, internet access, printers, and phones.
- Watch for renewed leases and repeat failures.
After recovery, document the final scope ranges, VLAN relationships, relay targets, reservations, and authorized DHCP servers. A current network documentation template can make the next investigation faster.
When to request assistance
DHCP incidents become harder when several VLANs fail, the server is remote, or an unknown device answers requests. Keep a record of affected users, timestamps, client addresses, DHCP server fields, and recent changes. That information gives a technician a useful starting point.
Tech Rescue Ops LLC can help with remote network troubleshooting when lease data, VLAN paths, DHCP services, or firewall rules need coordinated review. Professional assistance is especially appropriate before making changes that could disconnect an entire business.
Frequently asked questions
What does a 169.254 address mean?
It usually means the device did not receive an IPv4 DHCP lease. Check the adapter, VLAN, relay, DHCP server, and available address pool before assuming the server is down.
Can a full DHCP scope affect only new computers?
Yes. Existing devices may keep valid leases while new devices receive no address. Review active leases, stale records, reservations, and scope capacity.
How can I identify a rogue DHCP server?
Compare the DHCP server field on multiple clients. Different server addresses on the same segment justify an authorized switch, firewall, or packet-capture investigation.