[Solved]NFS Client Not Mounting Shares

Here is my setup:
I have two Arch boxes that I am attempting to setup NFS shares on. The box that is going to be the server is headless FYI. So far, I have installed nfs-utils, started `rpc-idmapd` and `rpc-mountd` successfully on the server, and started `rpc-gssd` successfully on the client.
The folder I am trying to share is the /exports folder.
ls -l /exports
produces
total 8
drwxrwxrw-+ 110 daniel 1004 4096 Dec 6 17:26 Movies
drwxrwxrwx+ 13 daniel users 4096 Jan 8 19:12 TV-Shows
On the server:
/etc/exports
# /etc/exports
# List of directories exported to NFS clients. See exports(5).
# Use exportfs -arv to reread.
# Example for NFSv2 and NFSv3:
# /srv/home hostname1(rw,sync) hostname2(ro,sync)
# Example for NFSv4:
# /srv/nfs4 hostname1(rw,sync,fsid=0)
# /srv/nfs4/home hostname1(rw,sync,nohide)
# Using Kerberos and integrity checking:
# /srv/nfs4 gss/krb5i(rw,sync,fsid=0,crossmnt)
# /srv/nfs4/home gss/krb5i(rw,sync,nohide)
/exports 192.168.1.10(rw,fsid=0)
On the client:
showmount -e 192.168.1.91
Export list for 192.168.1.91:
/exports 192.168.1.10
Everything is looking hunky-dory. However, I go to mount using
sudo mount -t nfs4 192.168.1.91:/exports /mnt/Media
and the mount never takes place. It sits there and does nothing. I CAN, however, kill the process with Ctrl-c.
So does anybody have ANY idea why my shares aren't working.
EDIT: Just thought I should mention that all of the data in the /exports folder is a mount --bind from /mnt/media. All of the /mnt/media is contained on a USB external hard drive. I did notice that there is an ACL.
getfacl /exports
getfacl: Removing leading '/' from absolute path names
# file: exports/
# owner: root
# group: root
user::rwx
group::r-x
other::r-x
Last edited by DaBungalow (2014-01-10 03:18:05)

I found what the problem was. Apparently rpc_gssd was causing a problem. Stopping it fixed everything.

Similar Messages

[solved] NFS client will not work correctly

I have all my $HOME on an NFS Server. So long I used suse and debian, now I want switch to arch but the nfs-client ist not working correctly:
I start "portmap nfslock nfsd netfs" over rc.conf. When I do a "rpcinfo -p <ip-arch-system>" I got the following
stefan:/home/stefan # rpcinfo -p 192.168.123.3
Program Vers Proto Port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100021 1 udp 32768 nlockmgr
100021 3 udp 32768 nlockmgr
100021 4 udp 32768 nlockmgr
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 4 udp 2049 nfs
100021 1 tcp 48988 nlockmgr
100021 3 tcp 48988 nlockmgr
100021 4 tcp 48988 nlockmgr
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100003 4 tcp 2049 nfs
100005 3 udp 891 mountd
100005 3 tcp 894 mountd
As you see "status" is missing, so the statd is not running. It sould look like the result on my suse box:
stefan:/home/stefan # rpcinfo -p 192.168.123.2
Program Vers Proto Port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100024 1 udp 32768 status
100021 1 udp 32768 nlockmgr
100021 3 udp 32768 nlockmgr
100021 4 udp 32768 nlockmgr
100024 1 tcp 35804 status
100021 1 tcp 35804 nlockmgr
100021 3 tcp 35804 nlockmgr
100021 4 tcp 35804 nlockmgr
There is the "status" line and so the statd is running.
How can I fix that problem, so that statd ist running on my arch box too?
Last edited by stka (2007-06-10 15:59:48)

The Problem ist solved.
I use ldap for authentication. During the setup of the ldapclient I copied the nsswitch.ldap to nsswitch.conf. But the line for "hosts:" was:
hosts: dns ldap
but in my dns ist no localhost entry. After I changed this line to:
hosts: files dns ldap
everything was ok. The statd is now running and I can start to migrate to archlinux ;-)

Nfs client ls /data/rw10 nfs client on mount: Permission denied

