I recently updated from Samba 3.0.23d to 3.2.0 on my AIX 5.3 with HACMP system.
With Samba 3.0.23d I could set the NETBIOS ALIAS to the DNS name that follows the HACMP failover. I would then be able to browse to my home directory. With Samba 3.2.0, this fails. It says that my home directory is not found on this server. The $S macro does not seem to be resolving my login name. It seems to be resolving as my PC's hostname. I can see a share with my login name in Windows explorer, but it says that the share refers to location that is unavailable.
Please upload your smb.conf and a debug level 10 log of the smbd that fails.
Created attachment 3444 [details]
Created attachment 3445 [details]
Attached requested files.
However, the Alias is now advertised, but now is asking for username and password, but not accepting my login.
There are error messages like
[2008/07/30 08:53:18, 3] libads/kerberos_verify.c:ads_secrets_verify_ticket(282)
ads_secrets_verify_ticket: enc type  failed to decrypt with error Decrypt integrity check failed
Is it possible that your new Samba installation for some reason does not have the same secrets.tdb available as the old one, or that the join information was lost somehow?
Created attachment 3446 [details]
New bziped log.smbd
You were correct. The Windows administrator refreshed the Test environment last night, so it did not have the samba system joined. I joined execha1 as execb80.
In that new logfile it does connect, however the first lines indicate some broken join: kerberos_kinit_password EXECHA1$@OHSERS.LOCAL failed: Client not found in Kerberos database or check_ntlm_password: winbind authentication for user [mcbride] FAILED with error NT_STATUS_NO_TRUST_SAM_ACCOUNT
After re-joining, did you restart Samba? And, what does not work?
I joined the domain when Samba was down as EXECB80. Started it. Stopped and restarted smbd with -d 10.
execha1 is the hostname. execb80 is the failover hostname that follows where the HACMP decides which system is active. execb80 is the NETBios Alias that I want users to connect to.
I did not join as EXECHA1.
When I browse to my home share "\\Execb80\mcbride", it does not allow me in.
not a bug for bugzilla but probably a configuration issue