ViaBTC | Antminer IP Address Not Found? A Network Discovery Checklist

Antminer IP Address Not Found? A Network Discovery Checklist

2026-10-18 16:07

Introduction

If you cannot find your Antminer’s IP address, start with its Ethernet connection, the computer’s network segment, Bitmain’s IP Reporter, and the router’s DHCP lease list. If you already know the current IP but the management page will not load, that is a separate access problem: check the network path and try another browser before assuming the address is missing. An unavailable management page alone does not tell you whether the miner is still hashing or submitting shares.

This article treats a missing Antminer IP address as a network discovery problem and walks through it in a practical troubleshooting order — confirming the physical connection, identifying the correct network segment, using Bitmain's official discovery tool, checking DHCP leases and address conflicts, and escalating safely if none of those steps work. Pool configuration, worker names, and Stratum URLs are addressed only at the end, after local access has been restored, because changing pool settings cannot fix a device that the network cannot see.

Check physical connection

Before searching for an IP address, confirm that the miner has completed its boot sequence and has an active Ethernet link.

Practical checks:

Confirm the unit is powered on and has had enough time to finish booting; control boards on Antminer units generally need a short warm-up period before network services become available.
Verify the Ethernet cable is fully seated at both the miner's control board and the switch or router port.
Check the link and activity indicators on the Ethernet port or switch port, where the hardware provides them.
On models with status LEDs, wait for the pattern documented in that model's manual before assuming the device is unreachable. Bitmain's T17 setup guide, for example, instructs users to wait for a steady green flashing pattern before attempting to find the IP address; this behavior is model-specific and should not be assumed for every Antminer series.

If a normally available link indicator stays off, first check the cable, switch or router port, and control-board power. If a known-good cable and another enabled port do not restore the link, check the control-board status and consult Bitmain support. Resolve the missing Ethernet link before continuing with IP discovery.

Identify the correct network

A common reason an Antminer appears "not showing on network" is that the computer running the search and the miner itself are not actually on the same network segment.

Situations that cause this mismatch include:

A laptop connected to guest Wi-Fi while the miner is wired into the primary LAN.
A managed switch placing the miner and the computer in different VLANs.
Wireless client isolation on the router, which blocks wireless devices from reaching wired ones.
An active VPN connection, which can route local traffic away from the LAN.
A miner still holding a static IP address from a previous network, which no longer matches the current router's subnet.

Antminer management interfaces on typical home and small-site networks use private IPv4 addresses — the ranges 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16 defined in RFC 1918. These addresses are not directly routable over the public internet. For IP Reporter, use a computer on the same network segment as the miner, as Bitmain specifies. Accessing a known IP through a browser instead requires a valid network route and permission to reach the management interface; this can include an appropriately configured internal routed network or trusted VPN. For straightforward local troubleshooting, use the same LAN or VLAN.

Use official discovery tools

Once the computer is confirmed to be on the same network segment as the miner, Bitmain's IP Reporter utility is the most direct manufacturer-supported method for locating an Antminer's address, particularly when the unit is using DHCP and has no previously recorded address.

Follow Bitmain’s official IP Reporter guide:

Download IP Reporter through the official guide or Bitmain’s firmware download page, then extract the ZIP file.
Run IPReporter.exe; the S21 Immersion manual specifies running it as Administrator.
If prompted, allow the program to communicate on the trusted local network where the miner is connected.
Click Start in IP Reporter.
Use the miner’s IP Report button according to the instructions for that exact model.
Record the displayed IP and MAC address, confirm the device, and enter its IP address in your browser.

Bitmain’s general guide lists Windows XP, Windows 7, and Windows 10. That list does not establish compatibility with newer operating systems; check current manufacturer guidance for your system. If you cannot run IP Reporter, use the router’s DHCP lease list as described below.

Button timing is model-specific. Bitmain's general IP Reporter guidance describes a one-second press, while the Antminer S21 Immersion manual instructs users to hold the button until the unit beeps, which takes approximately five seconds. Readers working with an Antminer S19 IP address issue, an S21, or another model should confirm the exact procedure in that model's manual rather than apply instructions written for a different series.

If IP Reporter does not detect the unit even though the computer is on the correct segment, check whether the program has local-network permission, whether the switch isolates ports, and whether the miner has completed startup. These checks are not exhaustive; if discovery still fails, continue with the DHCP and escalation steps below.

Check DHCP and address conflicts

Most Antminers ship configured for DHCP, meaning the router or DHCP server assigns the address rather than the device holding a fixed one. Bitmain's documentation notes that a new miner in DHCP mode does not have a fixed IP address, which explains why an address that worked previously may stop responding after a reboot, a lease renewal, or a router replacement.

To find the current address through the network itself:

Open the router's or DHCP server's client list, often labeled Connected Devices, DHCP Clients, DHCP Leases, or Client List depending on the manufacturer.
Look for a hostname that resembles "Antminer," where the router displays hostnames, but confirm the match using the device's MAC address rather than relying on the name alone.
Check the lease timestamp or "last seen" time against when the miner was powered on, which helps separate it from other devices on a busy network.
If several Antminers are connected to the same switch, connecting or powering them up one at a time can make matching a specific unit to its lease considerably easier.

Address conflicts are a related and separate cause of an unreachable management page. These occur when a device has been manually assigned a static address that is also within the router's active DHCP pool, or when two devices on the network end up using the same address. If the miner was previously configured for a static IP, check that the address still falls within the current subnet and does not collide with another client before concluding that the device is offline.

