192.168.1.1 How do I bind a static IP to a device? The printer lost contact when rebooted, and the NAS port forwarding failed. I fixed each device at home one by one
the cause of the incident was the HP printer at home. Originally, my phone's air printing was working fine, but one day I restarted the printer and couldn't find it on my phone again. Reinstalling the driver, restarting the router, and pressing the restore button on the printer for a long time all worked to no avail. Finally, after checking the device list in the 192.168.1.1 backend, I found that the printer's previous address was 192.168.31.106. After restarting, DHCP assigned it 192.168.31.112, but the phone still had the old address, so of course it couldn't connect.
this isn't a broken printer; it's DHCP the nature of dynamic allocation. : the address the router sends to your device has a lease term. When it expires or the device restarts, you reapply. Which address you get depends on the availability at the time. The device used to use your phone doesn't matter, but there are several types of devices that can cause trouble once you change address: printers, NAS, cameras, TV boxes—devices that are 'connected to by others.' This article will describe the complete process of fixing each device at home to a fixed address, including three pitfalls I encountered.
first understand: static binding is not about manually entering the IP address on the device, but about doing it on the router
many people, upon hearing "set static IP for the printer," immediately go to the printer's network settings and manually enter the IP, subnet mask, and gateway. This path is acceptable, but I strongly advise beginners not to do it. The reason is simple: if the IP you manually entered isn't in your mind, you forget it after half a year, and the device has another issue, so you'll have to take a detour to investigate; Moreover, if you manually enter the address into the DHCP allocation range, if one day the router assigns the same address to another device, the two machines clash and the fault becomes even stranger.
correct approach is called DHCP static allocation , while some routers call it "address retention," "static DHCP," or "IP and MAC binding." The names differ, but the tasks are the same: device's IP is automatically acquired, but the router remembers its MAC address and sends it the same IP every time . Zero configuration for devices, and the address for the network never changes—the benefits of both ends are included. At home, the printer, NAS, two cameras, and TV box are all fixed like this, and I've never had the 'lose contact after reboot' incident again.
Step one: Find the device list in 192.168.1.1 and identify who is who
Connect
your computer or phone to the router's WiFi, enter 192.168.1.1 in your browser, enter the management password to access the backend (if you can't get in, first check the troubleshooting for that won't open; for mobile operation, refer to of the process for connecting to 192.168.1.1). Then, in the backend, look for menus like "Device Management" or "Terminal Management" and "Connected Devices." Different companies have different terms: the new TP-LINK interface is under "Device Management," while the old interface is under "DHCP Server → Client List"; Mercury, Tenda, and TP-LINK follow the same model; ASUS in the "Web Map → Client"; Xiaomi is in the "Frequently Used Settings" → device list.
After
entering, you'll find an online device list, focusing on three columns: device name, IP address, and MAC address. identifying devices is the most time-consuming at this step, because half of the devices in the list display English codes or a string of letters and numbers. My clumsy method: compare them one by one. Pick up your phone and check the IP address in the WiFi details; if the number matches, mark it; For uncertain devices, just cut off the power—the one missing from the list is the one that disappears. The mysterious device at my home displaying "esp-A3F2" was dug out this way—a temperature and humidity sensor with ESP8266 chip disappeared from the list when the power was cut off, and it matched up.
here's a detail worth mentioning: it's also recommended to review devices like phones and laptops—not for fixation, but so you can understand the list when checking "which device is competing for bandwidth" in the future. previously wrote about how to locate the bandwidth-grabbing device , provided you can see who is in the device list.
Step 2: Static assignment of target devices, and I run through the NAS
After identifying
device, find the entry point for "DHCP static distribution." TP-LINK and Mercury are in "Device Management" by clicking "Static" or the pencil icon on the target device's line; Tenda has advanced features → address retention; ASUS → "Internal Network (LAN) DHCP Server →Manual Allocation"; In the "Device List," Xiaomi clicks on Devices and enters details, where there is a "Static IP" toggle. If you can't find the path, use the backend search box; searching for "static" or "DHCP" usually yields results.
after entering, you actually fill in two things: MAC address (usually automatically displayed, no manual input) and the IP address you want to fix. I used my Feiniu NAS at home as an example. Its original address was 31.112. After using it for a while, I found it hard to remember, so this time I fixed it directly to 192.168.31.10—the smaller integer that makes it easier to remember. Save and restart the NAS (you don't have to restart; it takes effect when you renew next time. I didn't want to wait and restarted), then use a browser to access the new address. If it works, it means it's bound.
There's a little trick
picking IPs: I set a rule for myself: pick from the end of DHCP's assigned range, or simply make the range smaller . My router's DHCP range is from 192.168.31.100 to 192.168.31.200, so all static addresses use 31.10, 31.11, 31.12 under 100, which are completely different from the dynamic pool and never clash. Some routers (ASUS, OpenWrt) can even directly check "Exclude static assignment" in DHCP settings, with the same logic.
the third type of device, let's talk about it separately: don't fix cameras and TV boxes randomly
I fixed all the cameras because the IP addressed when adding devices in the phone app changes and the app can't connect. The two cameras were set to 31.20 and 31.21, and for the next six months, they didn't disconnect again. The previous situation of "turning on surveillance and spinning around for half a day when outside" never happened again.
But I fixed the TV box in the wrong place at first. This was the first pitfall : I had two TV boxes at home, different models. I bound one of them based on memory, but it ended up binding the old address to the other. Both boxes got the same IP, and that night both TVs went black at the same time. The lesson is to always confirm the MAC address before binding, don't rely on the impression that "this IP has always been it"— recognize MAC, not IP. In the binding interface, the MAC will automatically appear. Check if the device name is correct before saving.
second pitfall is forgetting about this after binding. One day, I retired an old box, and the new box was connected to the same spot, but no matter what, it wouldn't get online. After fiddling for a while, I remembered: the MAC on the old box was bound to 31.15, while the MAC on the new box was different, so theoretically there shouldn't be a conflict—in the end, I found out the new box itself had a problem and it wasn't about binding. But my first reaction during troubleshooting was to suspect static binding, and I had to uninstall the network cable for nothing. To clarify: static binding only applies to designated MACs; switching devices won't block the new device's internet , but the old binding remains in the list and occupies a gap. It's recommended to delete the corresponding entry when retiring your device.
after binding static IPs, port forwarding and printer are truly stable
Why am I so fixated on a fixed address? Because is the foundational of a bunch of network functions. When I access my home NAS from outside, I rely on the port forwarding rules on the router, which specify the address 192.168.31.10—if the NAS ever switches to 31.115, the rule points to a device that doesn't exist, remote access will fail instantly, and the fault will be especially confusing: everything at home is normal, but you can't get back from outside. You never realize the IP has changed. In the about port forwarding and DMZ, I mentioned that 'intranet devices must first fix their IPs,' which refers to this issue. This time, the prequel has been completed.
printers are the same, and printers are even more delicate than NAS: they won't proactively tell you they've changed their address, just quietly lose contact. Once fixed, the printing configuration on your phone or computer is configured in one go, making it effective for a long time. Also the camera mentioned in the about installing surveillance cameras at home follows the same principle: the device address entered in the app must be valid for a long time.
summarize which types of equipment are worth fixing in a table and assign them accordingly:
| device type | should be fixed or not | reasons |
| printer | must be actively connected | phone or computer, If you change the address |
| NAS | you lose contact, you must | port forwarding, mapping rules all pointing to its IP |
| camera | must | App the address you entered when adding; if you change it, it spins |
| the TV box | casting and LAN players to recognize the address | |
| phones, laptops | there's no need to | they actively connect to others, and changing addresses doesn't matter |
troubleshooting incidentally: Address binding is not a cure-all
Finally, let's talk about a situation that is easy to misjudge. Some friends fixed all their devices as I told them and came to ask why their home WiFi was still laggy. Static binding only solves issues like "address changes"; it cannot handle weak signals, channel interference, or bandwidth being stolen. If your device lags a lot, check the on bandwidth; if signal is poor, check the frequency band and channel. A fixed IP is the foundation, not the decoration—don't expect it to cure all problems.
there's another scenario where the opposite is used: if you want to completely kick out a WiFi device , just changing the WiFi password isn't thorough enough. If the device reconnects and gets a new address, it can continue to ride. At this point, the statically bound sibling feature "MAC filtering" or "blacklist" comes in handy—adding your MAC to the block list and changing the address won't help. article about anti-anti-online has written a complete approach, so I won't repeat it here.
finish with a sequence, repeat it once, and it's done in half an hour: go to the backend and find the device list, identify each person one by one, pick out the "connected" devices like printers, NAS, and cameras, pick a few memorable numbers outside the DHCP range to fix them and save, then restart them, then check the port forwarding and printer configuration for the old addresses one by one. After the procedure, you'll find that those "every few days" little internet issues at home have been reduced by more than half.
