StarWind Software

Hello,

I was able to connect with the Starport initiator to my Starwind target.
However, when I try to connect with the Microsoft iSCSI initiator 1.06, I receive the error "a non specific error occured" (typical non descriptive error from Microsoft...).

Do you have any idea what is wrong ?

Thanks,

Niko

You need to send StarWind logs to support. W/o it it's nearly impossible to say what's wrong with MS junkware. You could have CHAP enabled, IQN blacklisted, wrong session discovery (to the different target) happending etc etc etc. Please try again and send us latest .log from StarWind \Logs folder. Then we'll be able to help you in sorting the issue out

niko wrote:Hello,

I was able to connect with the Starport initiator to my Starwind target.
However, when I try to connect with the Microsoft iSCSI initiator 1.06, I receive the error "a non specific error occured" (typical non descriptive error from Microsoft...).

Do you have any idea what is wrong ?

Thanks,

Niko

Dear Anton,

As requested, these are the logs on the target, after connecting with the Microsoft iSCSI initiator 1.05 or 1.06 (both same result):

08:07:54:525 (454) Srv: Accepted connection from 192.168.6.158:1339. id assigned - 4372
08:07:54:525 (454) C[0x1114], FREE: Event - CONNECTED.
08:07:54:525 (454) C[0x1114], XPT_UP: T3.
08:07:54:525 (acc) C[0x1114], XPT_UP: Login request: ISID 0x400001370000, TSIH 0x0000.
08:07:54:525 (acc) C[0x1114], XPT_UP: Event - LOGIN.
08:07:54:525 (acc) C[0x1114], IN_LOGIN: T4.
08:07:54:525 (acc) Params: <<< String param 'InitiatorName': received 'iqn.1991-05.com.microsoft:test', accepted 'iqn.1991-05.com.microsoft:test'
08:07:54:525 (acc) Params: <<< Enum param 'SessionType': received 'Discovery', accepted 'Discovery'
08:07:54:525 (acc) Params: <<< Enum param 'AuthMethod': received 'None', accepted 'None'
08:07:54:525 (acc) Params: Update OFMarkInt according to the value of OFMarker.
08:07:54:525 (acc) Params: Update IFMarkInt according to the value of IFMarker.
08:07:54:525 (acc) Params: <<< Enum param 'AuthMethod': received 'None', accepted 'None'
08:07:54:525 (acc) T[0x1]: Anonymous connection allowed.
08:07:54:525 (acc) Params: >>> AuthMethod=None.
08:07:54:525 (d04) T[0x1]: The end of stage 0, next stage is 1.
08:07:54:525 (acc) Params: <<< Enum param 'HeaderDigest': received 'None', accepted 'None'
08:07:54:525 (acc) Params: <<< Enum param 'DataDigest': received 'None', accepted 'None'
08:07:54:525 (acc) Params: <<< Numeric param 'ErrorRecoveryLevel': received 0, accepted 0
08:07:54:525 (acc) Params: <<< Numeric param 'MaxRecvDataSegmentLength': received 65536, accepted 65536
08:07:54:525 (acc) Params: <<< Numeric param 'DefaultTime2Wait': received 5, accepted 5
08:07:54:525 (acc) Params: <<< Numeric param 'DefaultTime2Retain': received 5, accepted 5
08:07:54:525 (acc) Params: >>> ErrorRecoveryLevel=0.
08:07:54:525 (acc) Params: >>> HeaderDigest=None.
08:07:54:525 (acc) Params: >>> DataDigest=None.
08:07:54:525 (acc) Params: >>> InitialR2T=No.
08:07:54:525 (acc) Params: >>> ImmediateData=Yes.
08:07:54:525 (acc) Params: >>> MaxRecvDataSegmentLength=65536.
08:07:54:525 (acc) Params: >>> MaxBurstLength=262144.
08:07:54:525 (acc) Params: >>> FirstBurstLength=65536.
08:07:54:525 (acc) Params: >>> DefaultTime2Wait=5.
08:07:54:525 (acc) Params: >>> DefaultTime2Retain=5.
08:07:54:525 (acc) Params: >>> MaxOutstandingR2T=1.
08:07:54:525 (acc) Params: >>> DataPDUInOrder=Yes.
08:07:54:525 (acc) Params: >>> DataSequenceInOrder=Yes.
08:07:54:525 (d04) T[0x1]: The end of stage 1, next stage is 3.
08:07:54:525 (d04) C[0x1114], IN_LOGIN: Event - LOGIN_ACCEPT.
08:07:54:525 (d04) C[0x1114], LOGGED_IN: T5.
08:07:54:525 (d04) C[0x1114], LOGGED_IN: Event - LOGOUT.
08:07:54:525 (d04) C[0x1114], IN_LOGOUT: T9/10.
08:07:54:525 (a7c) C[0x1114], IN_LOGOUT: Event - LOGOUT_ACCEPT.
08:07:54:525 (a7c) C[0x1114], FREE: T13.

