Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We have a working iSCSI SAN, an Equallogic, which runs fine with the Microsoft iSCSI initiator.

With the Starport Initiator, we can't even connect. There's no login needed, neither local nor LDAP.

Any ideas?

The log is swamped with these:

6/13 17:51:37.842 CMainFrame::PoolingServiceEvents: Event checking failed, status == 2

Here's the relevant bits of the log:

6/13 17:51:29.699 CWPPiSCSITargetSelection::CreateDevice: Trying to add an iSCSI device using, IP:0xA060101, Port:3260
6/13 17:51:29.699 >> CStarPortAPI::CStarPortAPI()
6/13 17:51:29.699 >> CStarPortAPI::DriverOpen()
6/13 17:51:29.699 >> CStarPortAPI::DriverVersion(...)
6/13 17:51:29.699 CStarPortAPI::DriverVersion: Calling STARPORT_IOCTL_GET_VERSION
6/13 17:51:29.699 CStarPortAPI::DriverVersion: Calling DeviceIoControl(...)
6/13 17:51:29.699 CStarPortAPI::DriverVersion: Input: ApiVersion = 30001
6/13 17:51:29.699 CStarPortAPI::DriverVersion: Output: Version = 20110316, API = 30001, DriverOpenContext = 0, DriverInstance = FFFFFA8005844B90 
6/13 17:51:29.699 CStarPortAPI::CStarPortAPI: StarWind iSCSI Initiator version: 20091223; StariSCSI driver: API v30001, Build 0x20110316
6/13 17:51:29.699 >> CStarPortDoc::CreateiSCSIDevice(IP=0x26E6CE0, Port=3260,, Flags=0)
6/13 17:51:29.699 >> CStarPortAPI::InsertiSCSIDevice(dwIPAddress=0xA060101, dwPort=3260,,, szAdditionalParameter=, nTargetID=...)
6/13 17:51:29.699 CStarPortAPI::InsertiSCSIDevice: Calling STARPORT_IOCTL_TARGET_MOUNT
6/13 17:51:29.699 CStarPortAPI::InsertiSCSIDevice: Input buffer:
6/13 17:51:29.699 CStarPortAPI::InsertiSCSIDevice: Flags = 0
6/13 17:51:29.699 CStarPortAPI::InsertiSCSIDevice: ServerAddress = #iscsi:
6/13 17:51:29.699 CStarPortAPI::InsertiSCSIDevice: Parameter[0] =
6/13 17:51:29.699 CStarPortAPI::InsertiSCSIDevice: Parameter[1] =

and then of course

6/13 17:51:38.731 CStarPortAPI::InsertiSCSIDevice: Session failed, status == 1326 !
6/13 17:51:38.731 >> CStarPortAPI::~CStarPortAPI()
6/13 17:51:38.731 CWPPiSCSITargetSelection::CreateDevice: Exception caught: Logon to the server failed.
6/13 17:51:38.731 CWPPiSCSITargetSelection::CreateDevice: Failed to connect to create iSCSI device using, IP:0xA060101, Port:3260
6/13 17:51:38.731 CWPPiSCSITargetSelection::CreateDevice: Creation of the iSCSI device failed with all the addresses supplied by the server.
6/13 17:51:38.731 CWPPiSCSITargetSelection::CreateDevice: Exception caught: Creation of the iSCSI device failed with all the addresses supplied by the server.
share|improve this question
Stupid question, but have you asked either Dell or Starwind what they make of the event logs? – Brent Pabst Sep 18 '12 at 18:41
Dell can't help because nothing shows in the EqualLogic logs, and Starwind insists it's a handshake problem on the Dell side... – DutchUncle Sep 20 '12 at 19:29
I suspect this is the key to the Initiator's problem: "Creation of the iSCSI device failed with all the addresses supplied by the server." – DutchUncle Sep 20 '12 at 19:35
Should we shorten/change the target names? – DutchUncle Sep 20 '12 at 19:35

Is your initiator with name IQN actually mapped/zoned to access the LUNs at target IQN on that target?

share|improve this answer
The Starwind IQN is generated by the Starwind Initiator itself. Can I check/force it anywhere? – DutchUncle Sep 20 '12 at 19:33
Sure, your Equallogic box should have a mapping/zoning configuration setup. – pfo Sep 24 '12 at 14:02
up vote 0 down vote accepted

Turns out we DO have some kind of login/password set in the eQuallogic setup... but only the Starwind client seems to pickup on it...

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.