SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have just upgraded Suse 10.0 to 10.2
10.2 uses CIFS, and SMBF seems to be deprecated.
Our networked Linux file server runs Samba. When I mount a Samba share that has restricted permissions, the share has a "lock" icon visible in Konqueror. the same share was perfectly accessible with my same credentials in /etc/fstab with Suse 10.0. Using the same credentials in 10.2 however, I cannot access the restricted shares. The shares are mounted OK though. All other shares which do not have the same permission restrictions, work fine, and I can read, write and execute in those.
Any ideas as to how to solve this would be greatly appreciated.
it's not clear for me why you give arguments like "file_mode" and "dir_mode". These options should be set on server side in /etc/samba/smb.conf
Dis you check the file system permissions? I had often the problem I could not access a samba share, configured by samba a thousand times, and the local directory and file permissions were not set propper.
Greets
Shaddy
P.S. Why did you give your password as argument in fstab? That is very unsafe :-) I think there a better solutions where you can write a hash of your password to an external file, which can be named at mount time. Look at smbpasswd
noperm option fixes permissions check problem in Suse 10.2
Just to close this - I added the option noperm to the entry in fstab, such as . . . rw,noperm,etc
and removed unnecessary part,e.g. file_mode=0777,dir_mode=0777,uid=1000,gid=100 0 0
The line now reads:
//192.168.1.9/it /home/bert-berlin/it cifs rw,noperm,username=bert-berlin,password=****
Since I am not concerned about theft of my password on our Company network, there is no reason to use Shaddy's suggestion for protecting the password.
The addition of noperm seems to prevent the Suse client from doing unnecessary permissions check (which fails). The server side remains unchanged (it is properly managed by an IT specialist).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.