On the initiator (192.168.6.158) I select the "Target Portals" tab and click the Add button. Then I enter the IP address of the target, and I immediately get the error "a non specific error occured".

Many thanks for your help,

Niko

Hi Niko,

The partial log you sent shows only a successful Discovery session.

Could you send us a complete log file where all the session logs are shown?

The MS initiator v1.06 works with our StarWind without any problems.
Maybe there is some issue with the MS initiator...

Hello Valery,

In order to provide you with a complete logfile, I have done the following:
1. I stopped the Starwind service on the target
2. I deleted all log files (under C:\Program Files\StarWind\logs)
3. I started the Starwind service
4. I tried to connect with the MS iSCSI initiator (which gives the error mentioned in my post above)
5. I stopped the Starwind service to unlock the logfile
6. Here is the whole content of the one logfile which was created:

12:25:39:892 (224) Srv: StarWind iSCSI Target Version 2.6.0 (Build 0x20050314, Win32)
12:25:39:892 (224) Srv: *** TRIAL VERSION *** [ expires in 14 day(s) ]
12:25:39:892 (224) Srv: Please contact Rocket Division Software at <info@rocketdivision.com> for more details.
12:25:39:892 (224) Srv: Unlimited number of client hosts allowed.
12:25:39:892 (224) Srv: Config file: 'C:\Program Files\StarWind\starwind.conf'
12:25:39:923 (224) conf: 'LogLevel' = '1'
12:25:39:923 (224) conf: 'LogMask' = '0x8fffffff'
12:25:39:923 (224) conf: 'Port' = '3260'
12:25:39:923 (224) conf: 'Interface' = '0.0.0.0'
12:25:39:923 (224) conf: 'DefTargetName' = 'iqn.2003-06.com.rocketdivision.starwind:$(host).$(symid)'
12:25:39:923 (224) conf: 'Login' = 'test'
12:25:39:923 (224) conf: 'Password' = '##CY9rzUYh03PK3k6DJie09g=='
12:25:39:923 (224) conf: 'Echo' = 'no'
12:25:39:923 (224) conf: 'MinBufferSize' = '65536'
12:25:39:923 (224) conf: 'AlignmentMask' = '0x0000'
12:25:39:923 (224) conf: 'MaxPendingRequests' = '64'
12:25:39:923 (224) conf: Variable 'LogLevel' is set to '1'.
12:25:39:923 (224) conf: Variable 'LogMask' is set to '0x8fffffff'.
12:25:39:923 (224) conf: Variable 'Port' is set to '3260'.
12:25:39:923 (224) conf: Variable 'Interface' is set to '0.0.0.0'.
12:25:39:923 (224) conf: Variable 'DefTargetName' is set to 'iqn.2003-06.com.rocketdivision.starwind:$(host).$(symid)'.
12:25:39:923 (224) conf: Variable 'Login' is set to 'test'.
12:25:39:923 (224) conf: Variable 'Password' is set to '##CY9rzUYh03PK3k6DJie09g=='.
12:25:39:923 (224) conf: Variable 'Echo' is set to 'no'.
12:25:39:923 (224) conf: Variable 'MinBufferSize' is set to '65536'.
12:25:39:923 (224) conf: Variable 'AlignmentMask' is set to '0x0000'.
12:25:39:923 (224) conf: Variable 'MaxPendingRequests' is set to '64'.
12:25:39:939 (224) conf: 'RamDisk.dll' loaded successfully.
ImageFile[224] SscPort_Init: Parse ImageDir: 'd:\|cdfv|images|img'
ImageFile[224] SscPort_Init:
Dirname: 'd:\'
Rights: 0xffffffff
Alias: 'images'
Extensions: 'img'
ImageFile[224] SscPort_Init: Comment : ''
12:25:39:970 (224) conf: 'ImageFile.dll' loaded successfully.
VirtualDVD[224] SscPort_Init: Parse ImageDir: 'images|v|images|mds,iso'
Sw:[224] Browser_DirCreate: Mask mismatch (ff / ff000000)
Sw:[224] Browser_DirDelete: Mask mismatch (ff / ff0000)
Sw:[224] Browser_DirCreateFolder: Mask mismatch (ff / ff00)
VirtualDVD[224] SscPort_Init:
Dirname: 'C:\Program Files\StarWind\images'
Rights: 0xff
Alias: 'images'
Extensions: 'mds,iso'
VirtualDVD[224] SscPort_Init: Comment : ''
12:25:39:970 (224) conf: 'VirtualDvd.dll' loaded successfully.
12:25:39:970 (224) S: the device 'RamDrive0' is opened successfully.
12:25:39:970 (224) S: Assigned target name: 'iqn.2003-06.com.rocketdivision.starwind:dct-syvev76s699.ramdisk.ramdrive0', SymId: 'RAMdisk.RamDrive0'.
12:25:39:970 (224) S: parameter 'size', value '16'.
12:25:39:970 (224) S: parameter 'format', value 'yes'.
12:25:39:970 (224) S: clustered 0.
12:25:39:970 (224) S: iqn.2003-06.com.rocketdivision.starwind:dct-syvev76s699.ramdisk.ramdrive0: 1 session(s) allowed.
12:25:39:970 (224) conf: Target [0x9b7f8] has been created. Device 'RamDrive0' is accesible as target 'iqn.2003-06.com.rocketdivision.starwind:dct-syvev76s699.ramdisk.ramdrive0'.
12:25:39:985 (224) S: the device 'ImageFile0' is opened successfully.
12:25:39:985 (224) S: Assigned target name: 'starwind_100gb_imagefile', SymId: 'Imagefile.ImageFile0'.
12:25:39:985 (224) S: parameter 'header', value '0'.
12:25:39:985 (224) S: parameter 'file', value 'd:\image_100GB.img'.
12:25:39:985 (224) S: parameter 'buffering', value 'no'.
12:25:39:985 (224) S: clustered 0.
12:25:39:985 (224) S: parameter 'asyncmode', value 'no'.
12:25:39:985 (224) S: starwind_100gb_imagefile: 1 session(s) allowed.
12:25:39:985 (224) conf: Target [0x9c2d0] has been created. Device 'ImageFile0' is accesible as target 'starwind_100gb_imagefile'.
12:25:39:985 (224) Srv: Refreshing device list (complete)...
12:25:40:985 (224) Srv: A new SPTI device '\\.\F:' found.
12:25:40:985 (224) SPTI: '\\.\PhysicalDrive0': Test failed, the device cannot execute SCSI command. Status 0, SCSI status 0x0.
12:25:40:985 (224) SPTI: '\\.\PhysicalDrive1': Test failed, the device cannot execute SCSI command. Status 0, SCSI status 0x0.
12:25:41:001 (224) Srv: (FREE) Binding to 0.0.0.0:3260 ...
12:25:41:017 (224) Srv: Waiting for a connection at port 0.0.0.0:3260 ...
12:25:41:017 (be0) conf: Waiting for a control connection at port 3261 ...
12:25:46:642 (224) Srv: Accepted connection from 192.168.6.158:1095. id assigned - 4370
12:25:46:642 (224) C[0x1112], FREE: Event - CONNECTED.
12:25:46:642 (224) C[0x1112], XPT_UP: T3.
12:25:46:642 (be8) C[0x1112], XPT_UP: Login request: ISID 0x801234567890, TSIH 0x0000.
12:25:46:642 (be8) C[0x1112], XPT_UP: Event - LOGIN.
12:25:46:642 (be8) C[0x1112], IN_LOGIN: T4.
12:25:46:642 (be8) Params: <<< String param 'InitiatorName': received 'iqn.2003-06.com.rocketdivision.starport:test', accepted 'iqn.2003-06.com.rocketdivision.starport:test'
12:25:46:642 (be8) Params: <<< String param 'TargetName': received 'starwind_100gb_imagefile', accepted 'starwind_100gb_imagefile'
12:25:46:642 (be8) Params: <<< Enum param 'SessionType': received 'Normal', accepted 'Normal'
12:25:46:642 (be8) Params: <<< Enum param 'AuthMethod': received 'None', accepted 'None'
12:25:46:642 (be8) Params: Update OFMarkInt according to the value of OFMarker.
12:25:46:642 (be8) Params: Update IFMarkInt according to the value of IFMarker.
12:25:46:642 (be8) S: starwind_100gb_imagefile: 1 session(s) are opened, 0 more allowed.
12:25:46:642 (be8) T[0x6464]: iSCSI parameters set according to the device's MaxTransferLength (262144)
12:25:46:642 (be8) Params: <<< Enum param 'AuthMethod': received 'None', accepted 'None'
12:25:46:642 (be8) T[0x6464]: Anonymous connection allowed.
12:25:46:642 (be8) Params: >>> AuthMethod=None.
12:25:46:642 (be8) Params: >>> TargetPortalGroupTag=1.
12:25:46:642 (bf0) T[0x6464]: The end of stage 0, next stage is 1.
12:25:46:642 (be8) Params: <<< Numeric param 'ErrorRecoveryLevel': received 0, accepted 0
12:25:46:642 (be8) Params: <<< Numeric param 'MaxConnections': received 1, accepted 1
12:25:46:642 (be8) Params: <<< Enum param 'HeaderDigest': received 'None', accepted 'None'
12:25:46:642 (be8) Params: <<< Enum param 'DataDigest': received 'None', accepted 'None'
12:25:46:642 (be8) Params: <<< Boolean param 'OFMarker': received No, accepted 0
12:25:46:642 (be8) Params: <<< Boolean param 'IFMarker': received No, accepted 0
12:25:46:642 (be8) Params: <<< Boolean param 'InitialR2T': received No, accepted 0
12:25:46:642 (be8) Params: <<< Boolean param 'ImmediateData': received Yes, accepted 1
12:25:46:642 (be8) Params: <<< Numeric param 'MaxRecvDataSegmentLength': received 65536, accepted 65536
12:25:46:642 (be8) Params: <<< Numeric param 'MaxBurstLength': received 262144, accepted 262144
12:25:46:642 (be8) Params: <<< Numeric param 'FirstBurstLength': received 65536, accepted 65536
12:25:46:642 (be8) Params: <<< Numeric param 'DefaultTime2Wait': received 5, accepted 5
12:25:46:642 (be8) Params: <<< Numeric param 'DefaultTime2Retain': received 20, accepted 20
12:25:46:642 (be8) Params: <<< Numeric param 'MaxOutstandingR2T': received 1, accepted 1
12:25:46:642 (be8) Params: <<< Boolean param 'DataPDUInOrder': received Yes, accepted 1
12:25:46:642 (be8) Params: <<< Boolean param 'DataSequenceInOrder': received Yes, accepted 1
12:25:46:642 (be8) Params: >>> ErrorRecoveryLevel=0.
12:25:46:642 (be8) Params: >>> MaxConnections=1.
12:25:46:642 (be8) Params: >>> HeaderDigest=None.
12:25:46:642 (be8) Params: >>> DataDigest=None.
12:25:46:642 (be8) Params: >>> OFMarker=No.
12:25:46:642 (be8) Params: >>> IFMarker=No.
12:25:46:642 (be8) Params: >>> InitialR2T=No.
12:25:46:642 (be8) Params: >>> ImmediateData=Yes.
12:25:46:642 (be8) Params: >>> MaxRecvDataSegmentLength=262144.
12:25:46:642 (be8) Params: >>> MaxBurstLength=262144.
12:25:46:642 (be8) Params: >>> FirstBurstLength=65536.
12:25:46:642 (be8) Params: >>> DefaultTime2Wait=5.
12:25:46:642 (be8) Params: >>> DefaultTime2Retain=20.
12:25:46:642 (be8) Params: >>> MaxOutstandingR2T=1.
12:25:46:642 (be8) Params: >>> DataPDUInOrder=Yes.
12:25:46:642 (be8) Params: >>> DataSequenceInOrder=Yes.
12:25:46:642 (bf0) T[0x6464]: The end of stage 1, next stage is 3.
12:25:46:642 (bf0) C[0x1112], IN_LOGIN: Event - LOGIN_ACCEPT.
12:25:46:642 (bf0) C[0x1112], LOGGED_IN: T5.
12:25:51:814 (224) Srv: Accepted connection from 192.168.6.158:1096. id assigned - 4371
12:25:51:814 (224) C[0x1113], FREE: Event - CONNECTED.
12:25:51:814 (224) C[0x1113], XPT_UP: T3.
12:25:51:814 (c18) C[0x1113], XPT_UP: Login request: ISID 0x400001370000, TSIH 0x0000.
12:25:51:814 (c18) C[0x1113], XPT_UP: Event - LOGIN.
12:25:51:814 (c18) C[0x1113], IN_LOGIN: T4.
12:25:51:814 (c18) Params: <<< String param 'InitiatorName': received 'iqn.1991-05.com.microsoft:test', accepted 'iqn.1991-05.com.microsoft:test'
12:25:51:814 (c18) Params: <<< Enum param 'SessionType': received 'Discovery', accepted 'Discovery'
12:25:51:814 (c18) Params: <<< Enum param 'AuthMethod': received 'None', accepted 'None'
12:25:51:814 (c18) Params: Update OFMarkInt according to the value of OFMarker.
12:25:51:814 (c18) Params: Update IFMarkInt according to the value of IFMarker.
12:25:51:814 (c18) Params: <<< Enum param 'AuthMethod': received 'None', accepted 'None'
12:25:51:814 (c18) T[0x1]: Anonymous connection allowed.
12:25:51:814 (c18) Params: >>> AuthMethod=None.
12:25:51:814 (c20) T[0x1]: The end of stage 0, next stage is 1.
12:25:51:814 (c18) Params: <<< Enum param 'HeaderDigest': received 'None', accepted 'None'
12:25:51:814 (c18) Params: <<< Enum param 'DataDigest': received 'None', accepted 'None'
12:25:51:814 (c18) Params: <<< Numeric param 'ErrorRecoveryLevel': received 0, accepted 0
12:25:51:814 (c18) Params: <<< Numeric param 'MaxRecvDataSegmentLength': received 65536, accepted 65536
12:25:51:814 (c18) Params: <<< Numeric param 'DefaultTime2Wait': received 5, accepted 5
12:25:51:814 (c18) Params: <<< Numeric param 'DefaultTime2Retain': received 5, accepted 5
12:25:51:814 (c18) Params: >>> ErrorRecoveryLevel=0.
12:25:51:814 (c18) Params: >>> HeaderDigest=None.
12:25:51:814 (c18) Params: >>> DataDigest=None.
12:25:51:814 (c18) Params: >>> InitialR2T=No.
12:25:51:814 (c18) Params: >>> ImmediateData=Yes.
12:25:51:814 (c18) Params: >>> MaxRecvDataSegmentLength=65536.
12:25:51:814 (c18) Params: >>> MaxBurstLength=262144.
12:25:51:814 (c18) Params: >>> FirstBurstLength=65536.
12:25:51:814 (c18) Params: >>> DefaultTime2Wait=5.
12:25:51:814 (c18) Params: >>> DefaultTime2Retain=5.
12:25:51:814 (c18) Params: >>> MaxOutstandingR2T=1.
12:25:51:814 (c18) Params: >>> DataPDUInOrder=Yes.
12:25:51:814 (c18) Params: >>> DataSequenceInOrder=Yes.
12:25:51:814 (c20) T[0x1]: The end of stage 1, next stage is 3.
12:25:51:814 (c20) C[0x1113], IN_LOGIN: Event - LOGIN_ACCEPT.
12:25:51:814 (c20) C[0x1113], LOGGED_IN: T5.
12:25:51:814 (c20) C[0x1113], LOGGED_IN: Event - LOGOUT.
12:25:51:814 (c20) C[0x1113], IN_LOGOUT: T9/10.
12:25:51:814 (c1c) C[0x1113], IN_LOGOUT: Event - LOGOUT_ACCEPT.
12:25:51:814 (c1c) C[0x1113], FREE: T13.
12:25:58:627 (214) ntsrv: Got SERVICE_CONTROL_STOP signal.
12:25:58:627 (be0) conf: Stop listening to control connections.
12:25:58:627 (224) Srv: Timeout 10 second(s)...
12:25:58:627 (214) C[0x1112], LOGGED_IN: Event - SHUTDOWN.
12:25:58:627 (214) C[0x1112], LOGOUT_REQUESTED: T11.
12:26:03:642 (be8) C[0x1112], FREE: *ERROR* 'recv' thread: recv failed 274a.
12:26:03:642 (bf0) S: starwind_100gb_imagefile: 0 session(s) are opened, 1 more allowed.
12:26:03:642 (224) Srv: Shutdown completed.
12:26:03:642 (224) S: the device 'RamDrive0' is closed.
12:26:03:642 (224) S: the device 'ImageFile0' is closed.

