Hi @JP²,
Welcome to Microsoft Q&A forum.
Regarding the issue that the iSCSI initiator sees the target connected but the disk is not showing in Disk Management, the issue may happen from some causes for need to troubleshoot.
Please follow these 3 first troubleshooting steps and please update me on the outcomes:
- Verify LUN Mapping and Access on the QNAP
- Even if the status shows "Connected," the specific LUN may not be properly assigned.
- Ensure the LUN is not only mapped to the target but that the Initiator IQN of your workstation has explicit permission to access that specific LUN in the QNAP storage settings.
- Match CHAP Authentication
- Event 20 in your logs often points to authentication mismatches.
- Confirm that the Target secret on the QNAP matches exactly in the iSCSI Initiator Properties under the "Advanced" settings. I suggest disabling CHAP temporarily on both ends to rule out credential errors.
- Check MTU and Jumbo Frames Configuration
- Consistent MTU is vital for iSCSI stability. Ensure the MTU is the same across the QNAP, the network switch, and your workstation.
- I recommend setting all devices to 1500 initially to establish a stable data link and prevent the connection resets indicated by Event 70.
Kindly update the outcome to let me further check if the problem persists.