How to Give Your Barcode Scanners Static IPs (And Why You Should)

Networked barcode scanners are one of those things that work fine until they suddenly don’t, and the failure mode is almost always the same: the IP address changed. Maybe DHCP handed out a different lease after a weekend power cycle. Maybe the router firmware updated and reset lease times. Either way, your Wavelink session is broken, your telnet host configuration is pointing at nothing, and someone on the floor is standing there with a scanner that won’t connect.

The fix is straightforward: give your scanners fixed IP addresses and leave them there. How you do that — and which approach is right for your environment — is what this article covers.

Why a Changing IP Is Actually a Problem

On a workstation running a browser-based application, a changing IP usually doesn’t matter. The workstation connects outbound to a server, and the server doesn’t care what the client’s IP is.

Networked barcode scanners are different in a few important ways.

Host-directed sessions. In many warehouse environments, scanners run terminal emulation or a thin client application — Wavelink, Ivanti Velocity, StayLinked, or a similar platform. The session configuration on the scanner specifies a host address to connect to. In some configurations, the host side has an ACL or whitelist that includes scanner IPs. If the scanner’s IP changes, the connection logic breaks. Sometimes immediately, sometimes the next time the session times out and tries to re-establish.

Telnet and legacy protocols. Plenty of WMS environments still use telnet-based scanner sessions. Telnet connections are point-to-point — the scanner initiates a connection to the host at a configured address, and sometimes the host maintains a mapping of device IDs to IPs for session management purposes. IP drift creates mismatches in those tables.

Troubleshooting. When you have 40 scanners on a floor and one is misbehaving, being able to look up “scanner 12 is at 10.10.20.112” and ping it, telnet to it, or pull its config remotely is enormously useful. If your DHCP table is the only record of which scanner has which IP, and that table changes every 24 hours, you’re doing operational detective work every time something goes wrong.

Fixed IPs solve all of this. The question is how to implement them.

Two Approaches: True Static vs DHCP Reservation

True static IP means you configure the IP address, subnet mask, gateway, and DNS directly on the scanner device itself. The scanner ignores DHCP entirely and always presents the same IP. This works and has worked for decades. The downside is that device-level configuration is manual — you have to touch each scanner to configure it, the configuration lives on the device and has to be re-applied if the device is reset or replaced, and managing a fleet of scanners each with hand-configured IPs is tedious to keep synchronized.

DHCP reservation (sometimes called a static DHCP lease or MAC address reservation) means you configure your DHCP server to always hand the same IP to a specific device, identified by its MAC address. The scanner still uses DHCP — it sends a DHCP request when it boots, and your server always responds with the same address. From the scanner’s perspective, nothing is special. From your perspective, you have a single place (the DHCP server or router) where all the IP assignments are documented and managed.

My recommendation: DHCP reservation for most environments. Here’s why:

When you replace a scanner — hardware failure, upgrade, whatever — you update the MAC address in your DHCP reservation table and you’re done. With a true static configuration, someone has to physically program the new scanner before it can take the role of the old one. In a facility with rotating spare units, DHCP reservations are much easier to manage.

The exception: environments where DHCP infrastructure is unreliable or where scanners need to maintain their IP even when the DHCP server is temporarily unavailable. In those cases, true static on the device is the safer call.

Finding the Scanner’s MAC Address

Before you can create a DHCP reservation, you need the MAC address of each scanner. The method varies by manufacturer.

Zebra Scanners

On most Zebra Wi-Fi handheld scanners (TC-series, MC-series), the quickest method is to print a configuration label. Hold the scan trigger and press the power button — on most models this initiates a self-test that prints a configuration sheet. On that sheet look for WLAN MAC (the wireless MAC address). That’s the value you need.

Alternatively, navigate the scanner’s Settings menu: on Android-based Zebra devices, go to Settings → System → About phone → Status or Settings → About device → Wi-Fi MAC address depending on the OS version and launcher. The exact path varies a bit across the TC21, TC52, TC57, MC33, and similar series, but it’s always somewhere in the About section.

For Zebra presentation scanners and corded units, the MAC is usually printed on a label on the device itself or accessible via the Zebra 123Scan utility if you have it connected.

Honeywell Scanners

On Honeywell Wi-Fi scanners, the EZConfig for Scanning utility (Honeywell’s configuration tool, available from their support site) lets you scan a Device Information barcode that displays the MAC address on-screen. The configuration label approach also works on some Honeywell models — check the specific device manual for the exact button sequence.

On Android-based Honeywell units like the CT40 or CK65, it’s under Settings → About phone → Wi-Fi MAC address, same pattern as Zebra.

Write down the MAC addresses with a note of which physical device each belongs to. A spreadsheet with columns for scanner number, model, serial number, MAC address, and assigned IP is five minutes of work that saves a lot of pain later.

Setting DHCP Reservations: Common Platforms

Ubiquiti UniFi

If you’re running Ubiquiti’s UniFi stack, IP reservations are in the UniFi Network application under Settings → Networks, then click on your SSID or wired network, navigate to DHCP, and look for Fixed IP Assignments or DHCP Reservations depending on your controller version.

The interface asks for a name (use something descriptive like “Scanner-Floor-01”), the MAC address, and the IP you want to assign. The IP must be within the DHCP range of that network. Once saved, the next time that device sends a DHCP request, it gets the assigned address.

UniFi is clean for this. The reservation table is easy to read and manage, and you can export it.

TP-Link Omada

