Bug 15835 - [BUG] net ads kerberos kinit -P: NT_STATUS_INTERNAL_ERROR after successful domain join
Summary: [BUG] net ads kerberos kinit -P: NT_STATUS_INTERNAL_ERROR after successful do...
Status: RESOLVED DUPLICATE of bug 15840
Alias: None
Product: Samba 4.1 and newer
Classification: Unclassified
Component: AD: LDB/DSDB/SAMDB (show other bugs)
Version: 4.21.3
Hardware: All Linux
: P5 normal (vote)
Target Milestone: ---
Assignee: Samba QA Contact
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-03-19 14:29 UTC by Thanh Nguyen
Modified: 2025-11-28 17:17 UTC (History)
0 users

See Also:


Attachments
Config file (1.22 KB, text/plain)
2025-03-19 14:29 UTC, Thanh Nguyen
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Thanh Nguyen 2025-03-19 14:29:25 UTC
Created attachment 18617 [details]
Config file

Problem Description:
Our system requires LDAP TLS/SASL channel binding support. To achieve this, we upgraded Samba to version 4.22. The installation and configuration were completed successfully, and we were able to join the Active Directory (AD) server without issues.

However, we encountered an error when attempting to create a Kerberos ticket using Samba via the net ads kerberos kinit command. Notably, when using the kinit command from the Kerberos package, the ticket is created successfully. The issue appears to be specific to Samba's net ads functionality.

Steps to Reproduce:
Join the domain successfully using net ads join.
Run sudo net ads kerberos kinit -P.

Expected Behavior: You expect the command to obtain a Kerberos ticket without errors.

Actual Behavior: The command returns:
failed to kinit password: NT_STATUS_INTERNAL_ERROR

Environment Details:
Samba Version: 4.22
OS: Ubuntu 24.04
Kerberos Version: 1.21.3
Comment 1 Guenther Deschner 2025-11-28 17:17:54 UTC
This is most likely the same issue resolved with #15840, can you verify? Unfortunately you now need to set KRB5CCNAME prior to calling net in that way.

*** This bug has been marked as a duplicate of bug 15840 ***