Please let me know if you need additional information.
Many thanks for your support,

Niko

Niko,

According to the log the ImageFile0 traget is already mounted by a StarPort initiator.
So it's impossible to mount it the second time. This could be the issue.

Anyway the log includes nothing abou any attempts of the MS initiator to mount a target.
I can't guarantee that the MS initiator 100% free of bugs. Maybe this is some issue of the MS initiator...

Why not to use our Starport initiator if it works good on your environment?

I had the same issue.

I checked my local storage connections on the Starwind system, then shutdown the system, and reseated my cabling. After this, I could log on with no problems.

-CJD

Do you mean the image file was not mounted before?

Crazy Joe Davola wrote:I had the same issue.

I checked my local storage connections on the Starwind system, then shutdown the system, and reseated my cabling. After this, I could log on with no problems.

-CJD

Our issue was with SPTI devices on SCSI disks. Even though we could access the SCSI disks locally without any problems.

We shutdown the system, reseated the cabling and rebooted. After that, we could log in no problem.

So, we really don't know where the problem was or what actually fixed it.

If you'll have the same problem again - please let us know! We'd like to catch this. Thank you!

Crazy Joe Davola wrote:Our issue was with SPTI devices on SCSI disks. Even though we could access the SCSI disks locally without any problems.

We shutdown the system, reseated the cabling and rebooted. After that, we could log in no problem.

