Visit Open-E website
Page 2 of 2 FirstFirst 12
Results 11 to 17 of 17

Thread: SMB/NetBIOS active on iSCSI-R3?

  1. #11

    Default

    Please send logs to support about this. We need to review them on these ports. Thanks for bringing this up!
    All the best,

    Todd Maxwell


    Follow the red "E"
    Facebook | Twitter | YouTube

  2. #12

    Default

    ok i sent it to support@open-e.com

    thanks for looking into this

  3. #13

    Default

    Any way you can send the logs from Status > Hardware > Log then click on the "Download" button so we can get the whole log file? Thanks for sending this!
    All the best,

    Todd Maxwell


    Follow the red "E"
    Facebook | Twitter | YouTube

  4. #14

    Default

    sent that as well

  5. #15

    Default

    NetBios is enabled as it should be to access server
    over IP and name.

    Also we don’t have IRC server, this port is used with raid tools
    (even if this tool is not used our port server lock it).

    Active Internet connections (only servers)
    Proto Recv-Q Send-Q Local Address Foreign Address
    State PID/Program name
    tcp 0 0 0.0.0.0:389 0.0.0.0:*
    LISTEN 12962/slapd
    Needed for SMB

    tcp 0 0 0.0.0.0:842 0.0.0.0:*
    LISTEN 9992/drbd_rpc
    Needed for replication

    tcp 0 0 0.0.0.0:6666 0.0.0.0:*
    LISTEN 7221/portreserve
    Reserved for raid tools

    tcp 0 0 0.0.0.0:139 0.0.0.0:*
    LISTEN 12595/smbd
    So you will see server in network neighborhood


    tcp 0 0 0.0.0.0:6667 0.0.0.0:*
    LISTEN 7221/portreserve
    Reserved for raid tools

    tcp 0 0 0.0.0.0:6668 0.0.0.0:*
    LISTEN 7221/portreserve
    Reserved for raid tools

    tcp 0 0 0.0.0.0:6669 0.0.0.0:*
    LISTEN 7221/portreserve
    Reserved for raid tools

    tcp 0 0 0.0.0.0:22222 0.0.0.0:*
    LISTEN 12845/sshd
    Administrator access for console

    tcp 0 0 0.0.0.0:6670 0.0.0.0:*
    LISTEN 7221/portreserve
    Reserved for raid tools

    tcp 0 0 0.0.0.0:111 0.0.0.0:*
    LISTEN 9987/portmap
    Needed for RPC

    tcp 0 0 0.0.0.0:80 0.0.0.0:*
    LISTEN 13017/apache-ssl
    WWW access

    tcp 0 0 0.0.0.0:25456 0.0.0.0:*
    LISTEN 7221/portreserve
    Reserved for raid tools

    tcp 0 0 0.0.0.0:25457 0.0.0.0:*
    LISTEN 7221/portreserve
    Reserved for raid tools

    tcp 0 0 0.0.0.0:11798 0.0.0.0:*
    LISTEN 7221/portreserve
    Reserved for raid tools

    tcp 0 0 0.0.0.0:888 0.0.0.0:*
    LISTEN 11484/3dm2
    3ware raid tools

    tcp 0 0 0.0.0.0:443 0.0.0.0:*
    LISTEN 13017/apache-ssl
    WWW access

    tcp 0 0 0.0.0.0:3260 0.0.0.0:*
    LISTEN 12292/ietd
    iSCSI protocol

    tcp 0 0 0.0.0.0:445 0.0.0.0:*
    LISTEN 12595/smbd
    So you will see server in network neighborhood

    tcp 0 0 0.0.0.0:4702 0.0.0.0:*
    LISTEN 7221/portreserve
    Reserved

    udp 0 0 192.254.17.56:137 0.0.0.0:*
    12591/nmbd
    udp 0 0 10.40.4.150:137 0.0.0.0:*
    12591/nmbd
    udp 0 0 0.0.0.0:137 0.0.0.0:*
    12591/nmbd
    udp 0 0 192.254.17.56:138 0.0.0.0:*
    12591/nmbd
    udp 0 0 10.40.4.150:138 0.0.0.0:*
    12591/nmbd
    udp 0 0 0.0.0.0:138 0.0.0.0:*
    12591/nmbd
    So you will see server in network neighborhood


    udp 0 0 0.0.0.0:840 0.0.0.0:*
    9992/drbd_rpc
    Needed for replication

    udp 0 0 0.0.0.0:111 0.0.0.0:*
    9987/portmap
    Needed for RPC

    udp 0 0 10.40.4.150:123 0.0.0.0:*
    10944/ntpd
    udp 0 0 192.254.17.56:123 0.0.0.0:*
    10944/ntpd
    udp 0 0 0.0.0.0:123 0.0.0.0:*
    10944/ntpd
    Time synchronization
    All the best,

    Todd Maxwell


    Follow the red "E"
    Facebook | Twitter | YouTube

  6. #16

    Default

    ok we have been pen-testing this since last night (mini hackathon lol) and what i have initially found is that there is no way to access these services - which is what i expected.

    what i really wanted to hint at for this wasnt that we didnt trust that they were configured properly by open-e; just that if i purchase an ISCSI-R3 product im still running all these DSS'ish services

    so in the food chain all dev work is done on DSS then flows out to ISCSI product, maybe before putting the "big red bow" on the ISCSI-R3 product, they could for example:

    "/etc/init.d/samba stop" etc. etc.

    make sense? its really the only difference in my performance variances between gentoo (my bootstrapped, hand built iscsi box which took 4 hours to get set up) and open-e. i have 2 ports open in gentoo - 3260,22 it was only about a 2% difference in performance and that small of a difference is completely trivial when you are talking about something that peaks at 128mb/s on a single gbe link.

  7. #17

    Default

    Thanks for the update. I will send this to our research and development team and se if we can have this excluded with iSCSI-R3. Again excellent work!
    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
  •