Fedora :: Mount Nfs Shares On F11 To A F14 Machine?
Oct 9, 2010
I'm trying mount nfs shares on f11 to a f14 machine. They are all sub-folders of /media, they all have the same owner (me), same group (ditto) 0x777 protection set. In some cases I can see files in the sub folders but other folders remain hidden. here is a copy of my exports file
I currently mount my smb shares by adding the appropriate line to fstab. Now my son also uses my laptop (F13 by the way) and I would also like to automount the shares for him but as a different user because there are some directories he should not have access to.
This morning my NFS shares mount but permissions are all NOBODY NOBODY. If I ssh to the server to check the drive(s) permissions are all as they should be! Exports there are fine as is my local fstab. I hope I am just suffering and update glitch because they usually go-away in a subsequent update.
I just spent an hour and a half trying to track it down with no success - time to give up before I do real damage (to which I am prone ).
I am unable to mount Windows shares on Fedora 12. From Nautilus, I can navigate to the shares, but when I attempt to open one I get a dialog "Password required for share ... on ..." asking for username (prepopulated with my username), domain (prepopulated with MYGROUP) and password. I have the same username on the Windows box, but when I enter the password and click Connect, the dialog just pops up again. I'm not sure what "domain" is, tried with my Windows workgroup name, no good. If I blank out either username or domain, the Connect button is disabled.
I tried using the mount command:mount -t cifs //192.168.0.2/... /tmp/mnt -o username=adrian,password=...,iocharset=utf8,file_m ode=0777,dir_mode=0777 That did work once, but now gives the useful error message:mount error(5): Input/output error Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) I can run Windows instead on the client machine, and that gives me access to the shares, no problem.
I have libsmbclient-3.4.5-55.fc12.i686, but that was installed a month ago. I don't see any more recent changes to anything relating to the samba client. I've never had to enter a password to access Windows shares. Actually, it looks like the problem may be on the Windows side, although as far as I know, nothing has changed there. Using smbclient with debuglevel set high, I see failures with this error:SPNEGO login failed: NT_STATUS_REQUEST_NOT_ACCEPTED Every now and again, I can connect to one or more shares, but after a few attempts, I can't connect to any more. Tried rebooting the Windows box, but that's had no effect. Oh, and "smbclient -L" shows domain as the host name of the windows box, but anonymous login (smbclient -L -N) shows domain as the workgroup name.
I've had my FC11 x86_64 installation up and running for 6 months. Until a week ago, I was able to mount windows shares through Nautilis using their netbios names. About a week ago, this all broke with no tinkering on my part. Now, I can mount the shares using the IP address, but not using the netbios name.
When I make he attempt either from scratch or by using a previously working bookmark, I get "cannot display location "smb:\..." When I browse the network using Nautilis I can see the workgroup, but when I try to open it, I get "unable to mount location. Failed to retrieve share list from server." When I use nmblookup with the netbios name, the correct ip adress is returned.
The problem seemed to correspond to a software update that occurred on 2009-11-21 that included updates to selinux-policy and selinux-policy-targeted. SE Linux has the System Default Enforcing Mode set to disabled. The system default policy type is set to targeted with no other options available.nsswitch.conf file appears to have been changed on the same date, but reverting back to the backup version of the file failed to solve the problem. Samba is up and running. My linux shares are accessible from my windows boxes. The firewall is open to smb and smbclient.
We are using spare parts (Socket 775 Biostar motherboard, OCZ 500wat PSU) to build a computer that will just be another system in the house. I want this system to be running Folding@Home, and the F@H SMP client for Linux is much less of a headache than its Windows couterpart, so I would like this computer to run Fedora. My dad loves networking, and knows how to do it in XP / Vista, so he has always opposed my frequent use of Linux. There are ways of accessing Windows shared folders from Linux, but that I haven't figured it out yet. I want to access Windows shared folders from my Fedora 10. I don't know how to go about doing this, can anyone point me in the right direction? Do I have to install anything special? I can go to Places, and then Network (in Gnome) and I see "Windows Network", but when I click it, I get "Unable to mount location Failed to retrieve share list from server"
It's been awhile since I posted anything which is a good sign my install has been working well and I have been able to handle most everything. However, I'm not able to handle this issue. I recently installed F11 and everything went well. But, when trying to see my other computers on the local network, I cannot. I receive this error message: Unable to mount location Failed to receive shared list from server. I understand the message as it is obvious, but do not know how to fix it.
I'm running Ubuntu 9.10. I am hooked into my home network with several windows machines attached. On a daily basis I browse the network and use network shares. Today, I can't. Today I can't see any other machines from ubuntu. I haven't changed any settings in Ubuntu, and nothing has been changed on the network, but yesterday it worked fine and today it doesn't.
Can anyone point me in the direction of setting up shares for windows machines on centos. I have found a few document but never managed to get it up and running correctly. I need to be able to get access to subfolder etc for different users. Is there any way of doing it with some sort of gui?
I have a file that was created in Virtual Machine Manager and I need to get it out of the virtual operating system(windowsXP). Writing to a USB would be ideal but that hasn't been working since I upgraded to Fedora12.Is there anyway I can mount the image to retrieve the file?wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so mounting as fvat doesn't work either.
From Konqueror/Dolphin is possible to access samba shares. If your computer is joined to a Active Directory domain and you use a domain user, you can access samba shares with smb://server.domain/share and you are not ask for user/pass (you use a kerberos tiquet). Kde programs as Amarok, K3b, ... can access files in samba shares without problem. But other programs, specially gnome programs (including the popular OpenOffice), are unable to use files in a samba share. If instead of using Konqueror/dolphin you use Nautilus, there is no problem because it maps the share to a local folder ($HOME/.gvfs/share in sever/) and the program are able to access files in samba shares without problems as the folder is mounted locally (as if you use cifs.mount). Its a problem to use konqueror/dolphin and have to change to nautilus to access samba shares.
If you use Windows you can mount it in an easy way. That's what I try to do from konqueror, not having to open a konsole and be able to mount the share in an easy way. I've tried with smb4k, but is has not worked for me (tried in 2 OpenSuse 11.3 and 1 opensuse 11.2). What Nautilus does when accessing a samba shares like smb://server.domain.dom/share is to execute the command: [URL]... What I try is to do the same, but just form Konqueror/Dolphin. I'd like to add a button to Konqueror/dolphin that pressing the button and if the URL points to a samba share, the share is mounted in $HOME/LocalNetwork/server/share. As I say, it can be as easy as executing the gvfs-mount, but don't know how.
I'm mounting a Windows share using the following in Ubuntu: mount -t cifs username=MYUSER,password=1234 //192.168.1.5/myshare /mnt/windows_share
This works fine, but I would like to mount the share using the computer's hostname, not the IP. I can ping the hostname fine, but I mounting using the hostname instead of the IP does not work. The share cannot be found.
In Windows, I can access the share as \COMPUTER\myshare, and using Nautilus in Ubuntu, I can connect to //COMPUTER/myshare, but I can't use the name in the mount command.
For some strange reason, I can't seem to be able to mount the nfs share from my FreeNAS system on SL6. I'm able to do it just fine from Ubuntu 10.04, Linux mint 9, Fedora 14, CentOS 5.5, and OS X Snow Leopard, so it has to be something specific to SL6. The below command does not work: mount freenas:/mnt/share /test.
I get a mount.nfs error message that says "requested NFS version or transport protocol is not supported." I also tried this command which yielded the same result: mount -t nfs FreeNAS:/mnt/share /test Am I doing something wrong or is this just a bug with SL6?
I'm running sid, and doing weekly updates. Recently I've been unable to mount nfs shares on one of my home computers. I haven't changed any settings, and nfs works fine on the other computers on my small home network. I suspect an update messed something up with nfs.
I have a Linux machine that shares some files through NFS. The shared directory is:
/foo
I then mounted a shared directory (from a Windows machine) to:
/foo/bar
/foo/bar is mounted successfully onto the Linux machine and everything is there. However any other machine that mounts /foo from the Linux machine everything is correctly there except /foo/bar is empty. Is there anyway to do a "recursive mount" of file shares. Here is the /etc/fstab entry for the Windows share mount of /foo/bar //windows_machine/share /foo/bar cifs username=user,password=pass 0 0 And the /etc/fstab entry on the client machines that mount /foo server:/foo /foo nfs rw 0 0
I'm setting up an NFS server on a command line install (9.10) to share a directory for a farmerjoe render farm. My instructions are from code...
I do not have DNS installed. I cannot install a stand alone DNS server on the network which the render farm will run. I cannot point any of the machines in the render farm to the current DNS server. The render farm is on a VLAN (in a design lab) with the NFS server receiving a reserved static IP address and the clients receiving DHCP addresses from a currently running server. After reading this post
http://ubuntuforums.org/showthread.php?t=321926
it seems that I should be able to mount NFS shares using an IP address.
Where are the mount points for smb shares connected via "Places -> Connect to Server"? I assumed them in one of the usual places like
/mnt or /media
but these folders are both empty. There are a couple of applications which are not capable of accessing my shares because i can't navigate to the right location...
It mounts OK on the fly (mount /usr/local) but when you reboot, it hangs, presumably forever, saying that "The disk drive /usr/local is not ready, S to skip, M for manual".Pressing S or M does nothing. I then have to turn the machine off, boot off a CD, mount the HD's / partition and remove the fstab entry before I can successfully boot the OS.Having looked at various forums, I have tried some different things like removing the "0 0", putting "auto" in the options. Unsurprisingly perhaps, these made no difference.
This behaviour was noticed on 10.04, but having tested it on 9.10 it does a similar thing on that version too, although on that one you can actually enter a shell at the hang point and edit your fstab.
Im setting up a Mythbuntu box as a HTPC, and I want to be able to stream my media from my Windows box to the Mythbuntu box. I got the windows shares mounted fine, everything works. But I want them to auto mount so I modded my /etc/fstab file to mount the share. The problem is the Mythbuntu box uses wifi, and during boot the computer can't connect to the Windows box, and it hangs on
Quote:
Error while mounting /blah/blah/ press s to skip or m for manual recovery and I am planning on not having a kbd hooked up to this computer once it is done.
1) Is there a better way to auto mount Windows shares - one that does the mounting after the computer is booted up? Furthermore, the Windows box may be off, so I want it to just skip the mounting on error.
2) Right now when I mount the share, I have to specify the Windows computer by its IP address. If I do it by PC name, it doesn't work, says it can't find the computer. Is there a way to mount using the computer name, so that if my router decides to give the windows box a new IP I wont have to reload everything?
I'm having trouble setting up samba to work with my vista machine. Whenever I try to mount certain shares I'm getting error 13- permission denied. Specifically, I'm trying to mount my entire C: with this command at the console:
The funny thing is that I CAN mount some other shares, but not all. My distro is slack-current. I've been following as many relevant threads on this issue for a while now and have tried as many of the suggestions as I could understand, but it's getting to the point that I've lost track of what I've tried and what I haven't. Things I have tried:
Checking permissions on the shares: seem to be ok enabling encrypted passwords: not sure if I did it right. editing the registry for LmCompatablity
I have never wrote a script before in linux/unix and I am having trouble doing so. I would like to turn this command: mount -t cifs //ntserver/download -o username=vivek,password=myPassword /mnt/ntserver
I recently replaced my windows fileserver with one running Ubuntu. One thing I've noticed (which is a annoying) is that when I copy files between two samba shares from my windows machine, it copies the file through my PC to the new destination. On windows shares it just did some sort of local copy (ie it took about 2 seconds) rather than 3-4 minutes. Is this the normal behaviour, is there any way around it on Linux
I have a Thecus NAS with nfs support running. Now I switched from OpenSUSE 10 to 11.2 on the client side and aren't able to mount my nfs shares. With SuSe 10.0 I didn't have any problems.
The /etc/exports: /raid/home_nas1 192.168.0.24/31(rw,no_root_squash,sync,anonuid=99,anongid=99,no_subtree_check) /raid/soundandmore 192.168.0.24/31(rw,no_root_squash,sync,anonuid=99,anongid=99,no_subtree_check)
On the client side I'm able to see the shares: showmount -e nas1 Export list for nas1: /raid/home_nas1 192.168.0.24/31 /raid/soundandmore 192.168.0.24/31
The client address: inet addr:192.168.0.27
I'm using nfs-3: mount -t nfs nas1:/raid/soundandmore/mnt mount.nfs: access denied by server while mounting nas1:/raid/soundandmore
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:
Code:
#!/bin/bash # The hostname or IP-address of the fileserver: FILESERVER="myfileserver.local" # Check every X seconds (60 is a good default):
[code]...
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:
Code:
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:
Code:
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.
Code:
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:
Code:
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:
Code:
# mount_my_nfs_shares - mount NFS shares on fileserver, if present description"Mount NFS-shares" start on (filesystem) respawn
[code]....
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 am trying to share files on my Windows XP Home machine over my P2P network to my Ubuntu netbook. The folder I wish to share is configured in Windows with public permissions. I go to the Files & Folders > Documents and then I click on Network in the Places tab. A Windows Network icon appears, but when I double click it I receive the error message, "Unable to mount location. Failed to retrieve share list from server."
I've been trying to set up a Linux-only network and currently have a working DHCP, DNS, LDAP and NFS server, with a client that can authenticate with the LDAP server and a central /home folder.However, if I wanted to share folders on the NFS server, how would I make the share available to, for example, a particular group of users in the directory?I've never used NIS(+) on a network, but believe you can add a 'group' of users in the /etc/exports file--simples!Does anyone know of the best way to do it (even better anyone who is doing this in a production environment)?
We 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:
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/