Once the correct device has been identified by MAC address, a DHCP reservation is generally the more maintainable option for most home or small-site networks, since it ties that MAC address to a chosen IP address inside the existing DHCP system rather than requiring the address to be entered and tracked manually on the miner itself, as described in Microsoft's DHCP server documentation. A static IP configured directly on the miner is also supported on many Antminer firmware versions, provided the chosen address fits the subnet and does not fall inside the router's DHCP pool.

Escalate without unsafe resets

If cabling, network segment, IP Reporter, and the DHCP lease list all fail to reveal the device, work through a short escalation path before considering a factory reset:

Re-seat or replace the Ethernet cable.
Try a different switch or router port.
Confirm the port is enabled and assigned to the expected VLAN, if the network uses VLANs.
Restart the miner only after recording its current visible status, since a restart can change which DHCP lease it receives.
Confirm the DHCP service has available addresses left in its pool and is otherwise functioning normally.
Check whether the unit was previously configured with a static IP that may no longer match the current network.
Consult the manual for that exact Antminer model before attempting any reset procedure.

A factory reset should be treated as a last resort because it can erase saved network settings, pool configuration, and worker details. Reset procedures are also model-specific: the Antminer S21 Immersion manual, for instance, instructs users to let the unit run for five minutes and then hold the reset button for ten seconds, which is not necessarily the correct sequence for other Antminer series. Where a reset genuinely appears necessary, following the documented procedure for that specific model reduces the chance of erasing configuration unnecessarily.

What not to do

Do not expect IP Reporter to discover a miner on a different network segment. Access to a known management IP from another subnet or a trusted VPN requires appropriate routing and access permissions; a private address is not directly reachable over the public internet.
Do not change pool settings before the miner's local management page has been reached — the pool URL cannot reveal or repair a missing local IP address.
Do not assume every Antminer model uses the same IP Report button timing; confirm the procedure in the manual for that specific unit.
Do not reset the miner before checking cabling, network segment placement, and IP Reporter results.
Do not assign a static IP address without confirming it fits the subnet and does not conflict with another device or the DHCP pool.
Do not expose the miner's management interface directly to the public internet through port forwarding; keep device administration on a trusted local network.

After you find the Antminer IP: verify pool configuration

Once the miner’s local IP address is confirmed and its web interface loads, check its operating status and pool connection. Finding the device on the LAN does not establish that it can reach the pool or submit accepted shares. Review the pool URL and worker name, then check accepted-share activity on the miner and the pool’s worker status page.

ViaBTC's current BTC mining configuration guide lists the BTC Stratum endpoints stratum+tcp://btc.viabtc.io:3333 and stratum+tcp://btc.viabtc.io:443, along with the Smart Mining endpoints stratum+tcp://bitcoin.viabtc.io:3333 and stratum+tcp://bitcoin.viabtc.io:443. Worker names follow a userID.workerID format, with the worker ID limited to lowercase letters and numbers up to 64 characters. ViaBTC's guide also notes that multiple ports can be entered in the miner's configuration so that the unit can fall back to an alternate endpoint if one connection attempt fails.

If the miner connects locally but appears offline or shows no recent share activity on the ViaBTC worker dashboard after pool settings have been entered, ViaBTC's step-by-step ASIC connection guide covers verifying the pool URL, worker name format, and firmware-side mining configuration in more detail. Continue with those checks after restoring local access. If shares remain absent, also check internet connectivity and the miner’s operating status and logs; local web access alone does not rule out network or hardware problems.

FAQ

Why can't I find my Antminer's IP address after a reboot?

Most Antminers use DHCP by default, which means the router assigns the address rather than the device keeping a fixed one. A reboot, a lease renewal, or a router change can result in a different address being assigned, so an address that worked before may no longer respond. Checking the router's current DHCP lease list, matching by the miner's MAC address, or using Bitmain's IP Reporter utility will reveal the current address.

Does IP Reporter work if my computer is on Wi-Fi and the miner is wired in?

It depends on whether the Wi-Fi network and the wired network are part of the same network segment. Bitmain's documentation specifies that the computer and the miner need to be on the same network for IP Reporter to detect the device. If the Wi-Fi network is isolated from the wired LAN, as is common with guest networks, connect the computer to the same network segment as the miner before running the tool.

Is there a universal default password for the Antminer web interface?

Default credentials can vary by model, production batch, and firmware version, and may also have been changed during a previous setup. Confirm the credentials documented for that specific model and firmware, and change the password after regaining access where the interface supports it.

Should I use a static IP or a DHCP reservation for my Antminer?

A DHCP reservation is configured on the router or DHCP server, while the miner remains in DHCP mode. It ties the miner’s MAC address to a chosen IP address and can simplify address tracking. A static IP is configured on the miner itself, where supported by its firmware. In either case, use an address in the correct subnet and prevent conflicts with other devices or dynamically allocated addresses.

My Antminer is connected to the pool but shares stopped updating — is this a network discovery problem?

Not necessarily. A miner that previously submitted shares can stop because of a local network interruption, loss of internet access, pool configuration, or a power, temperature, or hardware problem. First check whether it is currently reachable locally and running normally. If you cannot locate its IP, use this checklist. If local access works, check its mining status, accepted shares, internet connectivity, pool settings, and logs. Missing share activity alone does not identify the cause.

References

ICERIVER KS7 Profitability: Check Delivered Cost, Actual Power and KAS Output

Antminer KS5 Pro Profitability: Testing Emission, Power, and Downtime Scenarios