NAS Codex › QNAP › iSCSI initiator can't connect to the iSCSI target on a QNAP NAS
iSCSI initiator can't connect to the iSCSI target on a QNAP NAS
An iSCSI target on a QNAP NAS can stop accepting connections even though every other NAS service is running. QNAP documents a specific cause for this after upgrading to QTS 5.0 or QuTS hero h5.0, a related problem with virtual switches, and the basic setup checks (CHAP and LUN mapping) that stop an initiator from connecting.
Written against: iSCSI & Fibre Channel on QTS 5.0 / QuTS hero h5.0 or later (QNAP FAQs last modified 2022-06-24 and 2023-09-07; tutorial last modified 2023-07-20). 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
If the target stopped working after a firmware update, bind it to a network interface. Open iSCSI & Fibre Channel, go to iSCSI Storage, select the target, click Action > Modify > Network Portal, select one or more interfaces with a link connection, and click Apply.
Targets that stopped working after a QTS 5.0 update
QNAP says that after upgrading from QTS 4.5 or earlier to QTS 5.0 or later (or from QuTS hero h4.5 or earlier to h5.0 or later), iSCSI initiators may no longer reach iSCSI targets on the NAS, even though all NAS services are running normally.
The cause, according to QNAP, is a network binding feature added in QTS 5.0 and QuTS hero h5.0. It lets you choose which network interfaces each iSCSI target can be reached through. Targets that existed before the update are not yet bound to any interface, so initiators cannot reach them.
- Open iSCSI & Fibre Channel and go to iSCSI Storage.
- Select the iSCSI target.
- Click Action > Modify, then Network Portal.
- Select one or more network interfaces that have a link connection.
- Click Apply. The target is now reachable through those interfaces.
When you create a new target, QNAP says the creation wizard walks you through the network binding step.
Virtual switch missing from the Network Portal list
If you use Container Station or Virtualization Station, QNAP notes that after updating from 4.5.x to 5.0.x the initiator may fail to connect through a virtual switch. iSCSI & Fibre Channel takes its Network Portal list from Network & Virtual Switch, and virtual switches created by other apps may not appear if they don't use the standard naming (Virtual Switch 1, Virtual Switch 2).
QNAP's fix is to create a new virtual switch in Network & Virtual Switch (Advanced > Network > Virtual Switch > Add), then select it under the target's Network Portal setting. Initiators then connect using the new virtual switch's IP address.
Check CHAP and LUN mapping
- CHAP: if you set up CHAP authentication on the target, QNAP's tutorial says the target shows as Inactive in Windows iSCSI Initiator until you enter the credentials. Select the target, click Connect > Advanced, tick Enable CHAP log on, enter the CHAP username as the Name and the CHAP password as the Target Secret.
- LUN mapping: a LUN must be mapped to a target before initiators can use it. Check Storage & Snapshots > iSCSI Storage > iSCSI Target List, where mapped LUNs appear nested under their target.
- Port: QNAP's Linux example uses the default iSCSI port, 3260.
- Thin-provisioned LUNs: QNAP notes that QTS cannot save data to a thin LUN if its storage pool runs out of space.
Connect from Windows
- Open iSCSI Initiator.
- Under Targets, enter the NAS IP address and click Quick Connect.
- Add CHAP credentials if the target uses them.
- Once the target is Connected, format the LUN as a disk in Windows.
When to stop and get help
QNAP warns that connecting more than one initiator to the same target might result in data loss or damage to the NAS disks.
Questions
Why did my QNAP iSCSI target stop working after updating to QTS 5?
QNAP says QTS 5.0 added network binding for iSCSI targets, and existing targets are not bound to any interface after the update. Bind each target under iSCSI & Fibre Channel > iSCSI Storage > Action > Modify > Network Portal.
Why does my QNAP iSCSI target show Inactive in Windows?
QNAP says a target with CHAP authentication shows Inactive until you enable CHAP log on and enter the CHAP username and password in Windows iSCSI Initiator.
Can two computers connect to the same QNAP iSCSI target?
QNAP warns that connecting more than one initiator to the same target might result in data loss or damage to the NAS disks.
Sources
Every fact on this page comes from the vendor documents below, opened on 2026-11-17.