I just made a fresh install of OpenSUSE 11.4-Tumbleweed and have the latest updates. However fstab lines I've used in the past are not working.
Here's an example of two: //IPADDRESS/share /home/user/mount cifs credentials=/home/user/.scripts/.creds,_netdev,uid=client_user,gid=users 0 0 //IPADDRESS/share /home/user/mount cifs guest,_netdev,uid=client_user,gid=users
I can execute a command
Code: sudo mount /home/user/mount and it works, but I'm wanting all my fstab lines to automount at boot as on other machines.
I have mounted a windows network share using the gnome desktop environment, using Places -> Connect To server.The network share is OK, and I have the icon on my desktop and can see all the files.I want to be able to use this network as well in the console, so I need the mount point.What is the location on the filesystem were this networkdrive gets mounted? I find nothing in /mnt and nothing in /media also using mount to look at the registered mounts, there is no entry for the networkdrive.Nevertheless, I have this networkdrive now open in my desktop, and have an option to unmount it.I know that using the mount.cifs command you can specify the mounting point.
I have been running a server for 3-4 years now, and my shares have been mounting just fine. Well, the network admin looked at a backup and seen that the last date backed up was june. I got to looking around and seen that the share is not mounting. I can mount it with sudo mount -a, which tells me my syntax is correct. I get an error about IPv4 socket not opened and it is aborting the operation when I run dmesg | tail, since I can use the above command to mount later, it sounds to me like it is trying to mount before the network connection is ready.
I have done some looking over some init scripts and found that in the /etc/rc.d/init.r/netfs script it has a line that states that it is checking to see if the network is up before it starts to mount the filesystems and the such. This is set to no, my question is, can I change this option to yes and get my desired results, waiting for the network to be up before it mounts the filesystems.
I am attempting to set up autofs on Ubuntu 10.04 so that it can automatically mount cifs shares when wifi is connected. For some reason, it isn't working. First of all, I know the share is accessible because doing this works fine:
Code: sudo mount.cifs //192.168.0.12/share /cifs -o credentials=/etc/samba/credentials This is in my /etc/auto.master Code: /cifs /etc/auto.home --timeout=60 --ghost And this is /etc/auto.home
After booting, the sda5 and sda8 mounts work fine, but the Windows shares haven't been mounted. If I enter the command: mount -a everything works fine. I don't know if this a timing issue, or something to do with the new systemd stuff, but it has happened in previous Fedora releases from time to time.
The shares get mounted correctly and you can navigate through the directories and open files.The only problem is that it randomly starts going really slow taking 30 seconds or longer to open a directory that has 2 or 3 files in it.I have tried quite a few things to try and fix this without any luck. Its getting to the point where I am having to consider recommending that we use windows instead, which I would rather not do as I think its good for students to experience different operating systems during school.
Q: How can I allow my users to mount a cifs share without an entry in fstab in OpenSuse 11.4?
I have an answer myself. Until OpenSuse 11.2 I could mount my samba shares by making mount.cifs and umount.cifs setuid root. Today I installed OpenSuse 11.4. Unfortunately mount.cifs isn't anymore allowed to be setuid due to security concerns. Security is not an issue in my case, so I copied the mount.cifs and umount.cifs from 11.2 to make it work again:
1. Download cifs-mount-3.4.2-22.214.171.124.x86_64.rpm from this repository (I use 64 bit): "http://download.opensuse.org/distribution/11.2/repo/oss/suse/x86_64/" 2. Extract the files mount.cifs and umount.cifs from the rpm and copy them to /sbin 3. Make them setuid root:
Code: linux-y5qw:~ # chmod u+s /sbin/mount.cifs linux-y5qw:~ # chmod u+s /sbin/umount.cifs 4. Mount your cifs shares as a normal user:
Since upgrading to 10.04 I have had constant CIFS errors in /var/log/syslog
Eg - May 1 10:33:46 eclair kernel: [ 933.789217] CIFS VFS: No response for cmd 50 mid 32895 May 1 10:33:46 eclair kernel: [ 933.794567] CIFS VFS: No response for cmd 50 mid 32900 May 1 10:33:48 eclair kernel: [ 935.721371] CIFS VFS: No response to cmd 46 mid 37294
All shares mount and I can open them etc, but always those errors appear whenever I try and browse to it, read them etc. These shares are mount from a Windows 2003 Server and no other machine has a problem reading or writing to this machine. I have changed the network cable and network cards in both machines, with no success. If I copy a file from a local drive to a CIFS drive, the file on the CIFS drive becomes corrupted.
1. 11.4 x64. 2. Solaris SMB server. 3. Gigabit LAN 4. mounted shares from that server (fstab entries)
write speed: 80-90-100 MB/s read speed extremely slow: 3-4-5 MB/s (really funny - our administrator shoked, but i'm not fun, i need fast lan for work)But when i reboot to windows 7 - i have 60-70-80 MB/s in both directions. Read and Write - nice.What happened? kernel updated and all last updates is applied (exclude kopete-because i use old kopete with animated tray icon).I have to tried many tunes like: "noatime" "directio" and also in /etc/modprobe.d - put conf file with: options cifs CIFSMaxBufSize=130048
I mount the share on my Windows server with following command:
Code: mount -t cifs -o username=Administrator,password='mypassword',rw,dir_mode=0777,file_mode=0777,nobrl,uid=1000,gid=100 //10.8.0.1/users /mnt/
In my 11.3 computer it works well. I opening, copying files like I do in local filesystem. At the same time it's not working well on my 11.4 computer: the share mounts without errors, I see all files, can copy them from server to local computer. But when I'm trying to make copies to server, sometimes I receive messages like "Error writing file ...". Not always, but in the most part of my attempts. find the part of my /var/log/messages file:
I used command as followings. nothing special. mount -t cifs //192.168.55.53/windows$/Home /mnt/ -o user=username%password It works well after mounted. But mounting itself takes 1-2 minutes terribly. After mounted successfully, file transfer speed looks to be normal.
I have a SMB share being mounted during boot using a /etc/fstab entry.All that seems to work fine, but on shutdown or reboot I found that the system hangs for a variable period trying to unmount the share. It appears from the log that the unmount is happening after the network connections are closed.Is there someway around this, or is there some other way I should be mounting the share so that it is closes successfully at restart or shutdown?
We recently moved to a new home and I am trying to get my home file/print server set up again. Thanks to swerdna's excellent website, I got my server box (just upgraded from 11.0 to 11.2) running Samba and serving my shares over the network, and my "client" machines can access them without a problem.However, I'm not having much luck setting up CIFS mounts on my Linux desktop. I have my all-purpose user added to the Samba auth list (via smbpasswd), and configured my client as swerdna's howto's specify, and I can access the files just find. However, when I try to mount the shares with this command:
Code: mount -t cifs -o username=klein,password=klein //192.168.1.70/sharedmedia /home/zak/SharedMedia/ I get the following error:
I need to mount a windows share on my OpenSUSE 11.3. I get it using the mount.cifs command (by itself or using cifstab), but only root can rw file. I try the uid/gid parameters (also using forceuid) and the file_mode/dir_mode parameters, but I get the same behavior: all files and directory with rwxr-xr-x permissions and root/root (user/group). I read the whole section FILE AND DIRECTORY OWNERSHIP AND PERMISSIONS in man mount.cifs but nothing works.
Using Dolphin in Super-User mode, I can copy files and directories from the share to itself with no errors. Using Dolphin in Normal-user mode. I get the failure "Could not change permissions for...". The file is copied, but its owner,timestamp and permissions are wrong. If a subdirectory is involved, the copy aborts.
Using Windows XP I can copy files and directories from the share to itself with no errors.
Testing: If I mount with uid and gid, then my normal user can not access the share. mount.cifs //10.x.x.x/Data /home/stevej/Synology/Data/ --verbose -o user=stevej uid=stevej gid=users
Synology DS211 - There are 2 users on it. One of which is stevej and the other is julie. Rights RWX are applied to the users and the group called users. All files have stevej as the owner and users as the group with RWX Opensuse 11.4 - There are 2 pc's. One is run as stevej. The other pc runs as julie Windows 2000 - Runs as stevej and maps to the share as stevej.
Works as expected Windows XP - Runs as julie and maps the the share as julie. Works as expected Ultimately, I want the shares to automount at boot, or login and give the user full access. I have been to Swerdna's page and done as much as I can, but still no luck.
I'd like to have a CIFS drive mountable for various users. Each user uses different credentials and I want the drives to be automounted without using sudo-rights. I imagine the best thing to do would be to have the fstab entry point to multiple credentials files. Is there a way of doing that?
Am in the process of upgrading from an ancient OpenSuSE release (7.2) to 11.2. One thing I have been unable to do that worked fine under 7.2 is remotely mounting a compact flash drive from an XP machine. Worked fine for many moons on 7.2:
# mount -t cifs -o rw //xpbox/'cf (H)' /cf0 I get: mount error(12): Cannot allocate memory Other cifs mounts of hard disks work fine.
I found a posting that says this means the memory allocation error is from the XP side. It says to fiddle with the XP registry, specifically IRPStackSize. I was not confident this fix would work since there should not be anything significantly more consuming with 11.2 compared to 7.2, and indeed, I got the same error after changing the parameter to 18 and rebooting the XP machine. Any ideas? I have some suspicion that the space and parenthesis in the share name might be fouling up someone. XP forces the share name to this for some reason.
Was enjoying my new experiences until I tried to access/see my OpenSuse 11.4 install (Within VirtualBox on Windows 7)I can surf the net and download packages etc but from Windows 7 the Virtual OpenSuse7 does not show up.I know the windows network works because I also have Ubuntu10.4 on VirtualBox and that I can see and access fine.Change to OpenSuse and it all goes down the tubes, doesnt even show up in the Network on Winsows 7With Ubuntu I have etho setup to use DHCP automatically.I've tried numberous settings unsuccessfully on Suse and I think in the process have probably changed something incorrectly, but it didnt show up in Network places even before I started fiddling.Settings within Network Settings are:
1) Global options Network Setup method: Tradional with ifup IPv6 Protocol - Enabled
i'm trying to automount a samba share on computers startup, everything works just fine when the network adapter is controled by traditional way ifup but when i'm switching to NetworkManager doesn't work anyway. i'm hiding the share information from the common user by using the /etc/samba/cifstab as i read on intrernet, in the cifstab i put //server/share /home/user/share cifs sername=user,password=pass,uid=1000,_netdev .could anybody give me a hint or tell me where to look?
I wonder how to get Samba share access working well...Dolphin supports Samba but it doesn't really mount anything, it seems... Non-KDE Applications therefor can't access samba that way. In Gnome there was a workaround for the same problem. You could simply go to ~/.gvfs in any application and find the samba mounted there.Is there anything like that in KDE? I set up a Samba mount via /etc/fstab for now but that is quite annoying because it fails after each Suspend, changing WLAN Access Points, etc. Then I have to go to the console and manually launch sudo mount -a to get it working again. How can I make things more comfortable?
P.S.: I'm even up for using something else than Samba to talk to my fileserver. However I don't know of anything that would work better in this regard. (NFS would have the exactly same problem for example)
I followed samba setup per thread Samba and Suse: HowTo Set up an openSUSE-Windows Home Office LAN/Network. Versions 11.x and then upgraded my samba from the special repository per advice at Samba broken after latest security update 11.2 - openSUSE Forums I can now see all my boxes on the network from either an XP or linux box and I can access my linux shares from any XP box but I can't access any XP share from my linux box (openSUSE 11.2). I get an error that reads "The file or folder smb://SharedDocs does not exist"I can see the SharedDocs folder under the XP box in samba shares though. And it really does exist on the XP box.
Using SuSE 11./4 on two machines. Successfully set up a server to share a folder. The client is able to read files from the folder, but not write to them.the client perspective, the shared folder permissions are read and write if owner, read only for all otherHowever, the server shared folder has been set up for sharing, and the permissions are set for read and write to all.
One more thing. When the client goes into the samba share, it sees the workgroup. Clicking into that, it sees the name of the server computer. Clicking into that,it sees two folders: "profiles" and "users". Clicking into "users" goes into the shared folder. I tried setting the permissions from the client side on the "users" folder using root privileges to allow reading and writing without any success
I can't for the life of me figure out why I cannot browse my own shares from my linux boxes. both run OpenSuSE 11.3 I follow swerdna's tutorials and reboot several times but don't have a clue as to whats going on to prevent me from viewing localhost shares or 2nd linux box shares. I get 'unable to mount location, Failed to retrieve share list from server' error when I click on my workgroup icon in nautilus.
I am posting this as I have tried several times to work this out. I have read article after article, post after post and tutorial after to tutorial to sort this issue. I have an Ubuntu 10.04 machine running as the LDAP and NFS server with two Opensuse 11.3 desktop machines. Both of the Opensuse machines can login using the LDAP server for authentication and this works fine. The server also exports the NFS Shares no problem but I am unable to mount the shares from the Opensuse machines. I have been using Yast, NFS Client to mount them.
Yast NFS Client can see the shares and lists them however when I apply the settings it states:
'Unable to mount entries in etc/fstab' I need to mount the shares according to the LDAP details as I want the users to be able to access their files no matter which machine they login at. Can anyone shed any light on the issue. Any help would be great and I would be enternally grateful as I am now beginning to pull my hear out slightly.
Having a bit of a minor issue with samba on Opensuse 11.4 64 bit. My problem is that I can't view my samba shares in Dolphin although I know they are there. If I bring up dolphin using the Opensuse shortcuts to samba I get this
My computers / drives attached to my network should be viewable here yet they are not. However, if I type in the address directly I can view and access my shares.e.g.
Here is a copy of my smb.conf
Code: [global] workgroup = farcusnet netbios name = ThinkPad passdb backend = tdbsam name resolve order = bcast host lmhosts wins printing = cups
I got connecting to our NAS over NFS working perfectly. Direct NAS Reading & Writing - How? But on Saturday I found out it had stopped working. For no apparent reason, not straight after an update either I don't think. When I manually try to mount --verbose:
mount 192.168.100.14:/IHL /mnt/IHL --verbose mount: no type was given - I'll assume nfs because of the colon mount.nfs: timeout set for Tue Jul 6 14:48:32 2010 mount.nfs: text-based options: 'addr=192.168.100.14' mount.nfs: Unable to connect to 192.168.100.14:111, errno 111 (Connection refused) mount.nfs: mount to NFS server '192.168.100.14:/IHL' failed: System Error: Connection refused
Corresponding fstab line that used to work just fine. 192.168.100.14:/IHL /mnt/IHL nfs auto 0 0 For now, I can drop back to Samba but this is a PITA as I can't open OpenOffice documents and write to them directly on the NAS. The fact smb://192.168.100.14/IHL works proves networking wise we're cool too. There is no firewall between this PC and the NAS, the NAS is instructed to allow my PC's LAN IP full access. OpenSuse's software firewall has been told to allow NFS Client too. Why would this setup break out of nowhere? How can I debug this best? I see nothing relevant in /var/log/messages How can I get it to work again? A hopeful reboot didn't do its usual wonders...