Visit Open-E website
Results 1 to 10 of 36

Thread: Not listening on port 3260

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1
    Join Date
    Oct 2010
    Location
    GA
    Posts
    935

    Default

    can you get a telnet reply on port 3260 from the windows box?

  2. #2
    Join Date
    Oct 2009
    Posts
    53

    Default

    Hi

    Currently, there is a VMWare ESX 5 machine connected to another target and the connection is properly shown in the location you mentioned (will post a screenshot tonight)

    I have one spare NIC on the machine and I will see if I can connect a laptop directly and what the telnet response on port 3260 is, but that'll be tonight.

    Will keep you posted...

  3. #3

    Default

    Could it be that the ESX 4.1 and the ESX 5.0 that you mentioned in the other posts are connected to the targets? If so then using the Microsoft's (Win 2k8 R2) iSCSI initiator to the same targets wont work as the ESX are already connected to them.
    All the best,

    Todd Maxwell


    Follow the red "E"
    Facebook | Twitter | YouTube

  4. #4
    Join Date
    Oct 2009
    Posts
    53

    Default

    Well, the ESX machine is connected to the existing targets (still need a screenshot?), but the problem happens with the newly created target.

    <Offtopic>
    I would like to use the vStorage API for backups, but that requires direct connection from the MS machine, where the backup software resides, to the target, wouldn't it?
    </Offtopic>


    I've succesfully added this new target to te ESX machines using static discovery, but the MS iSCSI client cannot even log onto the portal on port 3260, although it does connect (breaking connection gives 'connection error' instead of 'authentication error'.

    Hopefully I find the time soon to connect a Windows notebook directly...

  5. #5

    Default

    What I think what is happening here is that your ESX servers are connected to the targets and locking it out for the Windows systems. Use the Deny and Allow for the new target so that only the windows IP is allowed to connect to the target. For the API to windows I have no idea.
    All the best,

    Todd Maxwell


    Follow the red "E"
    Facebook | Twitter | YouTube

  6. #6
    Join Date
    Oct 2009
    Posts
    53

    Default

    Hi Todd

    I do not think this is the case: I allowed a subnet /24 to the targets and connect from an IP within that range.

    Besides, I've also tried to connect with the IP restrictions removed from the new target IP.

    I would love to try further, but my certificate had expired and I've just created a new one using the Time settings on the console, but the certificate is still invalid and no browser allows me to proceed.
    I guess I need to reboot the DSS first?

  7. #7
    Join Date
    Oct 2009
    Posts
    53

    Default

    Little update:

    I connected a notebook with an IP in the correct range directly to the "spare" (but already configered for use in another subnet) NIC on the DSS and succesfully received a ping reply.

    I then tried to connect using "iscsicli qaddtargetportal <IP-address>, but still the result is "Authentication failure".

    I don't think IP restrictions are the problem, since I've already tried to connect from within the range that the ESX machine is also in.
    Nevertheless, just to get this straight: any IP restrictions on specific targets should NOT affect the targetportal on port 3260, should they?

    Next step will be more close examination of the DSS logs, but for now I still have the d*** certificate issue...

  8. #8

    Default

    Maybe some screen shots to show some of the settings and outputs. Also download the log file then look for the tests.log and look for the "session" like below and post for the iSCSI sessions so we all can see. I have seen in the past many times before where there is another initiator connected to an iSCSI target. For you to now to have issues with getting into the browser tells me there is something else going on (port, duplicate name, separate network, subet, static route...). if rebooting works then possible cache of the browser - use Firefox possibly.

    cat /proc/net/iet/session
    *-----------------------------------------------------------------------------*

    cat: /proc/net/iet/session: No such file or directory

    *-----------------------------------------------------------------------------*
    cat /proc/scsi_tgt/iscsi/session
    *-----------------------------------------------------------------------------*


    Also look in the tests.log and send us the info below.
    *-----------------------------------------------------------------------------*
    ifconfig -a
    *-----------------------------------------------------------------------------*
    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
  •