There's a particular type of network problem we encounter regularly — one that's created entirely by someone trying to be helpful. A previous IT person, a technically minded staff member, or an enthusiastic owner has manually assigned fixed IP addresses to devices on the network. It was done with the best intentions. It's now causing headaches that nobody can explain.
This is a surprisingly common situation, and it's worth understanding why it happens and why it's almost always the wrong approach.
First — what is an IP address, and how does it normally work?
Every device on a network has an IP address — a numerical label that the network uses to direct data to the right place. Think of it like a street address for each device.
Normally, your router assigns these addresses automatically through a system called DHCP (Dynamic Host Configuration Protocol). When a device joins the network, it asks the router for an address. The router assigns one from its available pool, keeps a record of the assignment, and the device uses it until it leaves the network or the lease expires. This happens automatically, invisibly, and correctly — thousands of times a day across well-run networks.
A static IP address is one that's been manually set on the device itself, bypassing this automatic process. The device declares its own address rather than asking the router for one.
Why does anyone do this?
The reasoning usually goes: "I want this camera/printer/server to always have the same address, so I know where to find it." That's a reasonable goal. The problem is that setting the address on the device is the wrong way to achieve it.
Why it causes problems
It breaks when the network changes
Networks change. Routers get replaced. IP address ranges get reconfigured. When this happens, devices with automatic addressing adapt immediately — they ask the new router for a new address and get one. Devices with manually set addresses don't. They continue using the address they were manually given, which may no longer be valid on the updated network. Suddenly a camera goes offline, a printer stops working, or a smart home device becomes unreachable — for no obvious reason.
Address conflicts
If a device has manually claimed an address and the router doesn't know about it, the router might assign that same address to another device. Two devices with the same address on a network creates a conflict — both stop working properly or behave erratically. These conflicts are notoriously difficult to diagnose because everything looks fine on the surface.
The router can't see it properly
When a device obtains its address automatically, the router logs it — it knows the device's name, what address it was given, and when. This information is visible in the management interface and is how network monitoring tools track what's connected. A device with a manually set address may not appear properly in these logs, making it effectively invisible to your network management system. If something goes wrong with that device, you're troubleshooting blind.
Network policies don't apply
Modern managed networks — like UniFi — apply policies to devices based on information gathered when they connect and get assigned an address. Traffic management, VLAN assignment, device tagging, and security policies can all depend on this process. A device that bypasses it by declaring its own address may not get correctly placed on the right network segment, or may be blocked entirely by security policies that flag unrecognised address assignments as suspicious.
The right way to give a device a fixed address: Configure the assignment in the router, not on the device. Almost all modern routers allow you to permanently associate a specific IP address with a specific device — so that device always gets the same address from the router, automatically. The device still uses the normal automatic process; the router just always gives it the same answer. This achieves the goal without any of the downsides.
What to do if you've inherited this problem
If you suspect devices on your network have manually assigned addresses — particularly if you have unexplained connectivity problems, devices that go offline for no obvious reason, or a network that was set up by someone with partial technical knowledge — it's worth having a professional look at the configuration.
The fix is usually straightforward: identify which devices have manually set addresses, move those assignments to the router instead, and restore automatic addressing on the devices. The result is a network that behaves predictably, can be properly monitored, and doesn't break when anything else changes.
💡 A tell-tale sign: if a device's network settings show an IP address but no "automatic" or "DHCP" option selected — or shows settings that were typed in manually — it's using a static address at the device level. This is almost always worth changing.
Mysterious network problems that nobody can explain?
We untangle complicated and poorly configured networks across the Southern Highlands. Often the cause is something simple that a fresh pair of experienced eyes finds quickly. Let's take a look.
Get in touch