> ## Content Index
> Fetch the complete content index at: https://routerhaven.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# tcp port dhcp: what it really uses and why rules fail
- URL: https://routerhaven.com/tcp-port-dhcp/
- Published: 2026-11-21T02:00:00.000Z
- Updated: 2026-11-21T02:00:00.000Z
- Author: Caleb Renwick
- Tags: Networking

DHCP does not use a TCP port at all; it uses UDP. For standard IPv4 DHCP, the client and server typically communicate on UDP ports 68 and 67\. If you were looking for a “TCP port for DHCP,” there isn’t one for the normal IPv4 lease process. When a device won’t get an address, the problem is usually a blocked UDP path, a broadcast issue, a missing relay, or a VLAN setup that keeps the client from reaching the server.

## Does DHCP use a TCP port at all?

No. Standard DHCP for IPv4 uses UDP, not TCP. The common ports are UDP 67 for the server side and UDP 68 for the client side, so a client asks for an address from port 68 and the server answers from port 67.

For example, a laptop sends a broadcast DHCP request over UDP, and the server replies with an offer and then a lease. There is no TCP session to open, no handshake to wait for, and no TCP port to permit for the basic exchange.

This also helps explain the boundaries: this answer applies to normal IPv4 DHCP. It does not cover every DHCP-related [feature in every network](https://routerhaven.com/firewall-configuration/), and it does not mean all address assignment on every platform works the same way.

## Why people keep looking for a TCP port for DHCP

This confusion usually comes from firewall or packet-filter rules. Many network services use TCP, so it’s natural to search for a “TCP port” [when a device cannot](https://routerhaven.com/static-ip/) reach a server. DHCP is different because it starts with broadcast UDP traffic, which some filters treat differently or block outright.

Another common source of confusion is troubleshooting by symptoms. If a printer, access point, or IoT device shows “no IP address,” people often assume a port rule is wrong. In reality, the issue may be that the device’s broadcast never made it to the right VLAN, or the reply never got back to it.

For example, if your router allows TCP traffic between subnets but blocks UDP broadcast forwarding, DHCP will fail even though the network looks open on paper. That is why the search for a TCP port is so common: the failure looks like a port problem, but the protocol flow is usually the real issue.

## Which ports DHCP actually uses

For IPv4 DHCP, the usual ports are:

- Client: UDP 68
- Server: UDP 67

The server listens on UDP 67 for DHCP requests. The client listens on UDP 68 for replies and related client-side traffic. In normal use, you want the server reachable on UDP 67 and you want client traffic on UDP 68 to be allowed where the exchange crosses devices or security boundaries.

The key detail is direction. A firewall rule that only allows inbound traffic to the server is not enough if return traffic, broadcasts, or relay traffic is blocked. DHCP depends on the full exchange, not just one port number in one direction.

Say you have a DHCP server on one subnet and clients on another. The server must receive the request, the relay must pass it, and the reply must get back to the client’s segment. If any part of that UDP path is blocked, the lease fails.

## What to allow in a firewall or router rule

What you need to allow depends on where the DHCP server sits and whether a relay is involved, but the core rule is simple: permit UDP 67 and UDP 68 along the path the DHCP packets actually take.

If the server and clients are on the same local subnet, make sure local broadcast DHCP is allowed and that any host firewall on the server permits UDP 67\. If clients are across subnets, allow the relay agent to forward DHCP traffic to the server and allow the server’s replies back to the relay and client network.

A practical rule set usually looks like this:

- Allow UDP 67 to the DHCP server.
- Allow UDP 68 from clients where the client system firewall is involved.
- Allow DHCP relay traffic between VLANs and the server.
- Make sure broadcast traffic is not suppressed on the client segment.

If you manage a router, switch, or firewall, check for DHCP helper or relay settings as well. Open ports alone do not fix a missing relay configuration.

If DHCP is broken in a VLAN design, the place to look is often the device doing the inter-VLAN routing. That is where you decide whether broadcasts stay local, whether a relay forwards them, and whether the server’s reply can return to the right segment.

![A network router sits next to a laptop with Ethernet connected.](https://tse1.mm.bing.net/th?q=network%20router%20connected%20to%20laptop%20photo&w=624&h=352&c=7)

## Why DHCP can still fail even when the ports are open

Open ports are only part of the story. DHCP often fails because the request or reply never reaches the right network segment.

Broadcast blocking is a common one. A new client usually starts with a broadcast because it does not yet know the server’s address. If a router, VLAN boundary, or security policy blocks broadcasts, the client may never see the offer.

Relay problems are another frequent cause. When DHCP crosses subnets, a relay agent has to forward the client’s request to the server and send the response back. If the relay is missing, pointed at the wrong server, or tied to the wrong interface, the client will not get a lease.

Managed networks can add more layers. Some switches or Wi-Fi controllers filter unknown broadcasts. Some endpoint security tools block DHCP on the host. Some guest networks isolate clients in a way that stops local discovery traffic. In those cases, the port numbers are correct, but the path is not.

If you have a packet capture, you should see the client’s broadcast leave the device, the server’s offer come back, and then the request/ack pair complete. If one of those steps is missing, that tells you where the break is.

![A network router is mounted in an office hallway near network cabling.](https://tse1.mm.bing.net/th?q=network%20router%20in%20office%20hallway%20photo&w=624&h=352&c=7)

## What changes with DHCPv6

DHCPv6 is different from IPv4 DHCP, and that is where some of the port confusion comes from. DHCPv6 uses UDP too, but it does not use the same port pair as IPv4 DHCP.

The main point for troubleshooting is that IPv6 addressing may involve router advertisements, SLAAC, DHCPv6, or a mix of those methods. So if an IPv6 host is not getting the address information you expect, the fix may not be “open the DHCP port” in the same way you would for IPv4.

If you are working in an IPv6 network, check whether the client is meant to use DHCPv6 at all, whether the router is advertising the right flags, and whether the network is set up for stateful or stateless behavior. The rules and packet flow are similar in spirit to IPv4, but the details are not identical.

## Quick check if your device still won’t get an address

Start with the shortest path to the answer:

1. Confirm the client is set to obtain an address automatically.
2. Test with one known-good client on the same port or Wi-Fi SSID.
3. Check the DHCP server logs for a Discover, Offer, Request, and Acknowledge.
4. Verify the client VLAN matches the DHCP scope or relay configuration.
5. Check whether a relay agent or helper address is configured on the router or switch.
6. Look for local firewall or security software on the client or server that could block UDP 67 or 68.

If the server never sees a Discover, the problem is usually upstream of the server. If the server sees the request but the client never gets an Offer, focus on the return path, relay, or broadcast handling. That tells you where to fix the network instead of guessing at a TCP port that DHCP does not use.

![A person troubleshoots a network router while looking at a laptop.](https://tse1.mm.bing.net/th?q=network%20router%20and%20laptop%20troubleshooting%20photo&w=624&h=352&c=7)

## Conclusion

If you are opening firewall rules for DHCP, think UDP, not TCP. For standard IPv4 DHCP, the main ports are UDP 67 and 68, and the bigger failure points are often broadcasts, relay settings, and VLAN boundaries. If you are still stuck, trace one lease attempt from client to server and back; that usually shows exactly where the path breaks.

## Frequently Asked Questions

### Is there any TCP port for DHCP?

Not for normal IPv4 DHCP. The standard protocol uses UDP, not TCP.

### Which UDP ports should I allow for DHCP?

Usually UDP 67 for the server and UDP 68 for the client, plus any relay path between subnets.

### Why does DHCP work on one VLAN but not another?

Because DHCP often depends on broadcast handling or a relay agent, and those are usually tied to the VLAN and router configuration.

### Does DHCPv6 use the same ports as DHCP for IPv4?

No. DHCPv6 also uses UDP, but the port numbers and the surrounding IPv6 behavior are different from IPv4 DHCP.