Security

last person joined: yesterday 

Forum to discuss Enterprise security using HPE Aruba Networking NAC solutions (ClearPass), Introspect, VIA, 360 Security Exchange, Extensions, and Policy Enforcement Firewall (PEF).
Expand all | Collapse all

CPPM - Failed to join domain: failed to connect to AD: Operations error

This thread has been viewed 1 times
  • 1.  CPPM - Failed to join domain: failed to connect to AD: Operations error

    Posted May 26, 2015 09:03 PM

     

    Hello,

     

    When trying to Join ClearPass to an AD domain it is faling due to  "Operations error"

     

    Join domain failed    
    Adding host to AD domain...
    INFO - Fetched REALM 'XXX.LOCAL' from domain FQDN
    'YYY.XXX.local'
    INFO - Fetched the NETBIOS name 'EU'
    INFO - Creating domain directories for 'EU'
    Enter -USER's password:
    >>>>  Failed to join domain: failed to connect to AD: Operations error <<<<
    INFO - Restoring smb configuration
    INFO - Restoring krb5 configuration file
    INFO - Deleting domain directories for 'EU'
    ERROR - ServerName failed to join the domain XXX.LOCAL
    with domain controller as YYY.XXX.local
    Join domain failed

     

    ClearPass has connectivity to the DC and the FQDN resolves to the correct IP@ and finds the NETBIOS name correctly.

     

    I am wondering if the firewall might be blocking port 389 , is there a CLI command I could use to test this port ?

     

    Thank you,

     

    David Sanchez



  • 2.  RE: CPPM - Failed to join domain: failed to connect to AD: Operations error

    EMPLOYEE
    Posted May 26, 2015 09:05 PM

    You can test authentication against a domain by using:

     

     auth -u <username> -n <domain NETBIOS name>


  • 3.  RE: CPPM - Failed to join domain: failed to connect to AD: Operations error

    Posted May 27, 2015 01:22 AM

     

    Hello Tim,

     

    Thank you for your reply.

     

    I've tried that command already and didn't work. For it to be used  CPPM needs to be part of the domain first, and I am stuck in the process of joining the AD. 

     

    I am awaiting to confirm port 389 by the firewall team and will post the outcome.

     

    DS