Kevin, I've done this repeatedly over the last several weeks and I have always been able to see the replica. Other than a license issue, there is no reason why you should not be able to see at least one network interface from both servers. I would avoid using direct attach until you can see interfac...

Have you tried deleting the image file and creating another? (delete files on disk too)

You have to "Add support for iSCSI devices" under the Discover Multi-Paths tab. Click Add and your server will restart. You may have a license issue on one of your nodes. You don't have to Discover Portals until you get ready to create a cluster. You only have to run the Initiator service ...

My guess... 1. IP's on replica server not on the same subnet. 2. Different VLANs or VLAN trunk issue. 3. Firewall blocking port 3261 on the specific interfaces. 4. iSCSI initiator service not started on one of the servers. 5. MPIO not installed or initialized on one of the servers. Make sure the pri...

The NFR license resolved the issue. However, it is not for production use and is only good for one year.

I flipped on the NFR license for this prototype and the iSCSI images became visible to the VMware host. The free version only supports iSCSI as a standalone target. This doesn't do me much good because all of the servers are configured for iSCSI MPIO and NFS would be a mess to reconfigure on my netw...

build 8730 killed the iSCSI target to VMware as soon as I added a replica even with a different adapter that is not used for sync or heartbeat. This is a simple 2 server C&SS config without MS clustering. I created another image device without the replica and VMware sees it fine. The replicated ...

If I understand you correctly, you have removed the iSCSI target capability from the Starwind host. Is that just for a hyper-converged configuration or does that include Compute and Storage Separated as well? A lot of storage vendors are using NFS on their storage boxes but still include the MPIO iS...