Firewall Support Center

DHCP Works in One VLAN but Fails in Another: Relay Troubleshooting

Follow DHCP Discover, Offer, Request, and ACK across a relay to diagnose a VLAN that cannot obtain an address.

Client VLANBroadcast Discover reaches the gateway
DHCP relayForwarded request identifies the client subnet
DHCP serverMatching scope and reply path must exist
Illustrative troubleshooting view · Firewall Support Center

Use the working VLAN as a comparison

When one VLAN obtains leases and another does not, compare the paths and server scopes for those two VLANs. The working segment confirms that part of the infrastructure operates, but its relay interface, scope, policy, and return route can differ. Record those differences before changing the server.

Understand where the relay operates

A client initially broadcasts on its local VLAN. A DHCP relay forwards requests toward a server on another subnet and provides information the server uses to select the client network. In Cisco IOS-style configuration, ip helper-address belongs on the client-facing Layer 3 interface. A remote switch access port alone cannot establish that relay function.

Inspect the Windows client

ipconfig /all
ipconfig /renew

Capture one renewal attempt

Use the affected client and record the test time and MAC address. Observe whether Discover leaves the client, whether it reaches the relay, whether the server sends an Offer, and whether Request and ACK complete. A link-local address is a symptom of missing address configuration. It does not identify which DHCP stage failed.

Review the gateway configuration

show running-config interface Vlan20
show ip interface brief
show ip route 10.50.0.10
show ip dhcp snooping

Configuration example to compare with your design

interface Vlan20
 ip address 10.20.0.1 255.255.255.0
 ip helper-address 10.50.0.10

Interpret the relay example

This illustrates a Catalyst or IOS-style SVI for client subnet 10.20.0.0/24 and DHCP server 10.50.0.10. Compare it with the real gateway rather than applying it to an unrelated device. Confirm the SVI is operational, the helper points to the intended server, and the server can return traffic to the relay. VRFs and source-interface selections require additional platform-specific checks.

Check the scope and server decision

Verify an active scope for the failing subnet, available addresses, exclusions, reservations, and any policy that filters requests. Examine the relay address and Option 82 information in the actual request. Compare it with the working VLAN. A request reaching the server without an Offer calls for server-side investigation before a trunk change.

Locate the first missing message

EvidenceInvestigation
Discover absent at relayClient port, VLAN continuity, authentication, and Layer 2 controls
Forwarded request absent at serverHelper, routing, VRF, ACL, and firewall path
Server receives request but sends no OfferScope availability, server logs, and policy
Offer leaves server but client never sees itReturn route, relay delivery, and DHCP snooping
Lease works but application failsGateway, DNS, lease options, and downstream connectivity

Validate a complete lease

After the repair, confirm the address, mask, gateway, DNS servers, and lease duration on a test client. Verify the server lease record and a complete transaction in the capture. Test a new client as well as renewal of an existing lease when practical. Keep DHCP changes scoped to the failing path and preserve the previous configuration.

Official references

Cisco DHCP relay agent configuration

Cisco IOS XE relay agent reference