We are running an 800 cpu amd solaris 10 x64 cluster for HPC and an 512 cpu ultrasparc cluster solaris 10 for high
throughput.
Until now the nfs servers played ball and I did not experience real difficulties.
I am running two Solaris 10 x64 servers serving a total of 80 TB over nfs4, one Thumper serving 17 TByte over nfs4
and 7 linux serving 30 TByte over nfs3.
Today for the first time I got a massive rejection of mounts with the following error on the client.
May 9 18:24:10 m2001 nfs: [ID 664466 kern.notice] NFS compound failed for server c-store2: error 12 (RPC: Remote system error)
May 9 18:24:10 m2001 last message repeated 1 time
May 9 18:24:10 m2001 automountd[428]: [ID 834250 daemon.error] Mount of c-store2:/data2 on /data/rw10: I/O error
The load is not heavy by my standards as there are only 50 concurrent clients trying to mount that file space and the
same clients are mounting the thumper and do not get this problem.
I have had considerably heavier loads on the linux based nfs3 servers when 300 concurrent jobs were accessing one
file space at a time and I did not get this problem.
Have any of you seen this and found a remedy. any hints would be welcome

The problem solved itself mysteriously overnight, without any interference from myself.
The systems are again perfectly happily mounting the file space (650 clients of them all at the same time
mounting up to 6 filesystems from the same server) and the server is happily serving again as it has been for the past 2 years.
My idea is that there has been a network configuration clash, but considering that the last modification of NIS hosts file was about 4 weeks ago and the latest server was installed then and has been serving since then, I have no
idea how such clash could happen without interference in the config files. It is a mystery and I will have to make
every effort to unravel it. One does not really like to sweep incidents like that un-investigated under the carpet.
If anybody has any suggestions and thoughts on this matter please post them here.
Lydia

Lion will not mount shares from Debian Linux 5.0 server

HI after Lion update I cant mount shares from our server, it replys back with this:
"The version of the server you tryed to connect to are not supported"
I can not find info about server versions supported anywhere
Anyone know what can be done to fix this problem with shares?.

I figured out the problem.
This is going to sound a little crazy, but I've spent a lot of time on this one.
There's some kind of incompatibility with Lion and Seagate ST31000340AS drives. I was trying to install Lion on these drives and it would consistently fail. I've also tried to use these drives in a RAID volume. No go. I tried three different drives of this model. All of them failed.
I tried to install Lion on a Seagate ST31000528AS and it worked first time and sings beautifully.

Oddball client not mounting XSan Volumes

Background: My client, a TV News broadcast station, had Apple and a third-party design and install a Apple based XSan storage and network. They ran all new fiber and gigabit ethernet to each station to use the XSan. It has been working great, with the exception noted below.
Setup: 2 MD Controllers, 1 XServe, 4 XRaids, each make up two 2 large TB volumes (raid 5, stripped together).
XServe, XRAID, MD controllers, and all clients are all connected together on a Fibre and Fiber Optic network using QLogic switches. SUBNET: 10.200.1.x.
Ethernet Network, also connected all the above together on HP Gigabit Switches. SUBNET: 10.100.1.x The public WAN is made available on this subnet by a connection to the HP switches. Still getting details on how this was done.
Everything is running OS X 10.4.8 or better, XSan File System 1.4.
Setup
There are 8 workstations (edit bays) that act as infusion and editing stations. Each station has two XSans volumes mounted NEWS01 and NEWS02. They have the odd numbered bays use NEWS01 and the even numbered bays use NEW02.
PROBLEM
All bays mount the XSan volumes, except one. FCP08 will not mount the XSan volumes. We have rebooted the workstation, and even went to the extreme of shutting down the entire setup all bays and MD controllers, File Servers, etc.. then bringing everything backup up. Same problem.
Based on some forum discussion, we have tried the following:
* Ensured that there is no empty mount point in /Volumes
* Uninstalled all XSan Software and resinstalled v1.4 from Apple's website.
* Removed the client from the XSan Admin, and readded it, made sure to enter valid serial number, etc..
* Verified that all fibers are working, all link lights look good, and you can ping across the MD network.
When you use the XSan admin from either FCP08 (edit bay 08) or from the server, and you add both MD XSans to it, you see the client, and you click on the client and click either Mount (read-only) or Mount (Read/write).
It will show "Mounting..." and then it will flip back to "not mounted". The only feedback we have received so far is "ACCESS DENIED". All affinity setting are set to rwxrwxrwx (wide open), and all the volumes and workstation logins all have the same access to the volumes. I can not find any restrictive permissions anywhere.
I plan on trying to move them away from a /etc/hosts type setup to a proper DNS Server running on their XServe using the DNS Server function of OS X Server. But currently all edit bay stations have the same /etc/hosts file installed, which accounts for MD and ethernet networks.
ANY IDEAS what is wrong with this workstation? With the setup?
I have had extreme ideas from some who have said that we need to blitz the entire client, and reinstall the operating system. I am not willing to go down that route, since each edit bay was built manually without an image (another aspect I will remedying soon). It will take sometime to rebuild this edit bay client if I that is the only solution.
The only this question I have if that is the popular opinion, is what is different from a client OS install and the existing one regarding the XSan? This are edit bays, not private workstations, and no one installs any extra software or surfs the net, etc.. They are used for ingest and editing only.
HELP!
Mac OS X (10.4.10)

