Tag: Kerberos

You may have a cross-forest trust set up, which uses RC4 on the trust relationship. In this case, please refer to https://support.microsoft.com/en-us/help/4492348/kerberos-unsupported-etype-error-when-authenticating-across-trust for more details and a method to configure the trust to use AES128 and AES256 encryption.

A second solution is to enable RC4 Kerberos encryption type on the Connectors through Group Policy:

• Navigate to Local Group Policy Editor –> Computer Configuration –> Windows Settings –> Security Settings –> Local Policies –> Security Options
• Select –> Network Security: Configure encryption types allowed for Kerberos
• Update Local Security Setting RC4_HMAC_MD5 so box is checked.
• Select ‘Apply’

You may have a cross-forest trust set up, which uses RC4 on the trust relationship. In this case, please refer to https://support.microsoft.com/en-us/help/4492348/kerberos-unsupported-etype-error-when-authenticating-across-trust for more details and a method to configure the trust to use AES128 and AES256 encryption.

A second solution is to enable RC4 Kerberos encryption type on the Connectors through Group Policy:

• Navigate to Local Group Policy Editor –> Computer Configuration –> Windows Settings –> Security Settings –> Local Policies –> Security Options
• Select –> Network Security: Configure encryption types allowed for Kerberos
• Update Local Security Setting RC4_HMAC_MD5 so box is checked.
• Select ‘Apply’

You may have a cross-forest trust set up, which uses RC4 on the trust relationship. In this case, please refer to https://support.microsoft.com/en-us/help/4492348/kerberos-unsupported-etype-error-when-authenticating-across-trust for more details and a method to configure the trust to use AES128 and AES256 encryption.

A second solution is to enable RC4 Kerberos encryption type on the Connectors through Group Policy:

• Navigate to Local Group Policy Editor –> Computer Configuration –> Windows Settings –> Security Settings –> Local Policies –> Security Options
• Select –> Network Security: Configure encryption types allowed for Kerberos
• Update Local Security Setting RC4_HMAC_MD5 so box is checked.
• Select ‘Apply’

You may have a cross-forest trust set up, which uses RC4 on the trust relationship. In this case, please refer to https://support.microsoft.com/en-us/help/4492348/kerberos-unsupported-etype-error-when-authenticating-across-trust for more details and a method to configure the trust to use AES128 and AES256 encryption.

A second solution is to enable RC4 Kerberos encryption type on the Connectors through Group Policy:

• Navigate to Local Group Policy Editor –> Computer Configuration –> Windows Settings –> Security Settings –> Local Policies –> Security Options
• Select –> Network Security: Configure encryption types allowed for Kerberos
• Update Local Security Setting RC4_HMAC_MD5 so box is checked.
• Select ‘Apply’

You may have a cross-forest trust set up, which uses RC4 on the trust relationship. In this case, please refer to https://support.microsoft.com/en-us/help/4492348/kerberos-unsupported-etype-error-when-authenticating-across-trust for more details and a method to configure the trust to use AES128 and AES256 encryption.

A second solution is to enable RC4 Kerberos encryption type on the Connectors through Group Policy:

• Navigate to Local Group Policy Editor –> Computer Configuration –> Windows Settings –> Security Settings –> Local Policies –> Security Options
• Select –> Network Security: Configure encryption types allowed for Kerberos
• Update Local Security Setting RC4_HMAC_MD5 so box is checked.
• Select ‘Apply’

You may have a cross-forest trust set up, which uses RC4 on the trust relationship. In this case, please refer to https://support.microsoft.com/en-us/help/4492348/kerberos-unsupported-etype-error-when-authenticating-across-trust for more details and a method to configure the trust to use AES128 and AES256 encryption.

A second solution is to enable RC4 Kerberos encryption type on the Connectors through Group Policy:

• Navigate to Local Group Policy Editor –> Computer Configuration –> Windows Settings –> Security Settings –> Local Policies –> Security Options
• Select –> Network Security: Configure encryption types allowed for Kerberos
• Update Local Security Setting RC4_HMAC_MD5 so box is checked.
• Select ‘Apply’

You may have a cross-forest trust set up, which uses RC4 on the trust relationship. In this case, please refer to https://support.microsoft.com/en-us/help/4492348/kerberos-unsupported-etype-error-when-authenticating-across-trust for more details and a method to configure the trust to use AES128 and AES256 encryption.

A second solution is to enable RC4 Kerberos encryption type on the Connectors through Group Policy:

• Navigate to Local Group Policy Editor –> Computer Configuration –> Windows Settings –> Security Settings –> Local Policies –> Security Options
• Select –> Network Security: Configure encryption types allowed for Kerberos
• Update Local Security Setting RC4_HMAC_MD5 so box is checked.
• Select ‘Apply’

You may have a cross-forest trust set up, which uses RC4 on the trust relationship. In this case, please refer to https://support.microsoft.com/en-us/help/4492348/kerberos-unsupported-etype-error-when-authenticating-across-trust for more details and a method to configure the trust to use AES128 and AES256 encryption.

A second solution is to enable RC4 Kerberos encryption type on the Connectors through Group Policy:

• Navigate to Local Group Policy Editor –> Computer Configuration –> Windows Settings –> Security Settings –> Local Policies –> Security Options
• Select –> Network Security: Configure encryption types allowed for Kerberos
• Update Local Security Setting RC4_HMAC_MD5 so box is checked.
• Select ‘Apply’

You may have a cross-forest trust set up, which uses RC4 on the trust relationship. In this case, please refer to https://support.microsoft.com/en-us/help/4492348/kerberos-unsupported-etype-error-when-authenticating-across-trust for more details and a method to configure the trust to use AES128 and AES256 encryption.

A second solution is to enable RC4 Kerberos encryption type on the Connectors through Group Policy:

• Navigate to Local Group Policy Editor –> Computer Configuration –> Windows Settings –> Security Settings –> Local Policies –> Security Options
• Select –> Network Security: Configure encryption types allowed for Kerberos
• Update Local Security Setting RC4_HMAC_MD5 so box is checked.
• Select ‘Apply’

You may have a cross-forest trust set up, which uses RC4 on the trust relationship. In this case, please refer to https://support.microsoft.com/en-us/help/4492348/kerberos-unsupported-etype-error-when-authenticating-across-trust for more details and a method to configure the trust to use AES128 and AES256 encryption.

A second solution is to enable RC4 Kerberos encryption type on the Connectors through Group Policy:

• Navigate to Local Group Policy Editor –> Computer Configuration –> Windows Settings –> Security Settings –> Local Policies –> Security Options
• Select –> Network Security: Configure encryption types allowed for Kerberos
• Update Local Security Setting RC4_HMAC_MD5 so box is checked.
• Select ‘Apply’