issues connecting to target - Storage

This is a discussion on issues connecting to target - Storage ; Hi, I'm having difficulties connecting to a target. If I enable CHAP the initiator returns with a login error: "authentication failure" I've read that if the auth method mismatches, this error could come up. But where can I see what ...

+ Reply to Thread
Results 1 to 4 of 4

Thread: issues connecting to target

  1. issues connecting to target

    Hi, I'm having difficulties connecting to a target.
    If I enable CHAP the initiator returns with a login error:
    "authentication failure"

    I've read that if the auth method mismatches, this error could come up.
    But where can I see what auth method is active on the target, and how to
    set this at the initiator's end?

    As long as I don't use CHAP, thing work well..

    Using:
    Windows storage server 2003 (R2)
    iSCSI Initiator 2.04


    Thanks in advance,
    rel.

  2. RE: issues connecting to target

    CHAP must be enabled on the storage target before you use it on the initiator.
    Configuring CHAP on the target will depend on what hardware/management tool
    you are using .

    After entering CHAP data on the target, you must enter the same
    data(username and secret) on each initiator you log in to. This data is
    sent to the target for authentication


    For initiator CHAP this data is the initiator username and secret that you
    entered on the Target. When the initiator sends this data, the target
    compares it with an account database and authenticates the initiator

    Thanks and Regard
    Ambarish.

    "relikwie" wrote:

    > Hi, I'm having difficulties connecting to a target.
    > If I enable CHAP the initiator returns with a login error:
    > "authentication failure"
    >
    > I've read that if the auth method mismatches, this error could come up.
    > But where can I see what auth method is active on the target, and how to
    > set this at the initiator's end?
    >
    > As long as I don't use CHAP, thing work well..
    >
    > Using:
    > Windows storage server 2003 (R2)
    > iSCSI Initiator 2.04
    >
    >
    > Thanks in advance,
    > rel.
    >


  3. Re: issues connecting to target

    Hi Ambrisch, thanks for your answer.

    Ambrish schreef:
    > CHAP must be enabled on the storage target before you use it on the initiator.
    > Configuring CHAP on the target will depend on what hardware/management tool
    > you are using .


    I do just that, on the target (properties/auth tab) I set the user
    and the secret. If I connect to this target from the initiator with the
    same userid and secret as I set on the target, I get authentication failure.

    There is an odd thing though:

    The initiator properties has a discovery tab, here I receive the error
    when trying to add target protal, while chap is enabled at the target.
    Thus I can never logon to the target, since it is not visible in the
    targets tab.

    If I use iSNS, then the target becomes visible within the target tab
    (inititator side), then I can login with id/secret. The issue now is
    that altough I select persistent, the connection is inactive after reboot.

    If I don't use CHAP at both sides, I can add the target portal, and
    afterwards logon to the target and persisten works. So wont need iSNS.


    I use the "Microsoft iSCSI Software Target" delevired with Windows
    storage server.


    Guess I stumbeled upon a bug..


    Regards,
    relikwie

  4. Re: issues connecting to target

    >
    Have to say that the issue is solved.
    I was trying to authenticate while adding the target portal.
    But authentication is done a logon stage (where one selects the target).

    A bit confusing, that CHAP checkboxes are under the advanced button
    at adding "target portal". Guess it's there for a reason.


    Thanks.

+ Reply to Thread