Visit Open-E website
Results 1 to 10 of 16

Thread: Cannot connect using Microsoft iSCSI Initiator

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1

    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?

  2. #2

    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

  3. #3

    Default

    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.

  4. #4

    Default

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

    Todd Maxwell


    Follow the red "E"
    Facebook | Twitter | YouTube

  5. #5

    Default

    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.

  6. #6

    Default

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

    Todd Maxwell


    Follow the red "E"
    Facebook | Twitter | YouTube

  7. #7

    Default Logs e-mailed

    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.

Posting Permissions

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