SAMBA on HP-UX 11.0

[Krishna Prasad]

Does anyone know the highest released version ( depot ) of Samba for HP-UX 11.0.

I can get 3.0.4 for 11.11. I only see 2.2.8 for HP-UX 11.0.

I my need to upgrade to 3.0 because of our pc's recently have been added to ADS? We don't currently use ADS to authenicate the Samba shares, but I believe something has changed on the Widows worksatation that has changed the way it talks to the samba share after it was added as a member to an ADS server? The pc's can still map the drive but it seems to have lost it's group access. I think ( guess ) that the mapping of Unix permissions to Windows attributes have changed?

[john kingsley · Accepted solution]

There is a 3.0.2 version of Samba available for 11.0 at the HP Porting and Archive Center:
http://gatekeep.cs.utah.edu/hppd/hpux/Networking/Misc/samba-3.0.2a/

[Sundar_7]

The latest supported CIFS release from HP is 2.2j that is based on Samba version 2.2.10.

2.2j can work with ADS but cannot use Kerberos authentication.

You can download 2.2j from software.hp.com

[eric roseme]

You do not need to upgrade to 3.x. There is something else going on that is affecting your permissions.

I am confused by your problem statement.

1. Is this opensource Samba or HP-UX CIFS?
2. Is the Samba server a domain (ADS) member?
3. If the clients were not previously domain (ADS) members, what were they members of? (was the Samba server a PDC?)

I apologize if the follwowing appears rudimentry. If your clients are now in a Windows domain, the Windows user must be mapped to a local unix UID for system resource access. Many users use the usermap file, but if the Windows user and unix username are identical, then the mapping is transparent. The mapped unix user must then belong to a local group GID in order to be granted group permissions for resource access.

In addition, in order to manage the user and group permissions from a Windows client (via the file Explorer), you will need to sync your /etc/passwd file with your smbpasswd file (for CIFS, this is /var/opt/samba/private/smbpasswd). CIFS provides a utility called syncsmbpasswd in /opt/samba/bin/ that will do this for you.

The bottom line is that you do not need a Samba/CIFS upgrade - you just need to figure out how your new server/client membership must be configured to provide local group access. If you are using Opensource Samba, then be aware that with HP CIFS Server (it's free) you could just call the response center and make them figure it out for you.

Eric

[Krishna Prasad]

1. OpenSource
2. No, The samba server is not a member of the new ADS server. ( We have been on Novell and we are moving to ADS. )

3. No - It is a stand-alone Samba Server using user security. The PC passes the local-machine token to the Samba Server. It uses the same name and the passwords are in sync.
We are still able to map the drives.

FYI - PC recently added to ADS - before this the same setup has worked 100% for over a year.

[eric roseme]

I tried to duplicate your problem using HP CIFS Server on Samba 2.2.8a. The client was a domain member but the server was not, using "security = user". Group permissions work fine for me in this environment, so I will reiterate that it is not a Samba version issue. There are too many config variables for me to even guess what the root cause is. You can set "log level = 10" and observe what happens during file access for a domain client versus a standalone client.

[Krishna Prasad]

There is something different with inter action between the PC that has joined an active directory domain and the samba server. It has worked for a year. Also, two other PC's that are not part of AD yet, are still working against the same samba server with the exact same permissions running the exact same software.