Hi,
You could check if it is Fibre Channel related:
from a terminal do a cvlabel -l
this should give you a list of the lun's in your volume.
When this tool does not show luns, you might have a zoning issue.
Regards
Donald

Nfs /vol not mounted

nfs umount: /vol: not mounted
WARNING: forceload of misc/md_raid failed
WARNING: forceload of misc/md_hotspares failed

Solution
Remove all entries from mac os disk manager (nfs) (better copy&past the entries into a text file)
sudo automount -vc -> working
Setup absolutely the same in disk manager again -> working
however
Lion-Mac-Pro:~ me$ sudo automount -vc
automount: /net updated
automount: /home updated
automount: /Users/me/Music updated
automount: /Users/me/Pictures updated
automount: /Users/me/Downloads updated
automount: /Users/me/Documents updated
automount: /Volumes/foo updated
automount: no unmounts

[SOLVED] Gnome does not mount ipod after system upgrade

I did a system upgrade today (2009.12.04) and now gnome does not mount my ipod video (gnome used to mount the ipod without problems before de upgrade).
Here is some information about the system messages:
Last lines of the output of dmesg before plugging the ipod:
wlan0: associated
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
wlan0: no IPv6 routers present
After plugging it:
wlan0: associated
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
wlan0: no IPv6 routers present
usb 1-4: new high speed USB device using ehci_hcd and address 3
usb 1-4: configuration #1 chosen from 2 choices
Initializing USB Mass Storage driver...
scsi6 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 3
usb-storage: waiting for device to settle before scanning
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usb 1-4: reset high speed USB device using ehci_hcd and address 3
usb 1-4: reset high speed USB device using ehci_hcd and address 3
usb 1-4: reset high speed USB device using ehci_hcd and address 3
usb 1-4: reset high speed USB device using ehci_hcd and address 3
usb 1-4: reset high speed USB device using ehci_hcd and address 3
scsi 6:0:0:0: Device offlined - not ready after error recovery
usb-storage: device scan complete
The output of the lsusb command:
[miguel@miguel ~]$ lsusb
Bus 002 Device 002: ID 0408:030c Quanta Computer, Inc. HP Webcam
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 08ff:2580 AuthenTec, Inc. AES2501 Fingerprint Sensor
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 05ac:1209 Apple, Inc. iPod Video
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
lsusb shows ipod is in Bus 001
Any help?
Many tks
Last edited by mmf1902 (2009-12-29 04:42:11)

Finally found the problem was the Ipod itself. After a soft reset everything worked again.

[SOLVED] pam_mount will not mount truecrypt volume on login.

