Cannot connect using Microsoft iSCSI Initiator

This is a rookie mistake, but I'm unable to connect to target0 using Microsoft V2 of iSCSI Initiator. This is my first experience using the product. Here's my configuration: Posted here as your mail server is down.

*** System Configuration ***

Wndows Server 2003 SP1 Current

NIC 1 192.168.1.6

NIC 2 192.168.2.6

*** iSCSI R3 Enterprise Setup ***

Version: 2.30 build 2820

Target0 Volumes iv0000, iv0001

Target0 name iqn.2007-10:raid:target0

Bond0 192.168.1.30

Bond1 192.168.2.30

CHAP username NTFS

CHAP password 12345612345601

Target IP Access 192.168.1.6;192.168.2.6

*** iSCSI Initiator properties ***

General tab - Secret 12345612345699

Discovery tab 1 192.168.1.30 port 3260

Discovery tab 2 192.168.2.30 port 3260

Discovery Advanced (2 separate entries)

Local Adapter Microsoft iSCSI Initiator

Source IP 192.168.1.6. 192.168.2.6

Target portal Grayed out (is this a problem?)

CHAP logon information Checked

Username NTFS

Target secret 12345612345601

*** Result Authentication failure ***

I'm stumped. :confused: Thank you,

Ted Gage AKA TedMac
Chief Engineer,
North Texas Fusion Center

Can you try without CHAP and see if this works first (disable it on the iSCSI-R3 and the MS initiator).

Tried that, didn't work either.

Any errors from the MS side or firewall blocking?

Same error regardless whether CHAPS is on or off.

*** System Event Log ***
iSCSI discovery via SendTargets failed 0xefff0009 to target portal *192.168.1.30 0003260 Root\SCSIADAPTER\0000_0 192.168.1.6

I do not understand the 0xefff0009 parameter above. Am I supposed to set a binary somewhere? I thought that the iSCSI Initiator install was straightforward.

Also, the initiator reports "Authentication error" when you OK the Advanced box whether CHAPS is on or off. Argggh..

Try re-installing the MS Init. and make sure that you have the CHAP off and nothing in the Target IP access restricions on the iSCSI server on to test. You can also reset the Secret in the MS Init. as well.

Did a reinstall as suggested. No improvement. Please address the following.

1. I noted the following statement on the support home page in the FAQ... "-windows domain connecting problems". That's me. but when you follow the link there's a statement "Problem solved" and a download for the latest version. There is no explanation of what was wrong, what was fixed, or how to onfigure the new version is there is any dofference.
I'm getting a Microsoft Authentication error when I try to connect even without a CHAP password (i.e., nothing asking to be authenticated). I suspect this may be because the machine is not a member of the domain. What's the story on this issue as it sounbds like my problem?

2. Is there a test program (such as a Java app) where I can test the system? Currently, I cannot isolate the issue to a MS or Open-E problem.

3. Is there another app other than the MS iSCSI Initiator that I can try?

Thanks you for your help,

TedMac

Can you test with another system (XP or other MS system) with the MS initiator 2.02 and above to see if we can isolate the issue, also are there any errors on the iSCSI-R3 server (look for Red exclamation mark on the bottom left side of the screen).

I have a Windows XP Media system that is not a member of the domain. I'll test using it.

In the meantime, do you know the answer to question #1?

It is related to ADS Authentication with NAS version of our software - you have iSCSI-R3 Enterprise this is Block based and does not Authenticate with ADS.

Tried XP Media which is running on the network but on a workgroup and not on the domain. Same exact error. Now what?

I'm either going to have to abandon Open-E or find a solution. What are you other users experiences running Windows 2003 server in a domain? Or Windows Media in a workgroup? If any user is lurking out there with this configuration, I would greatly appreciate your comments. Perhaps I should rool back to an earlier version of the initiator. The latest version of iSCSI Enterprise 2820 and initiator 5.2.3790.3273 simply do not interoperate.

Back to question 2. Is there another test application? Java-based or whatever to access the system? I need to isolate the problem if possible.

One would assume that the basic operation would be relatively simple (i.e., no CHAP password, etc.). Just set up the IP addresses, install the MS iSCSI Initiator and connect. I cannot get past discovery w/o an error. In fact, I cannot add the target portal to talk to Open-E.

Try testing with MS init. version 2.02 5.2.3790.1895. You can test with Open iSCSI using a Linux operating system with kernel version 2.6.16, or later - link below to download.

http://www.open-iscsi.org/index.html#download

I must admit this is troubling as you described it should be that easy with MS. I know you have no firewall issues but try with using a cable directly attached to the server. Make sure to set the Target portal in the advanced to "Default" for the Local Adapter.

I'll take a look at the download link. BTW, the cable on sybnet 2 is directly connected from the test machine to the target.

Here's a wonderment.
Port 1 port scan...
Port 1 (192.168.1.30)
80
111
139
443
445
888
6666
6667
6668
6669
6670
Port 2 (192.168.2.30)
389
6838
9325
10067
10167
10666
12623
18753
20433
26274
27444
31789
31791
34555
35555
47262

Where's 3260?

Boy, that's a lot of strange open ports.

Can you email me your contact info, so I can review some other settings. I may need you to send logs as well from the iSCSI server in Status > Hardware > Logs then click on the Download button.

I sent the logs to your attention via email.

What's this with "License key"? I haven't entered one and the documentation is silent.

Lic. Key is for adding additional storage beyond 16TB. Still have not seen the email only from someone else other then Ted.