In the Omada controller, go to Settings → Wired Networks → LAN, select your network, and look for DHCP Server settings. Scroll to Address Reservation and add entries with MAC address and assigned IP. Same concept, slightly different navigation.

pfSense / OPNsense

In pfSense, navigate to Services → DHCP Server, select the interface (usually LAN), and scroll to the DHCP Static Mappings section at the bottom. Click Add, enter the MAC address, IP, and a hostname. OPNsense is similar: Services → DHCPv4 → [your interface], scroll to Static Mappings, add an entry.

The pfSense/OPNsense approach has the advantage that you can also assign hostnames here, which brings me to the next section.

Setting a True Static IP on Zebra Scanners via 123Scan

If you’re going the true static route on Zebra handheld scanners, the cleanest way to do it at scale is via 123Scan, Zebra’s free Windows configuration utility.

In 123Scan, create or open a configuration profile for your scanner model. Navigate to the Network settings panel. You’ll see options for DHCP (enabled by default) and manual IP configuration fields: IP Address, Subnet Mask, Default Gateway, Primary DNS, and Secondary DNS.

Disable DHCP, fill in the static values, and build the configuration. 123Scan will generate a programming barcode. Scan it with the device and the network settings are applied. The scanner will now ignore DHCP and use the addresses you specified.

The limitation is per-device deployment — you need to generate a unique config for each scanner with a unique IP, or use a batch approach if your 123Scan version supports it. For small fleets this is manageable. For 50+ devices, DHCP reservations are almost always the better operational choice.

Field Notes — Weekly tools, techniques, and deals from J.D. Sweeney. Subscribe free →

IP Addressing Conventions for Scanner Fleets

When you’re assigning scanner IPs, take five minutes to think about your subnet structure. Ad-hoc IP assignment creates a mess that’s hard to untangle later.

A clean approach for a warehouse environment:

Segment by function. If your network is 10.10.0.0/16, consider something like:

10.10.10.x — servers and infrastructure
10.10.20.x — scanners and mobile devices
10.10.30.x — workstations and desktops
10.10.40.x — printers

Putting all your scanners in 10.10.20.x means your ACLs, firewall rules, and monitoring can target a specific range. You know immediately what a device is just from its IP. And when someone asks “is the scanner at 10.10.20.47 reachable?”, the answer doesn’t require looking up a device inventory first.

Use a dedicated VLAN if your infrastructure supports it. A scanner VLAN isolates scanner traffic from general office traffic and from IT infrastructure. It also makes it easier to apply QoS policies if your WMS sessions need priority treatment. Most managed switches and Ubiquiti/Omada/pfSense setups can handle VLAN segmentation without much complexity. If you’re running UniFi, creating a VLAN for scanner devices and putting the right SSID on it is about 15 minutes of work.

Number scanners sequentially and track them. Scanner-01 through Scanner-40, each with a corresponding IP. When a scanner is retired or replaced, update the record. It’s not complicated, it just has to be done consistently.

DNS Hostname Registration

This one gets skipped constantly, and it’s worth the five minutes.

When you create a DHCP reservation in pfSense or OPNsense, you can assign a hostname at the same time. In pfSense’s static mapping, there’s a Hostname field. Fill it in — something like scanner-floor-01 or wh-scanner-12. pfSense will register that hostname in its internal DNS resolver (Unbound), so that hostname resolves to the scanner’s IP within your network.

Why it matters: instead of remembering that scanner 12 is at 10.10.20.112, you can ping scanner-floor-12, pull a telnet session to it by name, or reference it in your monitoring configuration by hostname. When you replace a device and update the MAC in the reservation, the hostname stays the same. Any scripts or monitoring configs pointing at the hostname don’t need to change.

UniFi also does this automatically for clients with fixed IP assignments if you have the UniFi local DNS configured correctly.

This doesn’t require a full enterprise DNS server. The DHCP server doubling as a local DNS resolver — which pfSense/OPNsense do natively — is sufficient for a warehouse environment.

Recommended Hardware for Networked Scanner Deployments

The Zebra DS3608 scanner is a solid choice for USB and presentation scanning at fixed workstations — ruggedized, fast on 1D and 2D codes, USB and serial connectivity. For Wi-Fi networked handheld scanning where static IP management actually matters, you’re typically looking at Zebra’s MC or TC series mobile computers rather than a corded scanner.

For environments running Honeywell, the Honeywell Voyager 1470g covers the corded workstation case well — 1D/2D imaging, USB, solid build quality for a desk-mounted station.

The static IP and DHCP reservation practices in this article apply to any network-connected scanner regardless of brand. The specific menu paths to find MAC addresses and configure network settings differ by model, but the underlying approach is the same.

Quick Reference

To set up a DHCP reservation:

Find the scanner’s MAC address (config label, Settings menu, or EZConfig)
Log into your router/DHCP server
Create a static mapping: MAC address → IP address → hostname
Reboot the scanner so it requests a new DHCP lease
Verify it received the correct IP

To set a true static IP on a Zebra scanner via 123Scan:

Open 123Scan, create/edit a profile for your device model
Go to Network settings, disable DHCP
Enter IP address, subnet mask, default gateway, DNS
Generate and print/display the programming barcode
Scan it with the device
Verify the network settings applied via the device’s About menu

A few hours spent on this correctly pays back in eliminated troubleshooting calls for the life of the deployment. Do it once, document it, and you won’t think about scanner IP addresses again until you add hardware.