Ardis + StarPort = BSOD

[MaxBurn]

Hi,

I'm using Linux iSCSI targets available for years: iUNH from www.unh-iscsi.sourceforge.net and Ardis from www.ardistech.com. UNH works great but when I use StarPort to connect to Ardis target I'm immediately getting BSOD. Configuration does not matter. CHAP is not used. What's wrong?

Best wishes,
Maxi

[Val (staff)]

Maxi,

Thank you for the information.

We have tested StarPort with UNH iSCSI target for a long time. So there is no problems.

We have been notified about the Starport's problem with Ardis iSCSI target for Linux.

Now we are releasing a new StarPort version where this bug fixed (beside some other bugfixes and enhancements).

[skyaurum]

Hi,

I'm trying to connect Linux iSCSI target from Starport.

When I try to connect Remote iSCSI devices from Starport,
the error message occured in last stage.

In Device Installation Complete Dialog Box, the error message as follows,

"The following virtual device was installed:
No device description
An error occured during installation of the device.
Creation of the iSCSI device failed with all the
addresses supplied by the server."

And your log message as follows,
2/26 9:08:58 3b4 ntsrv: StarPort Service v3.5 (Build 20080111, WinXP x86)
2/26 9:08:58 3b4 Srv: No bound volumes found.
2/26 9:08:58 3b4 Srv: Service started.

Could you tell me what the problem is?

Best regards,
Skyaurum

[Val (staff)]

I'm trying to connect Linux iSCSI target from Starport.

When I try to connect Remote iSCSI devices from Starport,
the error message occured in last stage.

Could you tell me what the problem is?

Hi, Skyaurum!

It seems to be some issue in the iSCSI connaction negotiation.

Please send us a network dump file for a connection attempt with Wireshark (filter it by TCP port 3260).
It should answer the question why it fails and allow us to fix the issue...

Thank you.