Skip to content

We're upgrading our operations to serve you better. Orders ship as usual from Laval, QC. Questions? Contact us

Bitcoin accepted at checkout  |  Ships from Laval, QC, Canada  |  Expert support since 2016

WM_TOOL_TMO Info

Whatsminer – MinerTool Connection Timeout

WhatsminerTool (MinerTool) times out while trying to discover, authenticate to, or query the miner over its TCP 4028 API or UDP discovery broadcast. Almost always network, credentials, or firmware-handshake — occasionally a wedged control board.

Informational — Monitor and address as needed

Affected Models: Whatsminer M20S, M21S, M30S, M30S+, M30S++, M31S, M50, M50S, M50S+, M50S++, M53, M56, M60, M60S, M63, M66

Symptoms

  • WhatsminerTool shows `Timeout` or `No Response` after scan; miner never appears or appears then disappears
  • `IPFOUND` button lights an IPv4 address on the chassis but that IP is unreachable from the tool's workstation
  • `ping <miner_ip>` succeeds but the miner never appears in WhatsminerTool
  • `nmap -p 4028 <miner_ip>` returns `filtered` or `closed` instead of `open`
  • Web UI at `http://<miner_ip>` loads normally but WhatsminerTool still times out
  • Discovery finds zero miners on a subnet that has multiple known-running Whatsminers
  • Tool stops connecting to one or more units after a firmware upgrade (e.g. around `20231101` through `20251209.16`)
  • Tool connects from one workstation but times out from another on the same LAN
  • Connection succeeds for 2-3 seconds, returns partial data, then drops (half-open TCP / MTU mismatch)
  • Custom firmware (Vnish, Asicdip, HiveOS) installed; stock WhatsminerTool refuses to enumerate (anti-tamper `100001`/`100002`/`100003`)
  • Multiple miners show the same IP in WhatsminerTool (DHCP lease collision after router reboot)
  • Password field in the tool is non-empty but the miner is still at factory `admin`/`admin` (or vice-versa)

Step-by-Step Fix

1

Press the `IPFOUND` button on the miner chassis and read the IPv4 address displayed on the front LED/LCD. Compare it to what WhatsminerTool is trying to reach. Roughly 40% of `WM_TOOL_TMO` cases end here because the router handed out a new DHCP lease and WhatsminerTool cached the old one. If no IP displays at all, the control board is wedged and you should skip ahead to Tier 3 control-board isolation.

2

Unplug the miner's Ethernet cable for 5 seconds, plug it back in, and wait 60 seconds for DHCP renewal. Rescan in WhatsminerTool. This clears a stuck Layer-2 state from the miner's control board and forces a fresh DHCPDISCOVER on the wire.

3

Reboot the router or switch that the miner is plugged into. A stale ARP entry on a consumer router is a surprisingly common root cause — the router still thinks the miner is at its old MAC/IP pairing and drops the broadcast that WhatsminerTool needs for discovery.

4

Move the laptop running WhatsminerTool to a wired Ethernet connection on the same physical switch as the miner. Eliminates Wi-Fi issues, VLAN separation, and guest-SSID broadcast isolation in one move. If the tool now discovers the miner, the problem was in your upstream network topology.

5

Temporarily disable VPN, corporate endpoint protection (CrowdStrike, SentinelOne, etc.), and the Windows Defender firewall. Rescan. If the tool now works, the root cause was host-side filtering — add a permanent firewall exception for outbound TCP `4028` and UDP broadcast to WhatsminerTool before re-enabling protection.

6

From your workstation, run `ping <miner_ip>` and `nmap -p 4028 <miner_ip>`. Healthy: sub-5 ms ping RTT with 0% loss, port `open`. If ping fails you're on a different subnet or the miner is off the wire; if port returns `closed` the API switch is off on the miner; if `filtered`, a firewall is blocking. This single step resolves 90% of remaining ambiguity.

7

Open `http://<miner_ip>` in a browser, log in as `admin` / `admin` (or whatever password is set), navigate to Remote Ctrl and ensure the API switch is ON. Factory-reset images and some hosting-provider builds ship with the API disabled by default. Save and retry WhatsminerTool.

8

