All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fredrik Gustafsson <iveqy.mailbox@gmail.com>
To: nfs@lists.sourceforge.net
Subject: Access denied
Date: Tue, 21 Jun 2005 15:22:03 +0200	[thread overview]
Message-ID: <4c45183705062106223f32c263@mail.gmail.com> (raw)

Hi, I'm having a problem with my nfs sever/client.

This command:
root@Arwen:~ # mount 192.168.0.107:/home /mnt/misc/

Gives this error:
'mount: 192.168.0.107:/home failed, reason given by server: Access Denied



My client is: Linux Arwen 2.6.8.1-3-386 #1 Thu Nov 18 11:47:33 UTC
2004 i686 GNU/Linux

With package: Debian/Ubuntu 1.0.6-3 common and kernel server

My server is: Linux TheServer 2.6.10-5-386 #1 Tue Apr 5 12:12:40 UTC
2005 i686 GNU/Linux

With package: Debian/Ubuntu 1.0.6-3 common and kernel server
Export file:=20
# /etc/exports: the access control list for filesystems which may be export=
ed
#               to NFS clients.  See exports(5).
/home 192.168.0.105(rw)

hosts.allow:
# /etc/hosts.allow: list of hosts that are allowed to access the system.
#                   See the manual pages hosts_access(5), hosts_options(5)
#                   and /usr/doc/netbase/portmapper.txt.gz
#
# Example:    ALL: LOCAL @some_netgroup
#             ALL: .foobar.edu EXCEPT terminalserver.foobar.edu
#
# If you're going to protect the portmapper use the name "portmap" for the
# daemon name. Remember that you can only use the keyword "ALL" and IP
# addresses (NOT host or domain names) for the portmapper, as well as for
# rpc.mountd (the NFS mount daemon). See portmap(8), rpc.mountd(8) and
# /usr/share/doc/portmap/portmapper.txt.gz for further information.
#
portmap: 192.168.0.105
lockd:   192.168.0.105
rquotad: 192.168.0.105
mountd:  192.168.0.105
statd:   192.168.0.105

hosts.deny:
# /etc/hosts.deny: list of hosts that are _not_ allowed to access the syste=
m.
#                  See the manual pages hosts_access(5), hosts_options(5)
#                  and /usr/doc/netbase/portmapper.txt.gz
#

# Example:    ALL: some.host.name, .some.domain
#             ALL EXCEPT in.fingerd: other.host.name, .other.domain
#
# If you're going to protect the portmapper use the name "portmap" for the
# daemon name. Remember that you can only use the keyword "ALL" and IP
# addresses (NOT host or domain names) for the portmapper. See portmap(8)
# and /usr/doc/portmap/portmapper.txt.gz for further information.
#
# The PARANOID wildcard matches any host whose name does not match its
# address.

# You may wish to enable this to ensure any programs that don't
# validate looked up hostnames still leave understandable logs. In past
# versions of Debian this has been the default.
# ALL: PARANOID
portmap:ALL
lockd:ALL
mountd:ALL
rquotad:ALL
statd:ALL

>From the server:
root@TheServer:/etc # rpcinfo -p
   program vers proto   port
    100000    2   tcp    111  portmapper
    100000    2   udp    111  portmapper
    100003    2   udp   2049  nfs
    100003    3   udp   2049  nfs
    100003    4   udp   2049  nfs
    100003    2   tcp   2049  nfs
    100003    3   tcp   2049  nfs
    100003    4   tcp   2049  nfs
    100021    1   udp  32768  nlockmgr
    100021    3   udp  32768  nlockmgr
    100021    4   udp  32768  nlockmgr
    100021    1   tcp  32768  nlockmgr
    100021    3   tcp  32768  nlockmgr
    100021    4   tcp  32768  nlockmgr
    100005    1   udp    678  mountd
    100005    1   tcp    681  mountd
    100005    2   udp    678  mountd
    100005    2   tcp    681  mountd
    100005    3   udp    678  mountd
    100005    3   tcp    681  mountd
    100024    1   udp    752  status
    100024    1   tcp    755  status
root@TheServer:/etc #


>From the client:
root@Arwen:~ # rpcinfo -p
   program vers proto   port
    100000    2   tcp    111  portmapper
    100000    2   udp    111  portmapper
    391002    2   tcp   1004  sgi_fam
    100024    1   udp    811  status
    100024    1   tcp    814  status
root@Arwen:~ #


hoproot@Arwen:~ # rpcinfo -p
   program vers proto   port
    100000    2   tcp    111  portmapper
    100000    2   udp    111  portmapper
    391002    2   tcp   1004  sgi_fam
    100024    1   udp    811  status
    100024    1   tcp    814  status
root@Arwen:~ #


Hope someone, please, can help me...

Regards
iveqy


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

             reply	other threads:[~2005-06-21 18:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-21 13:22 Fredrik Gustafsson [this message]
2005-06-21 18:16 ` Access denied Fredrik Gustafsson

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=4c45183705062106223f32c263@mail.gmail.com \
    --to=iveqy.mailbox@gmail.com \
    --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.