Apparently, the Equallogic group manager doesn't even log the Starwind Initiator's attempt. All we have to go on is the Initiators error message on the Windows client side: "Creation of iSCSI device failed with all the addresses supplied by the server." Are our iSCSI target names too long?...

#1 I pressed the 'save' as draft button by mistake, then changed my mind, and then clicked 'submit'. Which resulted in no post at all. #2 OK, I'm looking at the log on the eQuallLogic and the plot thickens: it shows a successful login from Startport, and then a logout... Maybe this is because Starpo...

So now one of my post disappeared?

Let's type it out again:

The reason we are trying Starport is that we are troubleshooting bandwidth/IO issues.

But the reason for this thread is that we are foxed that we can't figure out how to connect with Starport?

Right, let's try that log again... I noticed the error messages this time: erm... which extensions *are* allowed? So let's try this <Code> button: 6/13 17:51:24.457 CMainFrame::PoolingServiceEvents: Event checking failed, status == 2 6/13 17:51:24.863 CMainFrame::PoolingServiceEvents: Event checking...

We have a working iSCSI SAN, an EquallLogic, 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 attached.