Visit Open-E website
Page 1 of 2 12 LastLast
Results 1 to 10 of 16

Thread: Cannot connect using Microsoft iSCSI Initiator

  1. #1

    Default 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. Thank you,

    Ted Gage AKA TedMac
    Chief Engineer,
    North Texas Fusion Center

  2. #2

    Default

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

    Todd Maxwell


    Follow the red "E"
    Facebook | Twitter | YouTube

  3. #3

    Default

    Tried that, didn't work either.

  4. #4

    Default

    Any errors from the MS side or firewall blocking?
    All the best,

    Todd Maxwell


    Follow the red "E"
    Facebook | Twitter | YouTube

  5. #5

    Default

    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..

  6. #6

    Default

    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.
    All the best,

    Todd Maxwell


    Follow the red "E"
    Facebook | Twitter | YouTube

  7. #7

    Default

    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

  8. #8

    Default

    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).
    All the best,

    Todd Maxwell


    Follow the red "E"
    Facebook | Twitter | YouTube

  9. #9

    Default

    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?

  10. #10

    Default

    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.
    All the best,

    Todd Maxwell


    Follow the red "E"
    Facebook | Twitter | YouTube

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •