From: Santiago <santi@mleads.com>
To: Paul Heinlein <heinlein@cse.ogi.edu>, nfs@lists.sourceforge.net
Subject: Re: RedHat/Mandrake NFS - not playing nice
Date: Tue, 18 Feb 2003 07:30:21 -0700 [thread overview]
Message-ID: <3E52437D.6000003@mleads.com> (raw)
In-Reply-To: Pine.LNX.4.44.0302171425550.928-100000@glenfiddich.cse.ogi.edu
In my first post (you might not have seen it) I indicated that I had
checked the hosts.deny/hosts.allow and turned off ipchains and iptables.
It is usually an obvious thing. The obvious thing I forgot to do was to
check the log files. Here is what appears to be the issue:
Feb 17 16:19:15 chance rpc.mountd: refused mount request from 10.0.0.10
(private-10.swlink.net) for
/var/www/html (/var/www/html): no DNS forward lookup
Feb 17 16:22:07 chance rpc.mountd: authenticated mount request from
10.0.0.57:958 for /var/www/html
(/var/www/html)
Feb 17 16:22:16 chance rpc.mountd: refused mount request from 10.0.0.10
(private-10.swlink.net) for
/var/www/html (/var/www/html): no DNS forward lookup
RedHat is trying to look up the host that it is exporting to? I don't
have this issue though when mounting on a debian box. There is nothing
in the /etc/host file. So this is still somewhat mysterious. I am going
to put an entry in /etc/hosts for the mandrake box and see what happens.
Thanks reminding me. It is usually the obvious things.
It worked. Any ideas as to why the nfs server would differentiate
between the mandrake clients and the non-mandrake clients (RH and Debian)?
Thanks,
Santiago
Paul Heinlein wrote:
> On Mon, 17 Feb 2003, Santiago wrote:
>
>
>>However, I still am receiving the same error as before:
>>[root@backup linux]# mount 10.0.0.48:/var/www/html /r/amanda/nitro-html
>>-t nfs
>>mount: 10.0.0.48:/var/www/html failed, reason given by server:
>>Permission denied
>
>
> I hate to ask the obvious questions, but
>
> * Is there anything in /etc/host.deny that would keep your client from
> getting to the server?
>
> * Is there any sort of ipchains/iptables packet filtering that would
> keep your client from getting to the server?
>
> * Do the logs on the server offer any clues as to why it doesn't like
> your client's mount requests?
>
> --Paul Heinlein <heinlein@cse.ogi.edu>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> NFS maillist - NFS@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nfs
>
>
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2003-02-18 14:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-17 16:41 RedHat/Mandrake NFS - not playing nice Santiago
2003-02-17 19:16 ` Trond Myklebust
2003-02-17 22:04 ` Santiago
2003-02-17 22:28 ` Paul Heinlein
2003-02-18 14:30 ` Santiago [this message]
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=3E52437D.6000003@mleads.com \
--to=santi@mleads.com \
--cc=heinlein@cse.ogi.edu \
--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.