Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!gem.mps.ohio-state.edu!brutus.cs.uiuc.edu!apple!sun-barr!newstop!texsun!pollux!ti-csl!ticipa!clif
From: clif@ticipa.ti.com (Clif Harden)
Newsgroups: comp.sys.apollo
Subject: Re: Apollo NFS V2.0
Message-ID: <239@ticipa.ti.com>
Date: 20 Oct 89 19:10:09 GMT
References: <758@idacom.UUCP>
Organization: TI PAC Wafer Fab Systems, Dallas
Lines: 28

From article <758@idacom.UUCP>, by danny@idacom.UUCP (Danny Wilson):
> 
> To realize this, we run the NFS servers on a node one the ring _different_
> from the gateway node to the Ethernet (which connects to some Suns and a
> Vax)

I am assuming that you mean the your gateway node is not running as a
NFS server.  Running the gateway node as a NFS server won't cause you 
any problems.  In fact it may be part of your problem.  We had a problem
quite similar to this.  We mounted files from our microvax to our 
gateway node which had NFS running.  Some of our nodes didn't have 
NFS running, these nodes could see the NFS mounted files but could not
access them properly, they timed out trying to access them.

Just because you have NFS running on some of your nodes doesn't
mean all your nodes can use the NFS mounted files.  Those nodes that
don't have NFS installed probably won't work correctly.

I suppect that if your gateway node isn't running NFS it may be
having trouble handling the NFS requests.  

I run NFS on all the nodes in my network and I don't have any NFS problems.  

 
Clif Harden                    TI PAC Apollo Network Adminstrator
Texas Instruments                                          
PO Box 655012  M/S 3635        
Dallas, TX 75265