NAS Codex › QNAP › Qfinder Pro can't find your QNAP NAS: QNAP's checks, in order

Qfinder Pro can't find your QNAP NAS: QNAP's checks, in order

You open Qfinder Pro and your QNAP NAS is not in the list. Sometimes you can still reach it by its IP address in a browser; sometimes the NAS has dropped off the network entirely. QNAP's own FAQs treat these as two different problems. This page gives QNAP's checks for both, in the order QNAP recommends, plus how to add the NAS to Qfinder Pro by hand.

Written against: QTS and QuTS hero (QNAP FAQs last modified 2025-06-20, 2026-10-16 and 2026-11-16). Last Updated: November 2026. Vendor menus and wording change between versions; if yours differ, follow the vendor page linked under Sources.

Before anything else: if the data on this NAS is not backed up somewhere else, copy it off first. Do not continue with any step on this page until you have.

Fast Answer

First, make sure the NAS has finished booting: QNAP says a normal start gives two beeps, the second about 3 to 5 minutes after power-on, and only after the second beep can Qfinder Pro detect it. If the NAS works by IP but Qfinder Pro cannot see it, QNAP's order is: firewall or antivirus on the computer, different subnets or router isolation, QuFirewall on the NAS, virtual network adapters, and an invalid third-party App Center repository. If the NAS is on another subnet, add it by IP with Tools > Add Device Manually.

Why Qfinder Pro can miss a NAS that is working

QNAP explains that Qfinder Pro finds NAS devices by sending broadcast/multicast discovery packets on the local network. Typing the IP address in a browser, opening it in Windows network neighborhood or pinging it uses direct (unicast) traffic instead. So a NAS can be fully reachable by web page, file share and ping while staying invisible to Qfinder Pro, because something on the network path blocks or filters the broadcast packets.

First: did the NAS finish booting?

If the NAS stopped appearing after a firmware update or a power event, QNAP's newer FAQ says to confirm it actually boots before anything else. QNAP describes two beeps in a normal start:

Only after the second beep can the NAS be expected to appear on the network and in Qfinder Pro. QNAP says to give it up to 10 minutes before concluding the second beep never comes.

The NAS works by IP but Qfinder Pro can't see it: QNAP's order

  1. Firewall or antivirus on the computer. QNAP calls this the most common cause. Temporarily disable Windows Defender Firewall or any third-party antivirus or firewall and try Qfinder Pro again. If the NAS appears, add QfinderPro.exe to the firewall's allowed apps, with both the Private and Public network profiles checked.
  2. Different subnets, or a router isolating traffic. If the computer is on Wi-Fi and the NAS is wired, some routers and access points turn on AP Isolation or separate VLANs by default. Direct IP traffic may still work while broadcast packets are dropped. Compare the two IP addresses; QNAP's example of different subnets is 192.168.1.5 and 192.168.5.10. Disable AP Isolation or Wireless Isolation on the router, or connect both to the same switch or the same router's LAN ports.
  3. QuFirewall on the NAS. If the QuFirewall app is installed, its rules may block broadcast traffic or treat the computer's IP as untrusted, for example over a VPN. Log in to QTS or QuTS hero by IP, go to Control Panel > Security > QuFirewall and disable it temporarily to confirm. If that was the cause, add a rule that sets the computer's local subnet (QNAP's example: 192.168.1.0/24) to Allow.
  4. Virtual network adapters on the computer. VMware, VirtualBox and VPN clients add virtual adapters, and Qfinder Pro can send its discovery broadcasts out of one of those instead of the real network card. In Qfinder Pro, go to Settings > Network Interface and select the physical Ethernet or Wi-Fi adapter on the NAS's network.
  5. An invalid third-party App Center repository. Leftover XML data from a third-party repository that is no longer valid (QNAP's example is an old Qnapclub source) can make Qfinder Pro fail while reading the device information. Log in to the NAS, open App Center, click the gear icon, open the App Repository tab, remove any inactive or unreachable third-party repositories, and try Qfinder Pro again.

QNAP also suggests a direct connection test: one Ethernet cable from the computer to the NAS, to rule out the router and network.

The NAS is on another subnet: add it by IP

QNAP says Qfinder Pro can only discover a NAS on the same subnet as the computer, which is common in offices, dual-router setups and VLANs. If you know the NAS's IP address (from the router's DHCP client list, or by logging in locally with a monitor and keyboard), add it by hand:

  1. Open Qfinder Pro and click the + (Add Device) icon, or go to Tools > Add Device Manually.
  2. Set Category to NAS and enter the IP address.
  3. Keep port 443 if HTTPS is enabled; otherwise use 8080 for HTTP. Optionally check Enable secure connection (HTTPS), and enter a device name, username and password if you want to connect immediately.
  4. Click Add.

QNAP's tip: make sure the NAS and the computer can ping each other across the subnets.

You can still use the NAS meanwhile

QNAP points out that Qfinder Pro is mainly for first setup, finding an unknown IP, changing the NAS IP and mass Wake-on-LAN. If you know the IP, open http://<NAS-IP>:8080 or https://<NAS-IP>:443 in a browser, or \\<NAS-IP> in Windows File Explorer for the shared folders.

When to stop and get help

If the second beep never comes, QNAP's next test is to power off, unplug, label each drive with its bay number, remove all drives and start the NAS empty. Both beeps with no drives means the NAS hardware and base firmware work and the problem is with the drives or the system on them: reinsert the drives in their original order and contact QNAP Support. No second beep even with no drives points to a hardware or firmware fault, and QNAP says to contact support for repair or RMA. Take a photo of the front-panel LEDs after at least 5 minutes for the ticket. QNAP also warns not to initialize the NAS or the disks if Qfinder Pro or the web page offers it and you still need the data, because initialization erases the configuration and data.

Questions

Why can I open my QNAP NAS by IP but Qfinder Pro can't find it?

QNAP says Qfinder Pro uses broadcast/multicast discovery, while browser, file-share and ping access use direct unicast traffic. Something on the path, most often a firewall or antivirus on the computer, can block the broadcasts while direct traffic still works.

How do I add a QNAP NAS to Qfinder Pro manually?

Click the + (Add Device) icon or go to Tools > Add Device Manually, choose NAS, enter the IP address, keep port 443 for HTTPS or use 8080 for HTTP, and click Add. QNAP says this is the fix when the NAS and computer are on different subnets.

How long after power-on should Qfinder Pro see the NAS?

QNAP says a normal start gives a first beep within seconds and a second beep about 3 to 5 minutes after power-on. Only after the second beep can Qfinder Pro be expected to detect it. QNAP says to allow up to 10 minutes.

Sources

Every fact on this page comes from the vendor documents below, opened on 2026-11-16.