From: pascal <pascal@deception.nl>
To: nfs@lists.sourceforge.net
Subject: Unable to mount nfs share
Date: Sat, 10 Dec 2005 04:24:40 +0100 [thread overview]
Message-ID: <439A4A78.6070807@deception.nl> (raw)
I'm unable to mount a nfs share. I've followed the howto from
nfs.sourceforge.
Error:
mount: permission denied.
Is there anything else I have to think of in Debian? Or am I just plain
stupid?
Can't get it to work.
On the client:
rpcinfo -p 192.168.0.21 gives me:
programma versie protocol poort
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100021 1 udp 32768 nlockmgr
100021 3 udp 32768 nlockmgr
100005 1 udp 1014 mountd
100005 1 tcp 1017 mountd
391002 2 tcp 625 sgi_fam
100024 1 udp 633 status
100024 1 tcp 636 status
On the server:
cat /proc/fs/nfs/exp*
# Version 1.1
# Path Client(Flags) # IPs
/data *(rw,no_root_squash,sync,wdelay)
syslog:
Dec 10 02:29:58 mainframe mountd[5502]: authenticated mount request from
router.deception.lan:819 for /data (/data)
I'm trying to mount as root, since I haven't added the share to fstab yet.
Thx.
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
reply other threads:[~2005-12-10 3:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=439A4A78.6070807@deception.nl \
--to=pascal@deception.nl \
--cc=nfs@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.