CIFS Client Upgrade ... New Problem with Group Access

[A. Daniel King_1]

I've just updated CIFS Client from A.01.09.01 to A.02.02 on a test box. I had a previously working share which now causes problems from mount -a:

DOS: Access denied

I found that I needed to rebuild the user database and run:

cifslogin -s -U joeuser //1.1.1.1/share

Where joeuser is the remote user and share is the remote share. root is the local user. Then I needed to mount the filesystem, which was previously in fstab (mount –a got it). This time the mount worked, but other users could not see the share.

Previously, I was able to allow all users of the HP-UX box to access this share for reads and writes. The server side has not changed. Now, only root can read/write to this share. It is not a public share.

I realize that I can go to each individual account and cifslogin with the save option. However, I wonder if there is a way to avoid this. I know I’ll forget when I add a new user to add them to the list.

Q: How does one allow full-system access to a CIFS share under version A.02.02?

The old cifslist looks like this:

$ cifslist
=========================================================================
server 1.1.1.1:
=========================================================================
Remote Username: joeuser Local Username: root

Share: \\1.1.1.1\share
rw /sharedir

The new cifslist looks like:

Mounted Object Mountpoint State
-------------------------------------------------------------------------------
\\1.1.1.1\share /sharedir M
===============================================================================
Server Local User Remote User Domain State
-------------------------------------------------------------------------------
1.1.1.1 root joeuser LS

[Zinky · Accepted solution]

Daniel,

Have you tried :

cifsmount \\w.x.y.z\share /sharedir -s -U joeuser

With this you need not have entries in /etc/fstab for the mount and it will survive reboots.

Also, what's your permission on the /sharedir?

Have you checked if /etc/opt/cifsclient/cifsclient.cfg is properly configured post upgrade?

[A. Daniel King_1]

/etc/opt/cifsclient/cifsclient.cfg is radically different. I'm still sorting THIS part out ...

[Zinky]

Most important thing there is your :

domain = "YourDomain"
guestUser = "root"


And restart CIFSCLIENT:

/opt/cifsclient/bin/cifsclient stop|start


Cheers.

[Eric Raeburn]

Daniel,

Eric from the HP CIFS Client lab here. It is not clear to me just what method you were using with A.01.xx, that you are trying to re-create with A.02.01, but it sounds like you were using the "guest user" feature to allow all users access to the mounted cifs server, so that they would not have to manually log in, or each have individual entries in the user database.

On that assumption, I offer the following:

In A.02, the "guest user" feature has been simplified and improved. You no longer need a user database entry or a generic unix user. The remote, generic, cifs username and password are set in the configuration file, and you're done. Any user logged in to the HP-UX system can access the mounted CIFS share. Further, each unix user who does this will be listed with their real local (hpux) account name in the output of cifslist. The parameters in cifsclient.cfg are "guestRemoteUser" and "guestPassword".

This is documented on p.46 of the Admin Guide here: http://www.docs.hp.com/en/B8724-90067/B8724-90067.pdf

If I have misinterpreted your inquiry, please post a reply stating precisely what procedure from the previous version you are trying to replicate in the new.

BTW, the prior post stating the importance of setting the domain is likely based on a misunderstanding of that parameter. Configuring the domain on the HP CIFS Client is almost never necessary.

Good luck!
-Eric

[A. Daniel King_1]

Changed parms did the trick.

guestRemoteUser/guestPassword did the trick.