Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!ucbvax!NEUMANN.SQUIBB.COM!shaginaw
From: shaginaw@NEUMANN.SQUIBB.COM
Newsgroups: comp.sys.sgi
Subject: NFS access list problems
Message-ID: <9102281424.AA23149@neumann>
Date: 28 Feb 91 14:24:51 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 33


In response to Steve Reszutek's problem with NFS access:

     Although the machines are in one another's host tables, if you're
running the name server, you have to be careful to use the correct
form of the other machines' names.  Specifically, when authenticating
potential clients for access, NFS receives the IP address of the potential
client who is doing the mount; the server part of NFS has to be able to do a
reverse hostname lookup to obtain the name of the potential client and
then compare in against the access list in /etc/exports.  If named is running,
the host table is ignored.

     If you are running name service, try this.  Run nslookup interactively,
and type "set query PTR".  Then supply the IP address of one of the
potential clients.  The hostname that comes back must be the one you use
in the access list.  

     If all of this checks out and you still have the problem, let me
know.  We've been through a number of problems in this category.

     Hope this helps.

                                                            -- Rich

-------------------------------------------------------------------------------
   .-----.
  / \-_-/ \      Bristol-Myers Squibb Pharmaceutical Research Institute   
 /_-_\ /_-_\     ------------------------------------------------------
 ----- -----       Richard J. Shaginaw   Internet Address: shaginaw@squibb.com
 \-_-/ \-_-/    Principal Systems Engineer      Telephone: 609-921-5184
  \ /_-_\ / Macromolecular Modeling Department        FAX: 609-683-6607
   `-----'
===============================================================================