Hi,

there is no such string....
But on my testing machine i found this: <transport value="auto"/>

On our productive starwind-nodes we are running 5.8, updated from 5.6. On these machines ms-iscsi-service is running and populated with the partner iscsi-targets. I have built up a test environment with 5.8: no ms-iscsi-service running. So the initiator must be in starwind itself. Maybe the ms-initi...

Hi ! Our current Version "StarWind iSCSI SAN Software v5.8.0 (Build 20120124, [SwSAN], Win64)" AKA 5.8.1889 (obviously not the most recent one). Do we need an Full - sync after a minor release upgrade ? Regarding "The target did not respond in time to a task management request." ...

Hi Max,
We are using the Windows ISCSI initiator(default by starwind installation by 5.6).
There is a seperate direct line for starwind synchronisation (10Gb).
Client storage is also a seperate line (2x1000MBit Intel), this line is also used for heartbeat.

Hi, after update to 5.8, we are getting this in our eventlog all the time (translated...;) ): - The target did not respond in time to a task management request. - The target has not responded to a SCSI request in time. CDB information contained in the backup data. - Target or LUN can not be reset. I...