How to Disable DHCP

Disabling DHCP is a little like firing the office receptionist who hands out name tags… and then wondering why nobody knows where to sit.
It can be the right move (labs, static infrastructure, certain security policies), but it can also turn a perfectly happy network into a
quiet room full of confused devices staring at each other like, “So… what’s my IP again?”

This guide walks you through how to disable DHCP safelyon common routers, business firewalls, Windows Server, and individual computersplus what to do
when (not if) something gets cranky afterward. We’ll also cover smarter alternatives like DHCP reservations, because sometimes the best way to “disable DHCP”
is… not disabling it at all.

What “Disable DHCP” Actually Means (Server vs. Client)

DHCP (Dynamic Host Configuration Protocol) is the service that automatically assigns IP addresses and related settings
(subnet mask, default gateway, DNS servers) to devices. When people say “turn off DHCP,” they usually mean one of two things:

1) Disabling the DHCP server (most common)

This is typically your router, firewall, or a dedicated server (like Windows Server or a network appliance). Turning off the DHCP server means
devices will no longer automatically receive network settings on that network/VLAN.

2) Disabling DHCP on a device (switching the client to static/manual IP)

Here you keep (or don’t care about) the DHCP server, but you configure a specific laptop, printer, or server to use a manual/static IP address.
This is common for servers, cameras, access points, and printersthings you always want at the same address.

Before You Disable DHCP: The “Don’t Lock Yourself Out” Checklist

If you disable DHCP without a plan, the best-case scenario is that nothing works. The worst-case scenario is… also that nothing works,
but now you can’t even log back into the router to fix it. Let’s avoid that.

Step 1: Decide who will hand out IP addresses now

• Option A: Another DHCP server will take over (recommended if you have lots of devices).
• Option B: You will use static IPs on every device (fine for small, controlled networks).
• Option C: You’ll mix static IPs (servers/printers) + DHCP (everything else) often the sweet spot.

Step 2: Pick a clean IP plan

Example for a small network:

Subnet: 192.168.10.0/24

Router/Gateway: 192.168.10.1

Static range: 192.168.10.2–192.168.10.49 (routers, switches, APs, servers, printers)

DHCP range (if used elsewhere): 192.168.10.100–192.168.10.199

Step 3: Set a static IP on your “admin” computer first

Before you flip the DHCP switch off, configure the computer you’re using to manage the network with a manual IP on the same subnet.
That way, when DHCP disappears, your admin machine doesn’t disappear with it.

Step 4: Save/export your current router/firewall config

If your device supports backups, take one. You’ll thank Past You later. Past You is very responsible and deserves a snack.

How to Disable DHCP on a Home or Small-Office Router

Every router UI is a little different, but the path is usually something like:

LAN Settings → DHCP Server → Disable or uncheck “Use Router as DHCP Server”

Generic router steps (works for most brands)

1. Log in to the router’s admin page (often via a browser).
2. Find LAN or Local Network settings.
3. Locate DHCP Server settings.
4. Disable it (toggle off / uncheck the box) and apply/save.
5. Immediately verify you can still reach the router using your admin machine’s static IP.

Example: Router UI that uses a checkbox

Some routers use wording like “Use Router as DHCP Server.” Uncheck it, apply changes, and be ready to set client IPs manually if there’s no other DHCP server.

Pro tip: If this is a “second router,” use Access Point mode instead

If you’re converting an old router into a Wi-Fi access point, the easiest route is often Access Point (AP) mode or Bridge mode.
These modes typically disable DHCP automatically and prevent “two DHCP servers enter, one DHCP server leaves” chaos.

How to Disable DHCP on Business Firewalls and Network Platforms

pfSense: disable per interface

1. Log in to the web UI.
2. Go to Services → DHCP Server.
3. Select the interface (LAN/VLAN) you want.
4. Uncheck Enable DHCP server on [interface].
5. Save/apply.

Note: DHCP is often configured per interface/VLAN. You can disable DHCP on one VLAN without touching others, which is great for staged migrations.

Cisco IOS / IOS XE: disable the built-in DHCP service

On Cisco devices that support DHCP services, you can disable the DHCP server/relay features with a global configuration command.
A typical workflow looks like this:

If the device is also acting as a relay (using helper addresses), make sure you understand whether you’re disabling only local service
or impacting other DHCP-related behavior in your design.

UniFi: disable DHCP on a specific network

UniFi setups usually define DHCP settings per “Network” (often per VLAN). If you’re handing DHCP to another device (like a firewall),
disable DHCP for that UniFi network so you don’t run competing services on the same segment.

How to Disable DHCP on Windows Server (DHCP Server Role)

If Windows Server is running DHCP and you want it to stop handing out leases, do it cleanlyespecially if it’s on a domain controller
(where DHCP services are typically discouraged unless intentionally designed).

Option A: Disable the DHCP Server service

1. Open Services (services.msc).
2. Find DHCP Server.
3. Stop the service if it’s running.
4. Set Startup type to Disabled.

Option B: Remove the DHCP Server role (more permanent)

If you’re decommissioning DHCP on that server entirely, removing the role helps avoid accidental re-enablement later.
(Do this only after confirming another DHCP server is live and tested.)

How to Disable DHCP on Client Devices (Switch to Static/Manual IP)

This is the “I don’t want this device to use DHCP anymore” scenario. Common for servers, printers, NAS boxes, and managed switches.
The rule is simple: you must manually enter the IP address, subnet mask/prefix, gateway, and DNS servers.
Miss DNS and you’ll be able to ping things by IP… but not by name, which feels like your network is haunted.

Windows 11/10

