List- I have several samba 3.0.0 file/print servers running in a Windows 2000 AD domain. I do not use winbind; but have an LDAP database for Unix UID's with nss_ldap. I have MIT krb5-1.3.1. When I have tried to upgrade these machines to samba 3.0.1, clients get prompted for a user name and password when trying to connect. I have seen others with this problem, but none of their fixes have worked for me. I also get this message in the log files: setup_new_vc_session: New VC == 0, if NT4.x compatible we would close all old resources. [2003/12/17 14:01:00, 3] smbd/sesssetup.c:reply_sesssetup_and_X_spnego(471) Doing spnego session setup [2003/12/17 14:01:00, 3] smbd/sesssetup.c:reply_sesssetup_and_X_spnego(502) NativeOS=[Windows 2000 2195] NativeLanMan=[Windows 2000 5.0] PrimaryDomain=[] [2003/12/17 14:01:00, 3] smbd/sesssetup.c:reply_spnego_negotiate(380) Got OID 1 2 840 48018 1 2 2 [2003/12/17 14:01:00, 3] smbd/sesssetup.c:reply_spnego_negotiate(380) Got OID 1 2 840 113554 1 2 2 [2003/12/17 14:01:00, 3] smbd/sesssetup.c:reply_spnego_negotiate(380) Got OID 1 3 6 1 4 1 311 2 2 10 [2003/12/17 14:01:00, 3] smbd/sesssetup.c:reply_spnego_negotiate(383) Got secblob of size 1214 [2003/12/17 14:01:00, 10] passdb/secrets.c:secrets_named_mutex(697) secrets_named_mutex: got mutex for replay cache mutex [2003/12/17 14:01:00, 10] libads/kerberos_verify.c:create_keytab(56) creating keytab: MEMORY: [2003/12/17 14:01:00, 3] libads/kerberos_verify.c:setup_keytab(147) unable to create MEMORY: keytab (Unknown Key table type) [2003/12/17 14:01:00, 3] libads/kerberos_verify.c:ads_verify_ticket(280) ads_verify_ticket: unable to setup keytab [2003/12/17 14:01:00, 1] smbd/sesssetup.c:reply_spnego_kerberos(172) Failed to verify incoming ticket! [2003/12/17 14:01:00, 3] smbd/error.c:error_packet(118) error packet at smbd/sesssetup.c(173) cmd=115 (SMBsesssetupX) NT_STATUS_LOGON_FAILURE I haven't found anything that has helped. If I reinstall samba 3.0.0 and restart samba, everything works normally. I am using the same configure options for both source trees. I have also tried applying the patch sent out by Jerry today. I have Slackware 9.1. Can anyone tell me what is going wrong? I get some warnings while compiling the source, but I get the same warnings when compiling 3.0.0, so I don't think that is it. -Chris