i'm trying to setup a permanent CIFS share from my nas, but it keeps prompting for a password dispite GUEST access set on the share.FStab is as follows:
Code:
//192.168.0.253/media/ /mnt/nas1_media/ cifs guest,_netdev 0 0
if i do
[code]....
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 am trying to mount cifs through fstab but it is not working. I have an Ubuntu samba server and a Kubuntu client. The share from the server is one dir with subdirs having different permissions and owners/groups. When I do AS ROOT:
Code:
smbmount //192.168.0.254/share /media/maps/share -o username=toshko%pass
the output of the "mount" command is as follows:
Code:
//192.168.0.254/share on /media/maps/share type cifs (rw,mand)
The result is messed up owners with different uids and groups:
[Code]...
I just went from Jaunty to Maverick. I booted Maverick and manually mounted my Windows Network drives by clicking on the appropriate "mount" command in the directory /media.I then created an fstab file like I did in Jaunty. Here is the smb mount command that I had in the fstab file. I had a file with the user id and password in the credentials file.Code://???.???.??.?public_p/media/servername smbfs credentials=root,dmask=0777,fmask=0777 0 0This provided me access to my server for the past 18 months.I modified the fstab file for Maverick which was working fine for 3 days so I would automatically mount the server drives.
View 1 Replies View RelatedHopefully this'll be an easy one (but I wasn't able to find any other posts with the exact same problem).I'm connecting to a large hard drive at work. I can mount perfectly fine. The following is the relevant line in my fstab file:
//XXX.XXX.XXX.XXX/data /mnt/labdata cifs users,rw,exec,suid,dev,username=XXX,password=XXX,_ netdev,fmask=777,dmask=777 0 0
The problem is that when I try to cd to the correct directory, I get a permission denied error. I don't own the mount point, and there aren't general read/write permissions set. But if I change to superuser, I can access it no problem. I can read, write, make directories, etc. So the problem is with my computer--not the remote one.
Now, if I add the option uid=MYID, I can read and write just fine. The system makes me the owner of the directory on mounting. But that's not what I want--I'm trying to allow multiple users access to this file system. I want there to either be a neutral owner (e.g. root) with others having read/write access, or I want the owner of the mount point to be the user currently logged in.
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 have the following line in my fstab:
Code:
//192.168.0.242/websites /mnt/supercube cifs rw,user=XXX,pass=XXX,iocharset=utf8,file_mode=0777,file_mode=0777,dir_mode=0777,uid=XXX 0 0
But it doesn't auto mount with everything and disconnects whenever I suspend my computer. The only way to get it to mount is with
Code: sudo mount -a and it mounts fine with no error.
Did lucid change the way it uses fstab or something? Obviously writing mount -a isn't a huge concern, but it kind of destroys the point of putting it in my fstab.
I have mounted window shared partition to my RHEL 5.4 server through following command
Quote:
But I'm unable to mount the same via fstab.172.20.x.x is my windows server download is my shared folder name.
Suggest me correct fstab entries
My current fstab entry is as follows
Quote:
I've successfully mounted a network share with mount.cifs for the past 2 years using fstab with credfile.
[Code]....
Yesterday I moved this system to a new datacenter, but did not alter fstab or the credfile. The //server/share directory has IP rules in place, but this was updated with the new system IP while we moved the system. Now, I am mysteriously unable to automount //server/share. The local error is 13 (permission denied). The Windows server we are mounting returned a code that is defined as "username is valid but password is incorrect" Again - no changes (content or permissions) were made to my credfile or fstab entry. I've restarted netfs a few times, including rebooting the system twice. What is baffling is I can successfully mount //server/share via command line: Code: mount -t cifs //server/share /mnt/mycooldir -o username=foobar,password=1234
The username and passwords are identical in credfile and the mount options - I copied & pasted username / password from the credfile itself.
I'm using cifs to mount windows share.I have created one credentials file and given the path in fstab to mount at boot time. Now i want to encrypt the credentials file and place that in the fstab file.But it is not accepting.. how to use encrypted file to use in fstab,so that normal users can not watch the credentials inside the file.
View 3 Replies View RelatedQ: 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-1.1.3.1.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:
Code:
martin@linux-y5qw:~> /sbin/mount.cifs //192.168.2.2/data /home/martin/data/ -ousername=martin
Password:
I have the following two lines at the bottom of my /etc/fstab
Quote:
//172.16.6.15/e /tmp/e cifs _netdev,iocharset=utf8,credentials=/root/.smbcredentials,gid=0 0 0
//172.16.6.15/e/Public /var/www/index/pub cifs _netdev,iocharset=utf8,credentials=/root/.smbcredentials,gid=0 0 0
My server address is 172.16.6.1.
If the destination (which is my workstation desktop) 172.16.6.15 is offline when the server tries to boot, the entire boot procedure halts with the following message: Unable to find suitable address. mountall: mount <destination> terminated with status 2 The problem is that my server runs headlessly, and every time something silly like this happens where you'd normally expect the OS to continue regardless, I'm forced to plug a monitor in and diagnose on console
So my question: Is there any way to make it proceed with the boot normally despite the host being unreachable? I could probably chuck a mount command into crontab or /etc/rc.local or a /etc/network/if-up.d script, but isn't this the way it really should be done (/etc/fstab)? If so, then we shouldn't expect the entire boot to halt just because a network share can't be mounted, right? While on the topic of a headless ubuntu server 10.10 not booting without some kind of intervention, I have yet another issue: If the server goes down without proper shutdown (power failure, for example) the grub menu displays the kernel choices and there's no countdown timer. Instead, I have to manually press enter to continue the boot. Is there any way around this? Clearly this should not be the case for a server distribution
Question 1.I have strange problem in OpenSUSE 11.2I have /etc/fstab entry:
//server/projects /server/projects cifscredentials=/root/.credentials,dir_mode=0777,file_mode=0777,_netdev 0 0
service network running
[code]....
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:
Code:
Aug 23 17:35:55 linux-393i kernel: [ 3522.419904] CIFS VFS: Unexpected SMB signature
I use following kernel: 2.6.37.6-0.7-desktop
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.
View 9 Replies View RelatedI 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?
View 1 Replies View RelatedWe 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:
[code].....
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.
View 9 Replies View RelatedQ: How do I mount a CIFS share so that my user stevej has all rights to it?
Summary: I can mount the share as root.
mount.cifs //10.x.x.x/Data /home/stevej/Synology/Data/ --verbose -o user=stevej
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
[code]...
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?
View 2 Replies View RelatedAm 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.
I use wicd at my laptop, since networkmanager didn't work well for me.(unable to connect..) However wicd is not connected before fstab probes my nfs shares during boot, so I wold like either to delay the fstab mount command or make sure that the mount command is performed just after that the wireless connection to my home network is up and running. Running mount -a in terminal works well, but I prefer not to run manual commands at every boot. Opensuse 11.2, KDE 4.3
View 3 Replies View Relatedi am doing a project in which i have to use xen to create virtualised environment.I have already done this.
now i am using the following setup
host os :- opensuse 11.1with ip 192.168.9.19 and with aliasing ip 192.16.9.14
guest os1:- opensuse 11.1 with ip 192.168.9.107
guest os2:- opensuse 11.1 with ip 192.16.9.13
[code]....
I am getting this error when trying to mount my client on the directory I exported in Yast2 NFS Server
View 9 Replies View RelatedSince OpenSuse 11.2 doesn't reconnect samba shares upon a resume from suspend, I wrote a small, ugly script to do so. It's placed in /etc/pm/sleep.d/66samba-remount
#!/bin/bash
case $1 in
hibernate)
echo "Hey guy, we are going to suspend to disk!"
/etc/init.d/smbfs stop ;;
suspend)
/etc/init.d/smbfs stop ;;
thaw)
echo "oh, suspend to disk is over, we are resuming..."
sleep 15
/etc/init.d/smbfs restart ;;
resume)
sleep 15
/etc/init.d/smbfs restart ;;
*) echo "somebody is calling me totally wrong." ;;
esac
and made it executable
(as root)
chmod +x /etc/pm/sleep.d/66samba-remount
The 15 seconds sleep time is useful to me to postpone the remount after WiFi is back online. Perhaps there are way more elegant ways to do so (check for x times if WiFi is on, for example), but I'm no good at bash, and this serves me well. How do I file a wishlist for 11.3? If someone puts a samba share in fstab, I'd assume he wants it connected mostly everytime (at startup for sure... so why not over a standby?) I hope 11.3 just reconnects in-fstab samba shares in a polished way, out of the box.
Step 1 : In Hyper-v Machine i have created two Virtual Ports.
Step 2 : Now for these two diff ports two ip address with different subnet mask(e.g 192.168.9.19 and 192.16.9.20)have been assigned(and have checked using ifconfig).
Step 3 : In Host machine i have added one subnetmask for one machine next one for another machine,however i m not able to ping both the ports from either of the machines having static ip 192.168.9.13 or having ip 192.16.9.107.
Step 4 : If i add same subnet mask for both machine it is pinging properly between 2 machines.
I succeed in uTorrent server's install as a daemon in Opensuse 11.4 and it works great. I've already change my fstab file to add a network drive to be mount on startup localize in /mnt/freebox/. This is also working great. The issue is during the startup, utorrent starts before fstab and thus the network drive is unmount.
In my utorrent init.d daemon script, I ask for $Network starts in first time: Code: Required-Start: $network Is there any possibilities to order the startup and ask to fstab to start before uTorrent Daemon?
I'm a Windows person and will soon be tasked with UNIX/LINUX projects. I'm trying to learn as much as possible in a very short period of time. I'm very familiar with VMPlayer and VirtualBox. Recently I installed OpenSUSE 11.3 as a guest OS on VMPlayer (bridged network). The host is WinXP. I have also enabled shared folder to the host @ CRepositoryInstalls. Question - How do I access the shared folder from OpenSUSE (the guest OS) and vice-versa?
View 2 Replies View RelatedOpenSUSE installed in a Virtualbox Virtual Machine and I want to set a shared folder.
1 - Set up a Virtual Machine and install OpenSUSE 11.2
2 - Create a shared folder on host (HostFolder)
3 - Setup the shared folder in Virtualbox Via the Virtual Machine details or via Devices > Shared Folders...
4 - Install dependencies for running the Virtualbox installer You need to install the right development kernelpackage for your machinetype (use 'zypper search -i kernel' to see what's installed) sudo zypper make gcc kernel-source kernel-hosttype/default-devel
5 - Run the Virtual Machine and go to Devices > Guest Additions This mounts an iso image in your OpenSUSE guest.
6 - Open a root terminal and run
cd /usr/src/linux
make oldconfig && make prepare && make scripts && make dep
cp ../linux-obj/$HOSTTYPE/default/Module.symvers .
make prepare
* A commenter on previously mentioned thread says this step is unnecessary but it doesn't work without on my system. I suggest trying step 7 first and returning to step 6 if that fails. *
7 - Run ./VirtualboxLinux yourhosttype .run from the mounted iso image.
8 - Create shared folder in OpenSUSE (GuestFolder)
9 - Test with sudo mount -t vboxsf HostFolder /home/user/GuestFolder It works? Great! Let's set up the system so it automounts for your regular useraccount instead of root-only access.
10 - Add this line to /etc/fstab HostFolder /home/user/GuestFolder vboxsf defaults,uid=1000,gid=1000 0 0
11 - It works for me but if it still doesn't automount after a reboot; sudo mount -a