Confirm you are running WhatsminerTool V9.0.1 or newer. The V8.x line has known discovery bugs on M50 and M60 series units. Download the latest from `support.whatsminer.com` or a verified mirror. Delete any `config.ini` or `config.xml` in `%AppData%WhatsminerTool` on Windows to clear cached stale IP/MAC entries, then relaunch.

9

Verify the admin password in WhatsminerTool → Settings exactly matches the miner's current password (no trailing whitespace, correct case). If the password was changed and lost, factory-reset the miner via the IPFOUND-button long-press or dedicated reset button — 10-15 seconds depending on model — which restores `admin`/`admin` but wipes pool, network, and tuning config.

10

If you run a managed switch (Ubiquiti UniFi, MikroTik, Cisco), verify the miner's port and your laptop's port are in the same VLAN and broadcast domain. Disable broadcast/multicast isolation on those ports. As a control test, plug both into an unmanaged dumb switch with default config — if the tool now works, the managed switch's ACL or VLAN policy was the culprit.

11

Run Wireshark on the workstation, filter `udp port 14235 or tcp port 4028`, click Scan in WhatsminerTool. You will see one of three patterns: (a) UDP broadcast goes out, no reply = network/VLAN issue; (b) TCP SYN to `4028` returns RST or times out = API off or host firewall; (c) TCP handshake completes, encrypted command times out = password/token mismatch. Each points at a distinct fix.

12

SSH into the miner: `ssh admin@<miner_ip>` — stock MicroBT firmware accepts SSH with the admin password. Run `cat /etc/issue` and `cat /version` to confirm firmware build. Run `netstat -tln | grep 4028` to confirm the API daemon is actually listening. If it is not listening the daemon has crashed — issue `reboot` over SSH or cycle power at the PSU.

13

If SSH and the web UI confirm the miner runs non-MicroBT firmware (Vnish, Asicdip, HiveOS), stock WhatsminerTool may refuse to enumerate it due to anti-tamper codes `100001`/`100002`/`100003`. Either accept the tradeoff and use the custom firmware's own dashboard, or reflash stock firmware via the web UI to restore MicroBT tool compatibility.

14

For a clean stock reflash: download the signed `.bin` for your exact model family from `support.whatsminer.com`, open the web UI → Upgrade Firmware → upload the signed image, wait for completion, reboot, factory-reset, re-provision. Never flash an unsigned or cross-model image — wrong firmware for the wrong hardware revision bricks the control board and lands you in Tier 4.

15

If the web UI works but WhatsminerTool specifically times out on write commands (pool change, power-limit set, firmware upgrade) while read commands succeed, you are hitting the encrypted-command token handshake. Confirm the password matches exactly; if the handshake still fails after a factory reset, the anti-tamper store on the control board may be corrupted — reflash stock and rebuild config from scratch.

16

If the miner is fully unreachable but the PSU LED is lit and fans spin, attempt firmware recovery via the model-specific IPFOUND-button-plus-power-cycle sequence (M30 series, M50 series, and M60 series each have a slightly different procedure — consult the Whatsminer recovery docs for your model). Recovery mode exposes a bootloader shell where you can reflash stock firmware from a TFTP or USB source.

17

Stop DIY: PSU is live, fans spin, status LED is lit, but ping/IPFOUND/web UI/SSH all silent AND recovery-mode flash has failed once. The control board's network stack or eMMC is failed and you're in bench territory. Book a D-Central ASIC repair slot — we stock replacement control boards for M20 through M66 series and re-provision on a test fixture with a known-good PSU.

18

Shipping: include the miner's serial number, last-known firmware version, and a one-line description of what you already tried on a note in the box. Anti-static bags, minimum 5 cm of foam on every side, double-box. This cuts our diagnostic time in half and directly saves you money on the repair. Canada-wide shipping standard; US and international welcomed.

When to Seek Professional Repair

If the steps above do not resolve the issue, or if you are not comfortable performing these repairs yourself, professional service is recommended. Attempting advanced repairs without proper equipment can cause further damage.

Related Error Codes

Still Having Issues?

Our team of Bitcoin Mining Hackers has been repairing ASIC miners since 2016. We have seen it all and fixed it all. Get a professional diagnosis.