Page 1 of 1

Cant connect to ISCSI target

Posted: Wed Nov 18, 2009 6:42 pm
by doubledownn24
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.

The member server shows these eventid's:

Log Name: System
Source: iScsiPrt
Date: 11/18/2009 10:37:35 AM
Event ID: 70
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: SEADC0.teameric.com
Description:
Error occurred when processing iSCSI logon request. The request was not retried. Error status 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">70</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2009-11-18T18:37:35.071928300Z" />
<EventRecordID>2955</EventRecordID>
<Channel>System</Channel>
<Computer>SEADC0.teameric.com</Computer>
<Security />
</System>
<EventData>
<Data>\Device\RaidPort0</Data>
<Binary>000004000100000000000000460000C0000000000000000000000000000000000000000000000000200100C0</Binary>
</EventData>
</Event>


Log Name: System
Source: iScsiPrt
Date: 11/18/2009 10:37:35 AM
Event ID: 1
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: SEADC0.teameric.com
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="2009-11-18T18:37:35.071928300Z" />
<EventRecordID>2954</EventRecordID>
<Channel>System</Channel>
<Computer>SEADC0.teameric.com</Computer>
<Security />
</System>
<EventData>
<Data>\Device\RaidPort0</Data>
<Binary>000006000100000000000000010000C0000000000000000000000000000000000000000000000000BC0CC0A8016F</Binary>
</EventData>
</Event>

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 target portal *192.168.1.111 0003260 Root\ISCSIPRT

Re: Cant connect to ISCSI target

Posted: Wed Nov 18, 2009 6:44 pm
by doubledownn24
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 target portal *192.168.1.111 0003260 Root\ISCSIPRT000_0 .
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="MSiSCSI" />
<EventID Qualifiers="0">113</EventID>
<Level>3</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2009-11-18T18:37:35.000000000Z" />
<EventRecordID>2953</EventRecordID>
<Channel>System</Channel>
<Computer>SEADC0</Computer>
<Security />
</System>
<EventData>
<Data>0xefff0003</Data>
<Data>*192.168.1.111 0003260 Root\ISCSIPRT000_0 </Data>
</EventData>
</Event>

Re: Cant connect to ISCSI target

Posted: Wed Nov 18, 2009 7:16 pm
by doubledownn24
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).

Re: Cant connect to ISCSI target

Posted: Wed Nov 18, 2009 7:37 pm
by doubledownn24
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.

Re: Cant connect to ISCSI target

Posted: Thu Nov 19, 2009 1:40 pm
by Robert (staff)
We actually allow users chose both the ports and the firewall settings, so, in case one decides to actually choose a different port, we are not hard coding it to the program.

Thanks.