Bug 5638 - NETBios Alias not working correctly
NETBios Alias not working correctly
Status: NEW
Product: Samba 3.2
Classification: Unclassified
Component: Clustering
: P3 normal
: ---
Assigned To: Volker Lendecke
Samba QA Contact
Depends on:
  Show dependency treegraph
Reported: 2008-07-28 08:38 UTC by Mark D. McBride
Modified: 2008-07-30 09:40 UTC (History)
0 users

See Also:

bziped log.smbd (72.01 KB, application/octet-stream)
2008-07-30 08:28 UTC, Mark D. McBride
no flags Details
smb.conf (1.95 KB, text/plain)
2008-07-30 08:29 UTC, Mark D. McBride
no flags Details
New bziped log.smbd (119.25 KB, application/octet-stream)
2008-07-30 09:21 UTC, Mark D. McBride
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mark D. McBride 2008-07-28 08:38:02 UTC
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.


Comment 1 Volker Lendecke 2008-07-30 03:03:38 UTC
Please upload your smb.conf and a debug level 10 log of the smbd that fails.

Comment 2 Mark D. McBride 2008-07-30 08:28:39 UTC
Created attachment 3444 [details]
bziped log.smbd
Comment 3 Mark D. McBride 2008-07-30 08:29:11 UTC
Created attachment 3445 [details]
Comment 4 Mark D. McBride 2008-07-30 08:32:28 UTC
Attached requested files.

However, the Alias is now advertised, but now is asking for username and password, but not accepting my login.
Comment 5 Volker Lendecke 2008-07-30 08:44:53 UTC
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 [23] 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?

Comment 6 Mark D. McBride 2008-07-30 09:21:30 UTC
Created attachment 3446 [details]
New bziped log.smbd
Comment 7 Mark D. McBride 2008-07-30 09:23:24 UTC
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.
Comment 8 Volker Lendecke 2008-07-30 09:30:14 UTC
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?

Comment 9 Mark D. McBride 2008-07-30 09:40:02 UTC
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.