Tips for finding Knowledge Articles

  • - Enter just a few key words related to your question or problem
  • - Add Key words to refine your search as necessary
  • - Do not use punctuation
  • - Search is not case sensitive
  • - Avoid non-descriptive filler words like "how", "the", "what", etc.
  • - If you do not find what you are looking for the first time,reduce the number of key words you enter and try searching again.
  • - Minimum supported Internet Explorer version is IE9
Home  >
article

KB-8867: Solaris Samba not able to connect with NT_STATUS_CONNECTION_DISCONNECTED and krb5_kt_start_seq_get failed (No such file or directory) error

Centrify DirectControl ,  

21 June,17 at 11:35 AM

Problem:

Solaris not able to connect to the Samba share given out the following error:
 
"NT_STATUS_CONNECTION_DISCONNECTED"
 
While in log.smbd shows the following error messages indicating Samba is not able to retrieve the krb5.keytab file:
 
***********************************************
[2017/06/2014:01:50.787298,1] ../source3/librpc/crypto/gse_krb5.c:416(fill_mem_keytab_from_system_keytab)
../source3/librpc/crypto/gse_krb5.c:416: krb5_kt_start_seq_get failed (No such file or directory)
[2017/06/20 14:01:50.787582, 0] ../lib/util/fault.c:78(fault_report)
 [2017/06/20 14:01:50.787733, 0] ../lib/util/fault.c:79(fault_report)
INTERNAL ERROR: Signal 11 in pid 8717 (4.2.14)
***********************************************

Resolution:

This issue is due to the OS Solaris where it keeps the krb5.keytab file in a different location on the machine where Samba doesn’t know where to retrieve it. Therefore, resulting the connection issue above.
 
To workaround it, we can create a symlink pointing to the default location with the following command:

ln -s /etc/krb5/krb5.keytab /etc/krb5.keytab

Once done, please restart the samba service and try connect to the share again.

If the issue still persist, please help to perform the following and collect the debug that we need for further investigation:
a. Edit /etc/samba/smb.conf:
log level = 10
log file = /var/log/samba/smb.log
max log size = 0
 
b. Restart samba service

c. Switch on adclient debug:
/usr/share/centrifydc/bin/addebug on
/usr/share/centrifydc/bin/addebug clear
 
d. Reproducing the issue by running smbclient command with failure.
 
e. Pack up and turn off debug:
adinfo -t
/usr/share/centrifydc/addebug off
 
f. Remove or revert to your setting from smb.conf:
log level = 10
log file = /var/log/samba/smb.log
max log size = 0
 
Please help send in the following files:
> /var/log/samba/smb.log
> /var/centrify/tmp/adinfo_support.tar.gz

 

Still have questions? Click here to log a technical support case, or collaborate with your peers in Centrify's Online Community.

Related Articles

No related Articles