Operating System - HP-UX
1834015 Members
2741 Online
110063 Solutions
New Discussion

Upgrading from Samba 2.x to 3.x , for Clients using Kerberos %m is not working

 
Christian Schulze
Regular Advisor

Upgrading from Samba 2.x to 3.x , for Clients using Kerberos %m is not working

Hi,

we upgraded an old Serviceguard-Cluster providing SMB-Shares to a new hardware.
Along with the hardware there was an Upgrade of the complete System from HPUX 11.00 to 11.11 and Samba 2.2.8 to 3.0.14a (HP A.02.02).

We are using the following share-definiton:
[backup_nb]
comment = Share using Netbios-Name of Client
path = /cifs/data/backup/%m

This provided every Client with his own directory (named by the netbiosname)

I was told the reason for that, but I have no idea how to make a workaround.
Clients using Kerberos connect to samba over port 445 where no netbios wrapper listens, so the %m macro cannot reolve the netbiosname.
As a consequence every client tries to connect to his directory identified by the client-IP-Adress.
As a first shot I created tons of symbolic links for all IP-Addr to the Netbios/Hostnames.

But here I see a pitfall, if a client would change either his IP-Addr. and not his hostname and vice versa.

I cannot just replace all %m with %I for the IP-Adress of the client, because we have several applications relying on the hostname.

Another issue is, that generation of logfiles lead to logfilenames containing the IP-Addres in the filename instead of the hostname.

Did somebody else hit this problem ?
How was it solved ?

Any Ideas are very welcome.

Thanks Christian
never touch a running system