Resolved. You have to manually add 3260/3261 inbound ports to Windows Firewall to access Starwind ISCSI Targets. This should be done automatically during install.

More info: Installing Starwind on the second computer and trying to connect to the service running on the host, it is saying "Starwind Service Not Found" Again, ISCSI and Starwind ports on inbound and outbound are setup properly (as far as I can tell, whatever the default installation does).

Oops, my message got cut off: Here is the third Event ID Log Name: System Source: MSiSCSI Date: 11/18/2009 10:37:35 AM Event ID: 113 Task Category: None Level: Warning Keywords: Classic User: N/A Computer: SEADC0 Description: iSCSI discovery via SendTargets failed with error code 0xefff0003 to targe...

Running Starwind 5.0 on Windows 2008 R2 64Bit On the local machine I can ISCSI initiator to my targets on Starwind. On my member server I can not connect to Starwind targets. It doesn't show up when using ISCSI initiator and specifying the named host for my starwind targets, or just auto discovering...

I am getting this same exact problem.

Windows 2008 R2 64Bit
Starwind 4.0 build 20090212

If I power the computer off, then back on, the images go to non-active and there is no way to get them to go active without deleting and re-adding.