I use Suse 11.2. I mounted 5 folders from fstab. 2 of them work but 3 do not. The 3 folders that do not work let me enter them, and they let me see everything. I can even create or delete a folder on them, if I am just browsing with konqueror. The problem is that I have a program that will not read them. It’s a program made for my company and apparently it will only read folders that have all of their permissions set to read and write.
The program will read the first two because their permissions are set to Owner, Group, and Others, can view and modify content. (The network folders are all windows server 2003 computers). The 3 folders the program will not read are set to Owner can view and modify content, but Group and Others are “can view content” If I try to change those permissions even in root, it tells me that access is denied. This is what I wrote for my fstab:
The three that do not work are the first one and the last 2.
The network admin says he set all permissions to the network to let everyone read or write to them. I can access and read and write to everything from any other computer. Also there are 4 other machines set up to use these folders with identical fstab entries and they all work. They are running KDE 3.5 and I am running KDE 4.0. I can’t figure it out.
That’s very puzzling. Take this pair for starters: //192.0.3.100/netfolder3 /home/Tim/mount_point5 cifs username=administrator,password=secret,_netdev,uid =Tim,gid=users 0 0 //192.0.3.112/netfolder1 /home/Tim/data/stuff_Files cifs username=administrator,password=secret,_netdev,uid =Tim,gid=users 0 0
The first one works but the second one doesn’t – but the structure is exactly the same for both. Same everything except the IP address (i.e. different servers) and the mount point (mount point is almost the same, no real difference).
So let’s look into them a bit deeper – what do you get as a response to these two commands when the mounts are active:
ls -l /home/Tim/mount_point5
ls -l /home/Tim/data/stuff_Files
The second question is: the windows server 2003 permissions are not set to respond exactly (NB exactly) the same at IP addresses 192.0.3.100/netfolder3 and 192.0.3.1.12/netfolder1 to the particular user called “administrator” on those servers; what’s different between the servers?
Well the answer to your first question is total 0 for the first command… oops I forgot to add that one back to fstab, before trying, and the second gave me a list of the files in that folder. Every file in that folder has the permissions set as drwxr-xr-x. The answer to your second is that there are different user names for that server. I tried one as an administrator and one as a regular user to see if it made a difference. Those mount points are just 2 different folders on the same server. I did try both with the same user name and password as a regular user already and it didn’t work.
ok I tried mount_point 5 again and this time the response from ls -l /home/Tim/mount_point5 was a list of the folders with all of the folders in it with the permissions set as drwxr-xr-x.
I tried mount_point 5 again. This time I typed ls -l /home/Tim/mount_point5 and the response was that it showed me all of the folders in it and most of their permissions were set to -rw-rw-rw- and they had a 1 after them. Some were set to drwxrwxrwx and had an 8 after them.
Are the permissions on the server you are trying to mount from the same for all shares? Or the NTFS permissions?
By the way it might be wise to add something like this credentials=/root/my_credentials in /etc/fstab in stead of specifying your userid and password explicitly, that would save you some typing if you ever decide to change your password.
supposedly I have read write permission for everyone for the network folders. Was there a change made to the way fstab needs to be written between KDE 3.5 and KDE 4.0? or between Suse 10.3 and Suse 11.2? All of the older computers are working just fine with this and can connect with full permissions on everything. They are the KDE 3.5 Suse 10.3 32 bit machines. I copied the lines in fstab from the older machines and put them at the end of fstab in the new machine. I’m wondering if I download KDE 3.5 will that work?
It is not likely a KDE downgrade will fix your issue. The mounting of stuff in /etc/fstab happens at a lower level than your desktop environment is operating in.
When you run “umask” on both systems, do you get the same result? The default value should be 0022 (tested in on 10.0 and 11.2)
I found out something else… The folders that work are on the Mac servers, but the folders that do not work are the windows servers, could this possibly be something wrong with samba?