So, we really don't know where the problem was or what actually fixed it.

Using Starwind 2.4.3, 2.6.1, and ms software initiator 1.06, starport 2.6.1 I found this out.


Most testing was done on clean installs of W2K3 server enterprise
using VMWare GSX Server 3.1. From clean machines to new installs of
starwind on other clean machines I found that I sometims got an error and sometimes not while using the ms initiator. However, I had a server with starwind 2.4.3 running and I could not connect to it at all, and I received an 'unspecified error' message. Well... I decided to setup an ms-iSNS server too. In the course of doing this I noticed that it was difficult to find the iqn. names of devices that I had given alias names. So I removed and the re-added the devices without the aliased iqn names so that i could write them down to enter into the isns server.

On doing this I eventually found that I could connect to the starwind server using the ms iscsi initiator without receiving an error. The error seemed to be generated by the 'friendly names', and once they were removed everthing started to work right. Note also that I did not always get an error when I connected to the starwind server, sometimes I could connect, but only see the iqn. names and not the 'friendly' names.

AWMSC wrote:Using Starwind 2.4.3, 2.6.1, and ms software initiator 1.06, starport 2.6.1 I found this out.


Most testing was done on clean installs of W2K3 server enterprise
using VMWare GSX Server 3.1. From clean machines to new installs of
starwind on other clean machines I found that I sometims got an error and sometimes not while using the ms initiator. However, I had a server with starwind 2.4.3 running and I could not connect to it at all, and I received an 'unspecified error' message. Well... I decided to setup an ms-iSNS server too. In the course of doing this I noticed that it was difficult to find the iqn. names of devices that I had given alias names. So I removed and the re-added the devices without the aliased iqn names so that i could write them down to enter into the isns server.

