Okay, well, I've boiled it down to being a /etc/hosts.allow / hosts.deny issue.
I removed ALL:ALL from /etc/hosts.deny, and the NFS mount works.
I put it back, even though I've allowed the remote box in question
access to: nfsd, portmap, lockd, rquotad, mountd and statd
(as per the NFS HOWTO,
Google google google:
http://web.gnu.walfield.org/mail-archive/linux-config/2000-June/0061.html
So I tried adding:
rpc.mountd: IP_ADDR_OF_HOST_IN_QUESTION
...to /etc/hosts.allow, and it works now!
Whee!
-bill!
--
[EMAIL PROTECTED] Got kids? Get Tux
On Mon, Jul 14, 2003 at 04:36:13PM -0700, Peter Jay Salzman wrote:
On Mon 14 Jul 03, 4:05 PM, Ted Deppner [EMAIL PROTECTED] said:
portmap: 192.168.0.0/255.255.255.0
mountd: 192.168.0.0/255.255.255.0
[EMAIL PROTECTED] ldd /usr/sbin/rpc.nfsd
[no libwrap]
[EMAIL PROTECTED] ldd
On Mon, 14 Jul 2003, Peter Jay Salzman wrote:
On Mon 14 Jul 03, 4:34 PM, Bill Kendrick [EMAIL PROTECTED] said:
On Mon, Jul 14, 2003 at 03:06:46PM -0700, Ken Herron wrote:
Err, isn't hosts.allow the TCP wrappers config file? NFS usually runs
over udp in a lan environment; I don't
I'm not sure if I broke something, but suddenly the NFS mount I set up recently stopped
working.
Here's a paraphrase of what the mount line looks like in the mountING system's
/etc/fstab:
remote_host:/path/to/dir /home/username/mountpoint nfs
--On Monday, July 14, 2003 03:53:20 AM -0700 Bill Kendrick
[EMAIL PROTECTED] wrote:
The LAN IP of the mountING system is listed in the mountED system's
/etc/hosts.allow, with access to:
portmap
lockd
rquotad
mountd
statd
Shouldn't nfsd be in there?
If necessary, use rpcinfo to make
On Mon, Jul 14, 2003 at 06:25:39AM -0700, Ken Herron wrote:
--On Monday, July 14, 2003 03:53:20 AM -0700 Bill Kendrick
[EMAIL PROTECTED] wrote:
The LAN IP of the mountING system is listed in the mountED system's
/etc/hosts.allow, with access to:
portmap
lockd
rquotad
mountd
--On Monday, July 14, 2003 13:35:20 -0700 Bill Kendrick [EMAIL PROTECTED]
wrote:
Shouldn't nfsd be in there?
*shrug* Sure?! Why not? ;) Like I said, it worked previously, and I
know I didn't mess with hosts.allow between the time it /was/ working
and now, but I'll try it anyway...
Err, isn't
On Mon 14 Jul 03, 3:06 PM, Ken Herron [EMAIL PROTECTED] said:
--On Monday, July 14, 2003 13:35:20 -0700 Bill Kendrick [EMAIL PROTECTED]
wrote:
Shouldn't nfsd be in there?
*shrug* Sure?! Why not? ;) Like I said, it worked previously, and I
know I didn't mess with hosts.allow between
On Mon, Jul 14, 2003 at 03:06:46PM -0700, Ken Herron wrote:
Err, isn't hosts.allow the TCP wrappers config file? NFS usually runs
over udp in a lan environment; I don't see how TCP wrappers could be
involved.
True, but many programs compile against the tcpwrappers library and honor
it, as
On Mon, Jul 14, 2003 at 03:06:46PM -0700, Ken Herron wrote:
Err, isn't hosts.allow the TCP wrappers config file? NFS usually runs
over udp in a lan environment; I don't see how TCP wrappers could be
involved.
I was just following the HOWTO :^)
snip
It'd be helpful to to know exactly
On Mon 14 Jul 03, 4:05 PM, Ted Deppner [EMAIL PROTECTED] said:
On Mon, Jul 14, 2003 at 03:06:46PM -0700, Ken Herron wrote:
Err, isn't hosts.allow the TCP wrappers config file? NFS usually runs
over udp in a lan environment; I don't see how TCP wrappers could be
involved.
True, but
On Mon 14 Jul 03, 4:34 PM, Bill Kendrick [EMAIL PROTECTED] said:
On Mon, Jul 14, 2003 at 03:06:46PM -0700, Ken Herron wrote:
Err, isn't hosts.allow the TCP wrappers config file? NFS usually runs
over udp in a lan environment; I don't see how TCP wrappers could be
involved.
I was
13 matches
Mail list logo
