I'm trying to talk the studio I work at into switching one of the departments to linux. (likely kubuntu). So I'm trialling it, but having issues mounting windows shares.It's working great; all except that only Root can write to the mount. I've tried a few different things with fstab, no go.Below is my fstab so far, and you can see the mountpoints.
Code:
# /etc/fstab: static file system information.
#
[code]....
I have a Western Digital "My Book" on my network which I have mounted with cifs.
If I go into it and vi a file, all is fine. I can write and save and close. When I open the file and add to it and then try to write it again, I get the message:
"thefilename" E212: Can't open file for writing
The file is owned by me still and the permissions are -rw-rw-r--
I don't understand why it works the first time and not the second. Also this same effect is observable when I save from another program to there. The first save is fine, the second can not be saved.
I've got a Seagate Blackarmor NAS which I can mount with CIFS to my Centos 5 server fine but only root can read and write to it. All other users can only read. I've tried several different mount options but results are always the same.
Specific issue: I'm trying to connect the the NAS so Bacula, a backup app, can write backups to it. "bacula" is set up as a user on the NAS. BTW, I'm pretty sure the OS on the NAS is Linux, and I can connect through windows and write fine.
I am getting an error when I try to mount a CIFS file-system via terminal:
cifs_mount failed w/return code = -22
If I Places > Connect to server, it will open just fine. The share is also accessible from all the other computers on the network.
Google search brought me here to an archived thread which gave a different error number (!)
Desktop is Ubuntu 10,4LTS/Gnome; fresh install with no additional packages installed (so it's possible I am missing something but not sure what!)
I've been mounting our windows network by opening nautilus and typing in the address bar:
smb://<servername>/share
and I am prompted to log in, all is fine.
however, I need to use some apps where I need to pick the folder from a file list, which I can't get to work with the above connection.
I then created the following line in my fstab file:
Code:
//<servername>/<share> /mnt/fileserver cifs credentials=/home/<username>/.smbcredentials,iocharset=utf8,file_mode=0777,dir_mode=0777 0 0
This appears to mount correctly, however there are some filenames on the server with the bullet character() in their name, and by mounting via fstab, the bullet shows as a question mark, but mounting from nautilus shows the bullet.
Anyway I can mount with fstab, and have all characters show properly in the filename?
this subject seems to have been touched a hundred times, but after following all the advice google could provide, i'm still unable to mount cifs shares as user, here's the fstab line
<server> <mountpoint> cifs rw,noauto,credentials=/etc/gattonauth,uid=1000,gid=1000,dir_mode=0770 0 0
i've chowned the mountpoint to the user,
ive tried
chmod +s /sbin/mount.cifs /sbin/mount.cifs
suggested by http://www.linuxquestions.org/questi...-lenny-711337/
I have a bootable utility toolset that I put together with Fedora 14, one of its primary functions is to map a user designated share via script and access information from it. The command that I used, that functioned perfectly, in Fedora 14 was:
Code:
sudo mount -t cifs -o user=provided.account.name //file-server.mydomain.com/share/images /mnt/source
[code]...
My Open Office freezes when I try to save over a network to Win 7 Home Premium. I'm running fedora 14 with win 7 mount via mount.cifs. I have full rw access to windows via dolphin. Does anyone have a solution?UPDATE:this is an official bug.[URL]if anyone has a work around,but every work around I've seen in forums don't work.
View 3 Replies View RelatedI'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 RelatedLinux box info: root@mytestbox:~# uname -a Linux mytestbox 2.6.32-30-generic-pae #59-Ubuntu SMP Tue Mar 1 23:01:33 UTC 2011 i686 GNU/Linux
Windows box info: Windows Server 2008 SP2 Enterprise I've verified via --verbose output that mount.cifs is indeed processing the passed on options.
root@mytestbox:~# mount -t cifs //10.1.1.10/Test /root/testwin --verbose -o credentials=/root/testcreds,rw,nocase,noperm,noacl,nounix,noserverin o,iocharset=utf8,file_mode=0777,dir_mode=0777
[Code]...
Yet, when I type mount all it reports is (rw,mand). The share works just fine, and I can see the masking (all files are showing as rwxrwxrwx as expected etc) but mount is not listing the options?!
Is this normal expected behavior? Is there a bug report on this? I've google'd to the best of my capabilities and could not locate any such information which is why I decided to hit the forums prior to filing a bug.
This is the first time I have run into issues mounting windows shares but I really can't figure this out. Can someone put me out of my windows misery please.
First off, last week I rebuilt my work PC fromWIN7 32bit to WIN7 64bit since then I can no longer mount the window share on my ubuntu server:
I recreated my windows share called "Linux" and used the properties, advanced sharing and added everyone, full access and my domain account full access.
If I browse to \ipaddress I can see my share and access it. From a XP machine I can see the share and access it.
From linux I use the same mount point as before, /linux I use the same fstab and it fails
Code:
I try this manually now:
Code:
Next I try to mount it:
Code:
I looked at my firewall rules and they seem ok.
Next test was connecting to my 2nd pc on windows XP no probs mounted first time.
What is wrong with my new Win 7 setup?
I have mounted a iomega file system on a cetos os machine using
mount.cifs //filserver-ip/directory /home/my-home/mounted-file -o
user=username
(** mounted as root) The mounting works fine.
The problem arises when I try to create a sub-directory inside the mounted directory. All the newly created sub directories become write protected.
I am accessing this file system from R software and it needs to write/create directories in side this mounted directory.
how can newly created sub-directories will become automatically writable, so that R can create new sub-directories and write data inside those directories.
I'm having some trouble in trying to make a clean solution and tougher time searching to not get the basic mounting pages/posts. So I thought I'd throw this out hereFor Oracle, we have an app server that runs /sharedapps and is an NFS mount for all other app/db nodes. What I'm working on now is that on this app server that hosts/exports /sharedapps file system has a sub folder with a CIFS mount (/sharedapps/data/appmount). e thing is that the remote nodes with the NFS mount to /sharedapps don't see the remote data in /sharedapps/data/appmount, only the main app server that has the CIFS connection. Realistically it makes sense why, but I'm trying to research if there is a way to have it do so. This is where I'm struggling. We are working on this in a dev instance right now but soon to be in production. In production, there are many DB nodes that could process a request which is why it would be best to have the NFS connection follow the remote CIFS connection
View 8 Replies View RelatedWe have a network with several computer. We have two file servers (don't ask why) an Ubuntu and an XP as well as many clients. Setting shares on Ubuntu was easy and all clients can see them read and write. but I can't get the Ubuntu clients to see the SMB shares on the XP properly. This is my fstab:
Code:
//192.168.0.100/resources /media/resources smbfs iocharset=utf8,credentials=/home/boss/.smbcredentials,dmask=775,gid=1009 0 0
//192.168.0.9/summer /media/summer smbfs iocharset=utf8,credentials=/home/boss/.smbcredentials1,dmask=775,gid=1009 0 0
[Code]....
I have one NAS device and using samba share one folder without password, how can I use command mount -t cifs to mount this share folder? I tried the below command, but always popup password checking?How should I do mount this folder without password checking?
View 3 Replies View RelatedI am trying to image about 30 laptops with WinXP, and I am using Clonezilla and DRBL for the task. We will start migration to Win7 starting Q4, so for now we are still using XP. I used a Clonezilla live USB to capture a standardized image to a CIFS/SAMBA share on the enterprise file server. The file server does not support NFS. To deploy the image, I used Virtualbox to build a VM with Centos 5.5 and then later Ubuntu 10.10. I mounted the CIFS share to /home/partimag but I found that I cannot share this CIFS mount out as NFS so I was unable to deploy the image with the image still residing on the CIFS; I had to copy the image to the VM's local drive.
Now using the DRBL live distribution, which is Debian based, I was able to obtain the image from a CIFS share and then share it out to the clients to be imaged as NFS (I think). I was able to use the DRBL live for some older computers, but since that hasn't been updated in nearly 2 years, I think it's missing some device drivers for my newer machines so it doesn't work on them -- this is why I looked at using CentOS and Ubuntu. To mount the CIFS shares, I'm using the following command:
mount -t cifs -o user@domain //share_ip_addr/share_name/folder /home/mount_point
Do I need to do something different to enable the mounted CIFS share to be shared out as a NFS share so that the clients to be imaged can see the contents from the CIFS share as a NFS share? The below image depicts my setup. The workstation has two NICs. The 10 network is the enterprise network and the 192 network is for DRBL imaging only. DRBL/Clonezilla does PXE boot and leases DHCP for the laptops. The laptops are shielded from the enterprise LAN; I am not doing any kind of NAT on on the server. The Linux VM is built with dual NICs and are set to bridged mode so they appear to be a separate NIC from the VM host on the network even though they going into the same port on the wall. [URL]
I'm trying to configure a per user samba login for full access to the user's home directory.Mounting the shared directory works flawless when mounting from Windows. I can read, write, create without problems. However, when mounting from Linux the shared space is readonly.
View 8 Replies View RelatedI have a networked raid drive. Thecus 2100. Its running linux, and includes samba sharing. On that I have a folder shared. I can connect to and read and write from nautilus. No problems. However, I can't use other apps through that method. Its not really "mounting" that drive in the sense you'd normally think of (afaik).
If I try to mount the folder, no matter how I have tried so far (-t cifs, smbmount, etc), I can navigate the folders, but if I try to read any file I get a permission error. Looking at the permissions with 'ls -l', everything looks OK. The weird thing is, I can write a file, then read that file back as long as its the same session.
Just now I tried 'smbclient' with no special arguments. Just the server and path url. It asked for my password. Once I was in, I had no trouble getting files. I had a thread about this a while back and there were several links and all sorts of command line options to try, which I did, with no different outcome. I think its got to be something much simpler and more obvious. smbclient and nautilus seem to have no trouble. Anybody know what they're doing differently?
I'm trying to mount some CIFS shares (NetApp) to my Ubuntu 11.04 desktop (64-bit).I am mounting it as a domain user with admin rights and full control over the share.ter mounting it as root, all the files are owned by root and I can't modify them from my non-root user.Here is how I am mounting the share:
mount -t cifs -o domain=example,username=example-user,password=mypassword //myfiler.example.com/myshare$/mydir /mnt/myshare/
This share is a qtree under a volume with security type set to NTFS. (Although I have also tried security type = Mixed) We don't configure user-level access to shares on the filer, we create directories and lay down permissions on those from the Windows side. (Although I have tried explicitly adding my domain user to the access list for the share)
- my windows shares were working fine, since there was aktualization they don't any more
- i have Fedora 12
- my /sbin/mount.cifs und /sbin/umount.cifs have 777 permissions
when I execute my mount with normal user:
/sbin/mount.cifs //sdvbdta01/KADA/ /home/kada/dvb-shares/persoenlich -o user=kada,dom=dvbern,pass=$PASSWD
I get this error:
/sbin/mount.cifs: permission denied: no match for /home/kada/dvb-shares/persoenlich found in /etc/fstab
When I execute that mount with root then it works, but I can't edit documents on that share with normal user
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 upgraded my Karmic OS to Lucid the day after it became available and have been having some troubles - I am having trouble starting the OS. Brief history: I have real troubles with the ATI graphics and spent a while trying (finally successfully) to remove fglrx and associated dependencies. I then rebooted ready to install new drivers. I now get the following error on startup:
CIFS VFS Error connecting to socket - aborting connection
CIFS VFS cifs_mount failed w/return code (-101)
For the last couple of weeks or so, I have noticed CFS errors on shutdown which has meant that I have needed to physically press the off button to turn the machine off, but since I could still operate I left that problem on the back burner "for when I have more time". Don't know if the two problems are related. Anyway, I am currently in the situation where I cannot start Ubuntu at all unless I use the install CD and try the LIVE distro.
My fstab file looks like this:
aufs / aufs rw 0 0
tmpfs /tmp tmpfs nosuid,nodev 0 0
/dev/sda6 swap swap defaults 0 0
(My PC Has a 1 TB drive and a 500 gig drive. The 1 TB drive has dual boot Vista (came preinstalled and I have a couple of games for it - else, yuk) and Linux. The 500 gig drive is a data drive). I'd rather not reinstall from scratch though may have to? I don't know of any way to repair-install the OS - maybe that would be possible too?
I'm setting up Ubuntu Karmic on my sister's old computer for my nephew, he's quite young so my sister asked to install some content filtering. I'll first setup an OpenDNS account and I've installed and managed to get dansguardian and squid working on a virtual machine to try it out. so far it's working pretty well, but I need to secure it form the inside out.
I was thinking of blocking specific outbound ports so he could not bypass the proxy. because by default the firefox configuration can be easily changed. so I have a couple of questions.
1. is it possible to block outgoing ports on Ubuntu?
2. is that the best method?
3. is there anything else I should be aware of to prevent subversion?
lastly, this question is probably unrelated to this board but I've set up a cron job to update a dynamic ip with OpenDNS, the problem is that the password is in clear text in the user's crontab, can I play with permissions? is it possible to run the job under a root account and deny read/write access to a normal user?
So after having spent the past half year preparing to abandon Windows and come over to Debian I finally made the switch last night only to realize I forgot one important thing... I didn't figure out how to map the network drive on my Windows server (currently learning to replace this with Debian as well) to my Debian system.
I have read about 15 links but keep getting the following error: Mount Error (6): No such device or address
Here is what I'm trying to enter into my terminal (with important bits removed for security of course)
mount -t cifs //xxx.xxx.xxx.xxx/Network_Storage/ -o username=xxx,password=xxx /mnt/cifs
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 2 USB drives connected to an XP machine that I rotate twice a month for backups. On my CentOS box, I have that drive mounted at /home/backup using cifs.
Because the drive is mounted on the Linux box, Windows XP complains when I try to "Safely Remove Hardware". As a result, I have to "umount /home/backup", then "Safely Remove Hardware". After connecting the new drive, I then have to "mount /home/backup" in order to use it again on the Linux box.
Now, this question may be a Windows XP question, but I was wondering if there is anything I can do on the Linux box first. Is there anything that can be done on either end, so that I won't have to "umount /home/backup" first?
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
I followed this howto in order to mount CIFS shares on demand. This works great, however, this guide suggests leaving my network passwords unencrypted on the disk. This is a very bad security practice, as the passwords can be easly retrieved by booting the computer using a different OS.
I was looking for a way to secure things up, so I came up with this solution: Instead of storing the passwords plain text on the disk, I store them in a tar file encrypted using GPG. When I boot my system, I open this file to a directory in /dev/shm, and order AutoFS to retrieve the passwords from there.
This does the trick, but I presume this solution is not that secure, since /dev/shm content can be written to the swap partition. Is there any other solution which is a better security practice? Maybe using some sort of keyring service?
I'm using Debian 8.2 from a very recent download of the latest NetInst (less than 2 weeks). I'm sort of new to Linux - More accurately, I've used Unix and Linux extensively in the past, so most of my knowledge is dated. In particular, the whole systemd / systemctl paradigm is completely new to me.
Problem: I've added an entry to /etc/fstab to mount a NAS drive as CIFS. When I do a system shutdown or reboot, the system hangs for 90 seconds trying to unmount the NAS. If I manually umount the NAS prior to shutdown / reboot everything works fine.
I've done a fair amount of investigation and web searches, but haven't found a fix yet. Apparently several people were encountering similar problems about a year back, and it seems pretty clear that the root cause what ordering of steps in the shutdown process, e.g., WLAN being turned off before unmounting filesystems. This seems to have been resolved for most users (no one is discussing it any more), but I'm now running into the same issue. Ugh.
I tried to add a shell script to /etc/rc0.d to umount the NAS first in the shutdown process. This had no effect. I assume this is because the new systemd / systemctl paradigm supplants the old /etc/rc model of runlevel control, though it is rather baffling (to me, at least) as to why /etc/rc* still exists if the system is no longer using it...?
Here's some things I'd like to try, but how to proceed:
1. In the new systemd / systemctl paradigm, how do I examine and change the ordering of steps in the shutdown process? I've seen a lot of documentation on systemd, but nothing tells me how to do what I used to be able to do with /etc/rc with a simple rename of a symlink. If I knew how to look at the order of shutdown and change that ordering, I'm fairly certain I could identify and resolve this issue.
2. Is there some other way to mount my CIFS NAS other than editing /etc/fstab? Is it possible that my manual edit to /etc/fstab is the cause of this issue? My research into systemd indicates that it IS supposed to be compatible with /etc/fstab. I have not yet found documentation describing how to mount a filesystem at boot WITHOUT editing /etc/fstab ...
Running Debian stable. I added the following command to rc.local and made it executable:mount -t cifs -o username=ted,password=computer,uid=mooreted,gid=users "//192.168.1.121/Storage Volume" /mnt/vortexAfter rebooting dmesg throws the following error:
[ 21.400697] CIFS VFS: Error connecting to IPv4 socket. Aborting operation
[ 21.400708] CIFS VFS: cifs_mount failed w/return code = -101
However, if I run the command as root after the system boots it works fine.Been using this method on other distros for over a year. No idea what the problem is.