Forum Discussion
Multiple Namespace Detection in Windows NVMe Over TCP Initiator
We are evaluating the Windows NVMe Initiator and have observed an issue with namespace handling. Our NVMe subsystem contains multiple namespaces. When we connect to the subsystem over TCP and establ...
Hi, I’d test with unique subsystem names, updated target firmware, and the latest Windows build available to you. If Windows still exposes only the first namespace, it may be a current initiator limitation or a bug in how the namespaces are being mapped. The most helpful thing to provide Microsoft would be your target config, connection commands, and screenshots of what Windows sees