On doing this I eventually found that I could connect to the starwind server using the ms iscsi initiator without receiving an error. The error seemed to be generated by the 'friendly names', and once they were removed everthing started to work right. Note also that I did not always get an error when I connected to the starwind server, sometimes I could connect, but only see the iqn. names and not the 'friendly' names.

Hi,

Current StarWind version (2.6.1) does not support iSNS servers. So you need to add target names to SNS manually if you need them (as you did).

A canonic iSCSI target name should be formatted as "iqn.YYYY-MM.reverse_dns_name.xxxxx".
So some initiators may fail to connect to targets with non-canonical names.

We'll fix the issue with iSCSI target names in a next StarWind relese.

valery (staff) wrote:A canonic iSCSI target name should be formatted as "iqn.YYYY-MM.reverse_dns_name.xxxxx".
So some initiators may fail to connect to targets with non-canonical names.

We'll fix the issue with iSCSI target names in a next StarWind relese.

thanks for that info. fixed my problem pretty quick.

Nice to know the issue is gone

Anonymous wrote:

valery (staff) wrote:A canonic iSCSI target name should be formatted as "iqn.YYYY-MM.reverse_dns_name.xxxxx".
So some initiators may fail to connect to targets with non-canonical names.

We'll fix the issue with iSCSI target names in a next StarWind relese.

thanks for that info. fixed my problem pretty quick.