1. Open Settings → Network & Internet.
2. Select Wi-Fi (choose your network) or Ethernet.
3. Find IP assignment → click Edit.
4. Change from Automatic (DHCP) to Manual.
5. Enter IPv4 address, subnet prefix length, gateway, and DNS.

macOS

1. Open System Settings → Network.
2. Select your connection (Wi-Fi or Ethernet), then click Details.
3. Go to TCP/IP.
4. Set Configure IPv4 to Manually.
5. Enter IP address, subnet mask, router (gateway), and DNS.

Linux (Netplan on Ubuntu Server)

On many Ubuntu Server installs, Netplan controls networking. A typical static configuration looks like this:

Apply changes with:

Linux (NetworkManager / nmcli)

If you’re on a desktop distro (or a server that uses NetworkManager), you can switch a connection to manual/static using nmcli.
The exact connection name differs, but the concept is:

Troubleshooting After Disabling DHCP

If you disable DHCP and something breaks, don’t panic. Panic is for printers, not people.
Here are the most common issues and quick fixes:

Problem: “I can’t reach the router anymore”

• Set a manual IP on your laptop in the router’s subnet (for example, router is 192.168.1.1 → set laptop to 192.168.1.10).
• Plug in via Ethernet if possible.
• If you truly don’t know the router IP and can’t recover it, use the physical reset button (last resort).

Problem: Devices have “Self-assigned IP” (like 169.254.x.x)

That’s your device saying, “I asked for DHCP and nobody answered.” Either re-enable DHCP somewhere, or give that device a valid static IP.

Problem: IP conflicts (random disconnects, weird warnings)

• Two devices may share the same static IP. Create a simple IP inventory list.
• Don’t assign static IPs inside a DHCP pool (unless you’ve reserved them).

Problem: Internet works by IP, but websites don’t load

That’s classic DNS misconfiguration. Verify DNS servers on clients, and confirm your gateway and subnet mask/prefix are correct.

Smarter Alternatives to Fully Disabling DHCP

Turning off DHCP is sometimes presented as a “security trick,” but in many environments it’s just extra work with very little real protection.
A more practical approach is usually one of these:

Use DHCP reservations (best of both worlds)

DHCP reservations let the DHCP server keep running while always giving specific devices the same IP address. You get consistency without manually configuring
every deviceand you avoid the “Who assigned 192.168.10.27 to the toaster?” mystery.

Keep DHCP for clients, use static for infrastructure

A common best practice:

• Static/manual: routers, firewalls, switches, access points, servers, printers
• DHCP: laptops, phones, tablets, guest devices, anything that comes and goes

Disable rogue DHCP instead of disabling DHCP entirely

If your concern is “someone plugged in a rogue router,” the answer isn’t necessarily “disable DHCP everywhere.”
The answer is often switch protections (like DHCP guarding/snooping) so only approved DHCP servers can respond.

Conclusion

Disabling DHCP can be absolutely validespecially in controlled networks, labs, or when another DHCP server will take over.
The key is doing it in the right order: plan your IP scheme, set a static IP on your admin machine, disable DHCP in the right place
(router/firewall/server), and verify connectivity immediately.

If you’re doing this just because someone on the internet said “DHCP is insecure,” consider DHCP reservations or DHCP guarding instead.
Your future self will appreciate fewer late-night “Why is the Wi-Fi angry?” conversations.

Real-World Experiences Disabling DHCP ( of Field Notes)

1) The “Two Routers, One Network” classic. A small office had an ISP modem/router and a shiny new Wi-Fi router. Someone left DHCP enabled on both.
Half the laptops got addresses from Router A, the other half from Router B, and nobody could find the printer (because the printer was loyal to neither).
The fix was simple: pick one device to be the “real router,” disable DHCP on the other, and (bonus points) switch the second unit to Access Point mode.
The lesson: two DHCP servers on the same subnet is like two people trying to steer the same shopping carteveryone ends up in the snack aisle, upset.

2) The “I disabled DHCP and now I’m locked out” moment. This happens when your laptop was using DHCP and you turn off DHCP… then your laptop loses its IP.
Suddenly you can’t reach the router to turn DHCP back on. The quick recovery move is setting a manual IP on your laptop that matches the router’s subnet,
plugging in via Ethernet, and logging back in. It feels too easy after the panic, which is why it’s so common: people expect a dramatic fix, not a dropdown menu.

3) Static IPs everywhere: the honeymoon and the breakup. In a lab with a handful of devices, static-only is beautiful.
Everything is predictable, documentation is clean, and nothing changes unless you change it. Then the lab grows. A few more devices arrive.
A few more turn into a lot more. Suddenly static IP management becomes a part-time job, and nobody is sure if 192.168.10.23 is a camera,
a switch, or a mysterious device that pings back only on Tuesdays. At that point, many teams “re-discover” DHCPthen use reservations for the important stuff.

4) DNS: the silent troublemaker. One of the sneakiest failures after disabling DHCP is forgetting to set DNS on clients.
You can still ping 8.8.8.8, so you think “internet is fine,” but browsing fails because names won’t resolve. The fix is just entering valid DNS servers
on the client (or pointing to your internal DNS), but it’s always the last thing people checkbecause DNS problems are the networking equivalent of
“Did you try turning it off and on again?” (Annoying. Effective. Eternal.)

5) The security myth that won’t die. Disabling DHCP is sometimes pitched as a Wi-Fi security booster.
In reality, an attacker who’s already on your network can still assign themselves a static IP. Meanwhile, your legitimate users are now calling you
because their phones “won’t connect.” A better security approach is strong Wi-Fi authentication, proper segmentation (guest VLANs), and switch protections
against rogue DHCP servers. In other words: lock the door, don’t remove the house numbers.