[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-nfs
Subject:    RE: [NFS] NFS won't work over crossover cable
From:       "Jeff W. Hampson" <jwhamps () ilstu ! edu>
Date:       2001-10-30 23:23:27
[Download RAW message or body]

Well I believe I set up the authoritative zones correctly

client = 192.168.0.196
server = 192.168.0.1

 however I still get:  mount: RPC: Timed out from the nfs client.

and on the NFS server, in /var/log/messages, it states that "rpc.mountd:
authenticated mount request from 192.168.0.196 for /home(/home)"

however as mentioned it doesn't mount.

what am I missing?

thanks for the help

Jeff



-----Original Message-----
From: Ion Badulescu [mailto:ionut@cs.columbia.edu]
Sent: Monday, October 29, 2001 3:21 PM
To: Jeff W. Hampson
Cc: nfs@lists.sourceforge.net
Subject: Re: [NFS] NFS won't work over crossover cable


On Mon, 29 Oct 2001 14:36:01 -0600, Jeff W. Hampson <jwhamps@ilstu.edu>
wrote:

> I am using 192.0.0.195/255.255.255.0 for the redhat7.2 Box and
> 192.0.0.196/255.255.255.0 for the redhat7.1box. These IP's are being used
> between the boxes as they are connected via crossover cable.

Make sure these addresses either resolve in your local DNS, or at least
that you have stub zones for all the private ranges.

[This is a common mistake, I can't believe none of the DNS faq's covers
it. The root servers point 10.in-addr.arpa, 168.192.in-addr.arpa and
friends to blackhole.iana.org, which is, well, a packet blackhole, and
takes forever to time out. So you MUST provide authoritative zones for all
the private ranges you are using, otherwise DNS timeouts will soon become
very annoying.]

Ion

--
  It is better to keep your mouth shut and be thought a fool,
            than to open it and remove all doubt.


_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

[prev in list] [next in list] [prev in thread] [next in thread]