Hello.
I did system upgrade yesterday and encountered some problems with mounting my Truecrypt volume with pam_mount. I use pam_mount to mount my encrypted /home partionion at login. After first reboot and loging in I was dropped to / directory, with my /home partition clearly not mounted. I acknowledged the message from udev in pacman, that in some circumstances adding 'loop' to MODULES array in /etc/mkintcpio.conf is required and for a moment I thought it was it, but I tried this and it didn't help. Suprisingly, after another reboot I was placed im my home directory afer login, but it appears to be empty - I can see only dotfiles of few programs I used after the upgrade:
$ls -A ~/
.bash_history .links .qingy .viminfo .wicd
but my /home partition is obviously still not mounted. My relevant config files:
/etc/security/pam_mount.conf.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE pam_mount SYSTEM "pam_mount.conf.xml.dtd">

<pam_mount>

<debug enable="0" />




<mntoptions allow="nosuid,nodev,loop,encryption,fsck,nonempty,allow_root,allow_other" />

<mntoptions require="nosuid,nodev" />

<logout wait="0" hup="0" term="0" kill="0" />

<cryptmount>truecrypt --text --protect-hidden=no --keyfiles="/etc/home.key" %(VOLUME) %(MNTPT)</cryptmount>
<cryptumount>truecrypt -d</cryptumount>
<volume user="schirase" fstype="crypt" path="/dev/sda7" mountpoint="/home" options="fsck,relatime" />
<mkmountpoint enable="1" remove="true" />
</pam_mount>
/etc/pam.d/login
#%PAM-1.0
auth required pam_securetty.so
auth requisite pam_nologin.so
auth required pam_unix.so nullok
auth required pam_tally.so onerr=succeed file=/var/log/faillog
auth optional pam_mount.so
# use this to lockout accounts for 10 minutes after 3 failed attempts
#auth required pam_tally.so deny=2 unlock_time=600 onerr=succeed file=/var/log/faillog
account required pam_access.so
account required pam_time.so
account required pam_unix.sof
#password required pam_cracklib.so difok=2 minlen=8 dcredit=2 ocredit=2 retry=3
password optional pam_mount.so
#password required pam_unix.so sha512 shadow use_authtok
session required pam_unix.so
session optional pam_mount.so
session required pam_env.so
session required pam_motd.so
session required pam_limits.so
session optional pam_mail.so dir=/var/spool/mail standard
session optional pam_lastlog.so
session optional pam_loginuid.so
-session optional pam_ck_connector.so nox11
-session optional pam_systemd.so
/etc/pam.d/qingy
#%PAM-1.0
auth required /lib/security/pam_securetty.so
auth required /lib/security/pam_unix.so
auth required /lib/security/pam_nologin.so
account required /lib/security/pam_unix.so
password required /lib/security/pam_unix.so
session required /lib/security/pam_unix.so
session optional /lib/security/pam_console.so
Any ideas how to make it work again?
[EDIT] OK, I've looked into it a little more and I realised that I should try loging in without qingy. I tried on agetty console and it worked as before. It looks like qingy upgrade changed my /etc/pam.d/qingy file into default one. The one above is and obviously unsuitable for use with pam_mount and I failed to see that at first. It should look similar to the example file for slim in the wiki article on pam_mount:
#%PAM-1.0
auth required /lib/security/pam_securetty.so
auth required /lib/security/pam_unix.so
auth optional /lib/security/pam_mount.so
auth required /lib/security/pam_nologin.so
account required /lib/security/pam_unix.so
password required /lib/security/pam_unix.so
password optional /lib/security/pam_mount.so
session required /lib/security/pam_unix.so
session optional /lib/security/pam_mount.so
session optional /lib/security/pam_console.so
Sorry for the trouble, maybe at least it will help someone.
Last edited by Schirase (2012-03-25 17:49:21)

Having looked again, hal fails to start. I have it in rc.conf DAEMONS. When i try to start Hal manually, it also fails to start ...
Last edited by whitetimer (2010-11-09 16:45:46)

[SOLVED] NFS protocol not supported

I get this error:
mount.nfs4: Protocol not supported
when trying to mount a NFS share from my server like so:
sudo mount -t nfs4 192.168.1.20:/srv/nfs4/ /media/server
I can mount it on my raspberry pi, but not on my arch laptop.
The server configuration is like this:
/srv/nfs4/ 192.168.1.1/24(rw,fsid=root,no_subtree_check)
/srv/nfs4/media 192.168.1.1/24(rw,no_subtree_check,nohide)
showmount -e gives this:
Export list for 192.168.1.20:
/srv/nfs4/media 192.168.1.1/24
/srv/nfs4 192.168.1.1/24
Any ideas?
Last edited by marius (2013-08-17 12:50:46)

