Network Attached Storage​

 View Only

  • 1.  cannot join hostname to AD

    Posted 10-27-2022 16:36
    Receiving the following error:

    Name " " collides with similar name

    "?invalid?" which is already configured.

    cifs-names for all EVSes within a single cluster must be unique

    within their first 15 characters.

    Add attempt failed.



    ------------------------------
    Jon Fontaine
    IT Support Manager
    Department of National Defence
    ------------------------------


  • 2.  RE: cannot join hostname to AD

    Posted 11-01-2022 03:54

    Please try with FQDN. If you are using DNS IP then please try with the domain name as the hostname, not the server name.



    ------------------------------
    Mousumi Ghosh
    Software QA Engineer
    Hitachi Vantara
    ------------------------------

    Original Message


  • 3.  RE: cannot join hostname to AD

    Posted 11-01-2022 08:36

    For future reference, Jon is working thru the GSC (case 03744712); in the process Jon rebooted the nodes (this is a last resort type of operation).
    It should be noted this is a very rare error being reported and there is only one internal Engineering customer escalation.



    ------------------------------
    Albert Hagopian
    Software Development Engineer - Specialist
    Hitachi Vantara
    ------------------------------

    Original Message


  • 4.  RE: cannot join hostname to AD

    Posted 11-01-2022 12:50
    Did the reboot fix the issue with joining AD?

    ------------------------------
    Tammy Waldschmidt
    Software Integration Engineer
    Hitachi Vantara
    ------------------------------

    Original Message


  • 5.  RE: cannot join hostname to AD

    Posted 11-01-2022 17:24

    Hello Jon - I see you have a case opened with GSC on the topic and have since rebooted the nodes in an attempt to resolve with GSC requesting an update. Let's leave the resolution to the case as there is always the possibility that one size does not fit all - especially when it comes to rebooting the servers in an attempt to fix an issue.

    If anyone experiences similar behavior, please do open a case with Support - there are very few references to this specific error in the internal Engineering db, which indicates this error is very uncommon and possibly more easily solved beyond a large hammer approach of rebooting the HNAS.

    For the Community's future reference, the Support case is 03744712. If you experience this error, feel free Support if your symptoms are siilar.



    ------------------------------
    Albert Hagopian
    Software Development Engineer - Specialist
    Hitachi Vantara
    ------------------------------

    Original Message


Related Content