However, autofs does not work: the /msrv directory appears and disappears when I start and stop autofs; but when I enter "cd /msrv" followed by "cd Share05" in the terminal, I get the "bash: cd: /msrv/Share05: No such file or directory" message after the second command.
There are a couple of way to mount Samba shares, but I prefer using "autofs" which can mount them on the fly. Use the autofs daemon to have shares automatically mounted on demand. The netfs service (installed by default in Fedora) is not a daemon and can only mount shares on boot, (it can't mount them on demand).
* Install the autofs package:
Code: yum install autofs * Edit /etc/auto.master (the master map file), and comment out all lines (with #). This avoids conflicts with the CDROM (which is handled by Gnome), etc. Save the file. * Create a new file /etc/auto.cifs, with the contents of: Code: #!/bin/bash # $Id$
[root@serv03 /]# ls -l /media/exPort/mMusic total 16 drwxrwxr-x 11 databank lhome 4096 Jun 23 21:25 iTunes drwxrwxr-x 3 databank lhome 4096 Aug 19 2010 Network Trash Folder drwxrwxr-x 3 databank lhome 4096 Aug 13 2010 Streaming Radio
But it doesn't work - neither it throws any errors in, nor does it mount the share. All I need is to mount "/mMusic" (i.e. /media/exPort/mMusic) as "serv03:/media/nMedia/mMusic" so that tree looks like this:
Running 8.3..On 7.6 I had a automount and I was able to mount/unmount without issue. With 8.3, I can mount, but when I am in Thunar and i unmount, it gives me a permission denied.In /etc/groups I am in plugdev.
We have a homegrown process that runs on a windows box and produces a csv file. We mount the directory these are output to using autofs/cifs and then process them using a program on our linux database servers.
Is there a way from linux, looking at the cifs share, to tell if the target file is currently in use by a process on the windows box? We are having issues where an incomplete file is being processed occasionally.
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 cannot mount my windows share automatically with fstab and have the files be R/W. They are only mounted as read-only.I have tried several dozen commands in the fstab file with many mount points and different users. The share is on a Windows 2000 server, but NOT a domain controller.Thing is, using the Places|Connect To Server|Windows Server menu selection, it works fine. And when I use that, the share shows up on the desktop. However, in some programs I cannot see the share in the open/close dialog boxes. I can however go to /mnt/server to see them if I mount them in fstab. The files just open as "read only" that way however.Have tried... on last line of fstab mount command.....rw option, +777 option, using IP address of server, using server name.
Same result (as fstab) if I do a manual mount command, then a mount -a. Mounts Ok, just as "Read only". ex: sudo mount -t smbfs //192.168.1.xxx/sharename /media/server -o username=xxxxxx,password=xxxxxxxxThis has been the case with Ubuntu 8.04 until my current one, 9.10. Ubuntu (if you are listening) really needs to make this easier. It truly is basic network stuff that for some reason is rather difficult to do. Read only access is not actual network access and my other option (having to manually connect via the drop-down menu) each time I boot up is a pain.What is different about that "connect to server" option on the menu that makes it work? It'd be great if there was a check box there that said "remember this connection". Then all would work fine.
We have a computer here with stuff on it we all use. If I load up my Windows XP VM and open it through My Network Places it loads up just fine. In Ubuntu Nautilus complains that it cant mount the share. If I do:
I have 2 Ubuntu machines: a desktop in my bedroom, and a laptop.
I have my music shared on my desktop machine, and can access it through the network menu item in the nautilus manager, but I want the files from the share to be mounted on the disk so I can access it through the commandline.
If I right-click the shared folder in Nautilus, it says its location is smb://rob/music
If I do:
mount -t smbfs //rob/music /mnt/music, it tells me that it cant locate rob.
So I try "ping rob" and that doesn't work.
I can't make a hosts entry for rob which happens at this moment to be 192.168.0.8, because my router assigns different IP addresses to various machines at different times, and I cant seem to find a way to make static maps from MAC address to ip address.
So, how come nautilus can see my samba share on the machine "rob", but the mount commands cannot?
I have a network PC running Win7 that u use for storage of all my media; movies, music and pictures.I can connect and use the share just fine using the "connect to server" option under places menu.I think i need to modify the fstab file but I am not familiar enough with it to do this.Have searched other threads for help but I am doing something wrong.HP Laptop running Ubuntu 10.10 connecting to a win7 share through a router.
I have been searching around but could not find an answer that suits my problem.Here is the line I have in my /etc/fstab//192.168.1.188/openshare /mnt/lacie_nas/openshare cifs errors=remount-ro,iocharset=utf8,file_mode=0777,dir_mode=0777 0 0The remote directory is a LACIE NAS.At boot the directory is not mounted but if I execute the command "mount -a" it works perfectly.
Usually you put external mounts in the /mnt folder, then link there with a symbolic link if you want access from somewhere else. By keeping all of your mounts in /mnt its easier to manage them as your system and ability grow.
You need to make mounts as root. Mounts take the data in the target and put it on top of an existing folder. When you mount something on top of a folder whatever was there becomes invisible until you remove the mount on top of it. If there is a problem with a mount and it does not work, any writes to the mount will go to the folder underneath, and any data you expect to read from there will not exist.
In making a mount you should realize that the char requires an escape char in bash to show up in the final output to the command. The escape char is also . Therefore to show \ in a Windows command, you need to type \\. Also, spaces must be escaped once with .
You should substitute your ip or name for 10.10.9.5
Reminders: Make sure your Windows folder is shared read/write if you need to write to it.
You probably want to change permissions on /mnt/WindowsDocuments to 777
Tips:If you want a link from your desktop to your Windows "My Documents" folder you can now do this:
This will make a symbolic link to /mnt/Windows, and if you execute: ls -l ~/Desktop you should see the links information in the response
Finally, if you want to keep a local backup of what's on the windows box in a local folder you could do:
The ~ char is shorthand for /home/<uername> and represents your home folder.
The result of the rsync command is to make a copy of WindowsDocs (which points to your mount at /mnt/WindowsDocuments which is linked to your Windows machine shared 'My Documents' folder) and put it into ~/WindowsDocumentsBackup
As always, make use of the man command if you get confused or the info command for more detail. ie man rsync
Does anyone have any good articles on mounting a Ubuntu volume as an iSCSI share on a windows box? Originally I was just going to use a SAMBA share but it turns out samba has issues with my lan security. So I thought since all I really want to do is create the share on my backup server that an iSCSI device would do. Been using the following article with limited success... [URL]
Following instructions that I received from the Fedora 10 Guide, I recently edited my etc/fstab file so that I could auto mount my Windows share. It worked the first time, but when I rebooted, I noticed an error saying that Linux could not not unmount the cifs shares. Eventually it did reboot, but now I cannot mount the share at all from fstab. When I run the command #mount -a and then #mount, my share is shown to be mounted although I cannot access it and there is no link to it on the desktop like there was the first time it mounted. I basically want my Windows share to be permanently mounted with read/write permissions. My Distro is Fedora Core 10 64 bit. How can I resolve this issue?
We have a Windows server at work that has several shared directories. For whatever reason the lab administrator has required clear-text passwords for it. There is a registry tweak for Windows boxes. Nautilus can't mount shares because it is trying to use an ecrypted password. Ironically enough the Windows VM I have running in Virtual Box can mount the shares.... smbclient can see the server and shares if I specify a clear-text password option.
And then i get an error instead of my shared files
I assure that the /home/baronobeefdip/share directory exsists and i am using the username and password that exsist on the server's system (the username is baronobeefdip and the password i would like to keep secret)
What am i doing wrong here because something is wrong
And for refernece here is the result from the
I want to the get one that is commented as the "debian floor computer"
I'm having some trouble mounting a Samba share on my two Ubuntu machines. The Samba share is setup so that all files are readable and writable by everyone (it's only accessible via the local network). When I create a new folder on the share with either of my Ubuntu machines, the folder becomes non-writable by anyone ie. I can't place anything into the folder. I'm using the following command to mount the share:
I think the problem is with the way I'm mounting the share on my Ubuntu machines. If I go to the share using smb://192.168.1.160 in a file browser, I can create new folders which are readable and writable by everyone. But, if I create the new folder where it's mounted at /mnt/backup, no-one can modify or change it.
I've mucked through and figured out how to mount a windows share. I can access the folders I was looking for, but the windows share was not what I thought it would be. I was looking for the specific shared folder. Instead I got a root level parent directory that included the folder I wanted, and a couple others.
smbclient -L <ipaddress> gives me a parent directory on the root
First question: Can I mount a specific folder within a share? Second question: Could somebody define share? I thought it was the specific shared folder, but that doesn't seem to be the case.
A few days ago I got this Ubuntu box (9.10) to connect to the Windows network in our house. Sharing printers and files. Life was good. But today, Places > Network > Workgroup tries to connect for about a minute then I get a "Unable to mount locations, Failed to retrieve share list from server" error. The only thing I recall changing at around the same time was adding Wine.
Setup clients on a LAN to automatically mount NFS shares whenever the fileserver is up, without using autofs. Instead a simple bash script which checks if the server is up, and if the shares need to be mounted or unmounted is called by a custom upstart job. For a small office or home network populated with Unix-like computers (e.g., a few Ubuntu desktops or laptops and a fileserver), NFS (Network File System) is a good way to share storage space and centralise the backup of important documents. However, having a fileserver running 24/7 is often overkill for such a setup.
One way to have clients mount NFS shares automatically when the fileserver is turned on, is to use a package called autofs. Unfortunately, there are a few unresolved issues with using autofs in combination with NFS. In my case, when autofs tries to mount NFS shares when the fileserver is turned off, the Gnome desktop, and Nautilus in particular, becomes extremely unresponsive, regardless of the options used. Attempting to mount the share manually from the command line when the server is down however, does return a message of failure quite promptly, without hanging the desktop.
To solve this issue, I wrote a simple bash script that is run through the upstart system. The script simply checks if the fileserver is up, if the shares need mounting or unmounting, and then sleeps for a while before checking again. This works out quite well, so I decided to share this information in case someone else runs into these issues. PrerequisitesThis howto assumes that you have an NFS server set up with shares exported, and one or more clients capable of mounting those shares. For more information on setting up NFS shares and mounting them on a client from the command line, see: SettingUpNFSHowTo.
Clients should be able to ping the server to determine if it is running. Naturally, you need administrator access on the clients to install the script and upstart job outlined below. This script assumes that the directory paths of the shares match the location where they are mounted. In my case, the fileserver has two shares: /media/Storage and /media/Backup. On the clients these shares are mounted on the same paths. If your setup deviates from this, the script needs some modification. The script From the desktop of one the clients, paste the following bash script as a new file in your favourite text editor:
#!/bin/bash # The hostname or IP-address of the fileserver: FILESERVER="myfileserver.local" # Check every X seconds (60 is a good default):
Now adjust the FILESERVER variable. In this example, my fileserver is called myfileserver. By default, Ubuntu sets up your networking environment in such a way, that computername.local can be used to reach that computer over the local network, so the network name for myfileserver is myfileserver.local. Of course, you can also use the IP-address of the server. Next, change the MOUNTS variable to match the NFS shares exported by your NFS server. MOUNTS is an array; multiple entries are separated by spaces. So if you have one share exported as /media/MyShare, that line would look like this:
MOUNTS=( "/media/MyShare" )
An advantage of mounting shares in /media, is that they automatically show up as mounted drives on the user's desktop. Note that this howto assumes that you use the same paths for the share on the server and client side! Save the script to your desktop with an obvious name. In this example we call it mount_my_nfs_shares. Open a terminal and cd to the desktop. Make the script executable by calling:
chmod +x mount_my_nfs_shares
Next, move it to a place where it can be called by our upstart job, but also from the console to test. A good place to put such custom executables is /usr/local/bin.
sudo mv mount_my_nfs_shares /usr/local/bin
This script uses the logger command to tell the system's log what it is doing. To test this script, open up two terminals; in one, execute the following so we can monitor the log messages:
tail -f /var/log/syslog
In the other, simply execute mount_my_nfs_shares. If the script works, your shares should show up on the desktop and the computer:// location in Nautilus. If the fileserver goes down or becomes unreachable, the shares should disappear, and reappear when the fileserver comes back on-line. If this works, move on to the next step. Installing a custom upstart job The next step is to have the clients automatically run the above script when they are booted. We can use upstart for this. Create a new text file, and enter the following:
# mount_my_nfs_shares - mount NFS shares on fileserver, if present description"Mount NFS-shares" start on (filesystem) respawn
How the script works The script enters an eternal loop and keeps checking if it can reach the fileserver once every minute (unless you adjust the INTERVAL variable). If it can reach (ping) the fileserver, it checks if the mounts are already mounted by searching for them (grepping) in the output of mount. If they are not mounted, it tries to mount them. Else, if the server is down, it looks in the output of mount to see if these mounts exist. If they do, it tries to unmount them with the -f flag (useful for unmounting unreachable NFS shares).
I have a machine (mercury) on which /home/hyperhacker/video is a mounted external hard drive while the rest of /home/hyperhacker is on the internal hard disk. I have a second machine (konata) using autofs to automatically mount mercury:/home/hyperhacker in /mnt/mercury as needed. This works, except /mnt/mercury/video shows up empty.mercury:/etc/exports has: Code: /home/hyperhacker konata(ro,subtree_check)/home/hyperhacker/video konata(ro,subtree_check) and I've tried a few variations in konata: Code: $ cat /etc/auto.master
Because of NFS traffic congestion, I am trying to use autofs instead of fstab(NFS) to mount /home and /data directories on our system (from a NFS server). I have it up and running - users can log in and their /home directories work fine. However, when they need to save a file (openoffice or nautilus) they cannot see the directory tree to locate folders for saving. I have tried setting the --ghost option in auto.master, and I have tried commenting the BROWSE_MODE in /etc/default/autofs. But no luck. Using the terminal, I can go a folder and see subfolders using ls -la. They then appear in Nautilus, but later disappear. Since this is a school network, I can't expect teachers and students to use the terminal to save files. They are used to using Nautilus, with our regular NFS mounts.
Hi Linux Forum People! This is my first post. Somehow I'm not able to mount directories from other machine using autofs. Autofs maps successfully loaded into NIS client, but autofs does not recognize them. Please see belowI'm running RHEL4
I am attempting to mount an NFS share that has been setup on a Windows Storage Server 2008 (R1). Initially, I could not even mount the share, though it would show up using "showmount -e <server_ip>". After adding the "ANONYMOUS LOGON" user to the NTFS permissions and granting the "Full Control" permission, I was able to successfully mount the share and read from it. However, I cannot write to it. The NFS share is set to allow anonymous access, UID 0 and GID 0. The appropriate host is listed in the NFS Share Permissions with Read-Write permissions, and ANSI encoding. Root access has also been allowed. I also tried granting the "Everyone" user full control in the NTFS permissions as well. See screenshots and console quote for clarification if needed.
Hi, I have a server at my home which is a Ubuntu 9.1 which is setup as a NFS server using NFS v3. I am also using DYN DNS to access my home server remotely from another location using SSH. Everything works good, I can sucessfully log in to my server from my laptop via SSH, however my problem mounting my NFS share which consists of appx. 300 mp3 files. My question is:
1 How Do I Tunnel a NFS share through a SSH tunnel?
2 Is there any other configuration? needed to be done to the router?
3 is there anything needed to be configured to the server or my laptop?
4 Manual mounts is fine for me I don't care about automounting.
I just want to be able to mount the NFS share via the SSH Tunnel and play my music and access other files from my server.I just need the steps to set up this connection.
In Nautilus, I can find the share under Network which I want to mount. When I double-click on the desired folder, I was prompted for a username, domain and password. However, I could not log in; there was no error messages, but Nautilus kept prompting me for my username etc..It would seem like I've entered the wrong details, but I've used a Mac OS to access the share using the same wired network and I had no problems doing so.So what could be the problem? Am I missing some setting? Or is the Windows share setting denying access to Linux systems?
I have been looking into how to get Nautilus to emulate the windows "map network drive" feature.
I have found several howto's that use various command line utilities to try to do this, however they tend to be like trying to use a sledgehammer to fix small dents.
When I connect to a share server, Nautilus puts a directory on my desktop that only Nautilus seems to be able to see and use. I would like to be able to access this directory with non-Nautilus applications.