I don't think you are supplying all the information that you are given by your machine. The error you mention is often preceeded by a number of other messages which give some idea of what is actually occurring. Please post error messages exactly as they are given to you, and check the journal and/or dmesg for more information.
Also as a side note, you need to use code tags for things like commands and output. Hit the quote button on this post to see how I created the boxes below (the arrows will make sense when this post is quoted):
<--These are code tags-->
<--These are quote tags-->

[SOLVED]usb drive not mounting

I get this error when I try to mount a usb drive in pcmanfm. It used to work correctly before. Since then I tried uninstalling fam and installed gamin. But now I have reverted back to fam and I still see this. What could be the issue? I can mount the drive manually in CLI, but I was just wondering what suddenly happened.
inxs ~ > pcmanfm
(pcmanfm:4961): Gtk-WARNING **: Failed to set text from markup due to error parsing markup: Error on line 1 char 57: '-' is not a valid character following a '<' character; it may not begin an element name
(pcmanfm:4961): Gtk-WARNING **: Failed to set text from markup due to error parsing markup: Error on line 1 char 57: '-' is not a valid character following a '<' character; it may not begin an element name
Last edited by Inxsible (2009-02-13 05:43:07)

spookyln wrote:
this working like a charm.
edit your /etc/PolicyKit/PolicyKit.conf
<?xml version="1.0" encoding="UTF-8"?> 
<!DOCTYPE pkconfig PUBLIC "-//freedesktop//DTD PolicyKit Configuration 1.0//EN"
"http://hal.freedesktop.org/releases/PolicyKit/1.0/config.dtd">

<config version="0.1">
<match action="org.freedesktop.hal.storage.mount-removable">
<return result="yes"/>
</match>
</config>
Bingo!! Man you guys are good.

H: drive on Windows client not mounted

In WGM I defined network accounts for about 10 windows clients.
Our Xserve is used as a PDC and I can connect the clients to the domain and login using the accounts.
However, I tested the login procedure before creating a Home folder for each accounts and now the H: drive doesn't get mounted.
Next I removed the Windows-profiles hoping to start with a clean profile but they don't get recreated.
Can I force OS X server to recreate the profile info?

I've got a better understanding now of how to make folders and profiles by hand and setting the right privileges.

[SOLVED] External HDD not mounting at boot

So, I've got this USB external HDD which won't mount at boot time. I set it in /etc/fstab using its UUID and it works immediately after boot if I do
sudo mount -a
I had it before on a different machine, running Arch too, and never had this problem. How can I see what's going on at boot time? I usualy just start the computer remotely (wake on lan).
Last edited by RaisedFist (2010-10-21 11:22:46)

Couldn't it be caused by the external HDD not being ready yet when the system boot? Nowadays I rarely encounter these issues, but some years ago even certain internally connected drive would need a delay to get ready for boot. If so settings in BIOS has to be adjusted.
Just a quick guess.

[SOLVED] Silc-Client not working?

Hi there!
I wanted to install the silc-client from www.silcnet.org an my arch-machine, but it's not working. Everytime when I start the client it asks for my keyphrase; but when I'm typing it in and press enter nothing happens and I'M taken back to my prompt.
[riddler@morgue ~]$ /usr/local/silc/bin/silc
Private key passphrase:
[riddler@morgue ~]$
When I delete the keyphrases and create new ones it looks so:
[riddler@morgue ~]$ /usr/local/silc/bin/silc
Running SILC for the first time
Private key passphrase:
Retype private key passphrase: Generating RSA Public and Private keys, might take a while...
Finding p: ...............................................................................................................................
Finding q: .................................................................................................................................................................
Keys generated successfully.
Public key has been saved into `/home/riddler/.silc/public_key.pub'.
Private key has been saved into `/home/riddler/.silc/private_key.prv'.
Press <Enter> to continue...
Private key passphrase:
[riddler@morgue ~]$
Someone wrote in this forum, that his irssi behaves in the same way like the silc-client in my case, but irssi is working absolutely correct here.
It would be nice if somebody could help, it's important
Thank you very much.

