Visit Open-E website
Page 2 of 4 FirstFirst 1234 LastLast
Results 11 to 20 of 36

Thread: Not listening on port 3260

  1. #11
    Join Date
    Oct 2009
    Posts
    53

    Default

    Thank you for your reply!

    I've tried by IP, using two machines on different subnets that both could ping the DSS (and vice versa), and FQDN.

    I probably disabled the dynamic discovery in VMWare (is it by default? I never checked, since I install by kickstart script and use static discovery there), but I cannot see how that would be the cause the MS discovery authentication failure.

    Any other ideas?

  2. #12
    Join Date
    Oct 2009
    Posts
    53

    Unhappy

    Am I the only one experiencing difficulties with Microsoft's native iSCSI?

  3. #13
    Join Date
    Oct 2010
    Location
    GA
    Posts
    935

    Default

    See if you can telnet to the port and get an answer.
    There isnt anything on the DSS side that would block it. In fact DSS will broadcast the LUN on each IP assigned to it.
    You can try to remove the target and re-add it. This will not remove data, just don't delete the Volume.

    I suspect something is blocking traffic in between the initiator and the LUN.

  4. #14
    Join Date
    Oct 2009
    Posts
    53

    Default

    It's been a while since I've been struggling with this issue, but now that I'm trying to backup VMs using SAN access directly (using vStorage API), I'm running into this issue again.

    What I am trying to do: access any DSS target using Microsoft's native (Win 2k8 R2) iSCSI initiator.

    Even without CHAP and any IP restrictions, I get "Authentication Failure", no matter on what IP or from what machine I try to connect.

    DSS is listening on port 3260, and I have a VMWare ESX 4.1 connected to one of the targets.
    The problem solely exists when using Microsoft Initiator.

    I'm stumped - this should be easy. What am I overlooking here?
    Are there any requirements for the Initiator name?

    Please, help!

  5. #15

    Default

    Just to make sure that we are on the same page here, that the Windows 2008 server is NOT a virtual machine and the target that you are trying to connect is not being used by any other initiator.

    If you can ping from the Windows 2008 server to the DSS being the same subnet and no VLAN and maybe try to directly connect the Windows 2008 directly to the DSS server to rule out any network issues from the Windows to the DSS side.

    Also check the Windows event logs as well to see if there is any errors coming up.
    All the best,

    Todd Maxwell


    Follow the red "E"
    Facebook | Twitter | YouTube

  6. #16
    Join Date
    Oct 2009
    Posts
    53

    Default

    Hi Todd

    The 2008 R2 machine is a physical one and has an IP in the same subnet as the DSS server.
    Actually, I tried two subnets, one in the default LAN and one in the iSCSI VLAN.

    The iSCSI target on the DSS is a newly created one, but the error occurs already when connecting to the target portal on port 3260.

    In both attempts, I was able to ping the DSS server.
    Unfortunately, the windows logs do not reveal any more information.

    The weird thing is: I remember having had the same issue a year or 2 ago, but about a year ago I once succesfully connected a Windows machine to a newly created target...
    I simply can't think of any iSCSI setting I've changed since then...

  7. #17

    Default

    Can you provide me a screen shot from the GUI (location below) or tell me if you see any connections to the Target?

    MAINTENANCE -> Connections -> Function: iSCSI session manager

    Is there any chance to directly connect a PC/Notebook and or the Windows to see if it will connect.
    All the best,

    Todd Maxwell


    Follow the red "E"
    Facebook | Twitter | YouTube

  8. #18
    Join Date
    Oct 2010
    Location
    GA
    Posts
    935

    Default

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

  9. #19
    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...

  10. #20

    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

Posting Permissions

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