StarWind Software

Hi all,

I have installed Starwind iSCSI SAN & NAS ond two servers. With the iSCSI Initiator i can connect to the second server, but not to the other server. In the EventViewer i see the following ID's:

Log Name: System
Source: iScsiPrt
Date: 2/10/2014 23:50:27
Event ID: 10
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: RDDC.FUTURE.local
Description:
Login request failed. The login response packet is given in the dump data.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="iScsiPrt" />
<EventID Qualifiers="49152">10</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-02-10T22:50:27.698508000Z" />
<EventRecordID>20388</EventRecordID>
<Channel>System</Channel>
<Computer>RDDC.FUTURE.local</Computer>
<Security />
</System>
<EventData>
<Data>\Device\RaidPort1</Data>
<Binary>0000900001000000000000000A0000C0000000000000000000000000000000000000000000000000230000000000000040000137000000000000000100000000000000000000000000000000030100000000000000000000690071006E002E0032003000300038002D00300038002E0063006F006D002E007300740061007200770069006E00640073006F006600740077006100720065003A003100320037002E0030002E0030002E0031002D006E006F00640065003100</Binary>
</EventData>
</Event>

Log Name: System
Source: iScsiPrt
Date: 2/10/2014 23:51:17
Event ID: 1
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: RDDC.FUTURE.local
Description:
Initiator failed to connect to the target. Target IP address and TCP Port number are given in dump data.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="iScsiPrt" />
<EventID Qualifiers="49152">1</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-02-10T22:51:17.083118100Z" />
<EventRecordID>20390</EventRecordID>
<Channel>System</Channel>
<Computer>RDDC.FUTURE.local</Computer>
<Security />
</System>
<EventData>
<Data>\Device\RaidPort1</Data>
<Binary>000006000100000000000000010000C0000000000000000000000000000000000000000000000000BC0C0A000001</Binary>
</EventData>
</Event>

I have disabled the Windows Firewall on all servers. Hoe can i fix this issue?

In the serverlog of the iSCSI Target, i see the following:

2/10 23:56:01.062 a74 HA: CHADevice::RegisterSession: Client initiator iqn.1991-05.com.microsoft:rddc.future.local try to register session for target 'iqn.2008-08.com.starwindsoftware:127.0.0.1-node1'...
2/10 23:56:01.062 a74 HA: CHADevice::RegisterSession: Client session can't be registered because node is not active!
2/10 23:56:01.062 a74 HA: CHADevice::RegisterSession: Return code 21.
2/10 23:56:01.062 a74 Tgt: *ERROR* 'iqn.2008-08.com.starwindsoftware:127.0.0.1-node1' can't register session. The device 'HAImage1' may be owned by a local process!
2/10 23:56:01.062 a74 T[2f,1]: *ERROR* Login request: device open failed.
2/10 23:56:01.062 684 C[2f], IN_LOGIN: Event - LOGIN_REJECT.
2/10 23:56:01.062 684 C[2f], FREE: T7.
2/10 23:56:01.062 a74 C[2f], FREE: recvData returned 10054
2/10 23:56:06.061 a58 Srv: Accepted iSCSI connection from 192.168.18.2:54242 to 192.168.18.3:3260. (Id = 0x30)
2/10 23:56:06.061 a58 C[30], FREE: Event - CONNECTED.
2/10 23:56:06.061 a58 C[30], XPT_UP: T3.
2/10 23:56:06.061 92c C[30], XPT_UP: Login request: ISID 0x400001370000, TSIH 0x0000.
2/10 23:56:06.061 92c C[30], XPT_UP: Event - LOGIN.

Hi! Sorry to heat that you`re in trouble.
Can you confirm that the starwind service is started on the remote server that you are trying to connect to?

Yes, I can confirm that at the time of issue, the services were started. That's the first I've checked. Strangely, the problem is solved. I have changed nothing, just a few hours waiting,

Thank you for the heads up!
I think that the problem was caused by the synchronization process - the service was too busy by that, so he was not able to process requests from the console.
I have one more guess - can you confirm that your starwind is not up to date?

Thanks for the respone, what's tje workaround for this issue? Today the again the same as yesterday. When i come back from my work to test the connection, i can connect now to the iSCSI Target. On both servers i am running version 6.0.5713

Good question. Actually if the only problem is that you cannot connect to the targets with the console, then the best workaround is to wait untill the end of synchronization.
Please let me know if there is anything else.

I appear to have the same issue in version 8.0.7509 and it occurs after a reboot. If I leave it for a couple of hours it will connect up again. Any ideas on what the issue could be?

Can you confirm that the target is inaccessible before the synchronization is over?