Haha, so funny...
I compiled this packages (1.0.2) around 30times...5 mins ago i decided to try the 1.0-release and it worked...
i don't know why the 1.02 and 1.01 don't work, but the 1.0 works great...thank you anyways

Systemd nfs client mount share ???

Just installed systemd, systemd-arch-units and initscripts-systemd as per the wiki and all went well except mounting a nfs share from my server. (networking is OK!)
This is the old working mount command run from rc.local before installing systemd;
mount -t nfs4 -o rw,hard,async,intr,rsize=49152,wsize=49152,proto=tcp 192.168.0.250:/ /media/SERVER_NYTT &
Did not mount at all with systemd, not even when run manually from command line. From systemd log netfs and nfs-common failed to start.
So I tried from fstab instead;
192.168.0.250:/ /media/SERVER_NYTT nfs rw,hard,async,intr,rsize=49152,wsize=49152,proto=tcp 0 0
This did work but 'mount' showed that systemd had mounted with nfs default options instead of mine (wsize, rsize ...). Still errors from systemd starting netfs and nfs.
So I disabled netfs and nfs-common/rpcbind from rc.conf and created this systemd file (/etc/systemd/system/192.168.0.250.mount);
[Unit]
Description=ServerNfs
Wants=network.target rpc-statd.service
After=network.target rpc-statd.service
[Mount]
What=192.168.0.250:/
Where=/media/SERVET_NYTT
Type=nfs
Options=rw,hard,async,intr,rsize=49152,wsize=49152,proto=tcp
DirectoryMode=0777
StandardOutput=syslog
StandardError=syslog
From the sparce wiki and 'man systemd.mount'. Now nothing happens. With my limited understanding I thought it would start neccessary services (wants) and replace the entry in fstab.
I will now enable systemd services rpcbind, rpcstatd and see what happens.
Overall the transition to systemd went very well indeed; slim, openbox, network, .xinitrc, e4rat all started OK much to my surprise! There's still some fine-tuning to do like nfs, and possibly automounting and at last weeding out unneccessary services.
But any help with this nfs client problem is much appreciated.

swanson wrote:
Do you use any of this;
Alternatively, you can mark these entries in /etc/fstab with the x-systemd.automount and x-systemd-device-timeout= options (see systemd.mount ..
I did read the man for systemd.mount but couldn't make out what to put in the fstab line.
By the way, I renamed the mountfile to the target mountpoint but no success. I then reactivated the fstab line, with the new mountpoint in /mnt and that worked fine with mount -a. Except the mount options are not as I want, as they are in fstab. They were before systemd, and now they are as default for nfs4.
have a look here regarding the x-systemd-automount option. I seem to be only one who has noticed a problem with this option, comment=systemd.automount works fine for automounting though. I haven't changed the wiki because I'm still not sure if the problem is on my side.

Error mounting NFS share - mount.nfs: Operation not permitted

I've got an NFS share on a FreeBSD server which I mount via fstab.
It mounts automatically at boot and everything is fine.
However, if I unmount it and try to mount it again I get:
mount.nfs: Operation not permitted
I have tried vers=3 and nfsvers=3 in fstab, but to no avail.
rpcbind is allowed in /etc/hosts.allow.
Does anyone have any ideas?
fstab entry:
server:/path/to/files /mnt/files nfs ro,hard,intr,nfsvers=3 0 0

Tagging along, I have the same problem, although I have a different setup:
- Server = Arch linux
- Client1 = Debian Testing linux
- Client2 = Arch linux
On client1, I'm unable to mount all NFS-shares. 2 out of 3 mount ok and the third fails with this error (both through fstab and manually):
# mount -a
mount.nfs4: access denied by server while mounting (null)
On Client2 I'm able to connect automatically and manually to all shares.
Maybe it is Debian-related, but the debian user forums have not been of much help...
THX for any input!
Last edited by zenlord (2010-03-04 12:07:04)

[Solved]NFS Client Not Mounting Shares

Similar Messages

Maybe you are looking for