The problem with NFS now seems solved. It was a problem concernig the
hosts.allow entries. Putting there the name of the clients everything worked
fine.

Thanks for you precious suggestions.

> -----Messaggio originale-----
> Da: Robert Canary [mailto:[EMAIL PROTECTED]]
> Inviato: venerd́ 12 novembre 1999 9.10
> A: [EMAIL PROTECTED]
> Oggetto: Re: [RedHat-List] Problems with NFS (part II)
> 
> 
> Not always,
> 
> /etc/host.deny and /etc/host.allow will cause some headache 
> if it isn't set
> correctly.  I found this out when trying to do NFS install of 
> RHL5.2.   All
> though I had entire lan listed in the host.allow ( 
> .ohiocounty.net) I had to
> remove the ALL:ALL from the host.deny.  Then it worked.  
> After I made the
> connection (via NFS) I changed it back and it worked okay. Go 
> figure ___
> 
> Hope that helps
> 
> Cameron Simpson wrote:
> 
> > On Thu, Nov 11, 1999 at 06:43:23PM +0100, Nicola Lamarca wrote:
> > |       after some brainstorming I made rpc.nfsd working 
> either on the
> > | client or on the server. Unfortunately I'm facing a 
> problem with the
> > | portmapper. When the client tries to mount a volume 
> existing on the server,
> > | this one answers with:
> > |
> > | mount: RPC: Program not registered.
> > |
> > | How can I register the program (nfsd ?) ?
> >
> > Normally that error means that the mountd program is not 
> running on the
> > server. NFS uses RPC, and RPC doesn't use fixed port 
> numbers. Instead,
> > a daemon called portmap maintains a list of services and what ports
> > they're using. When a service (like mountd, which processes 
> NFS mount
> > requests) starts up it contacts the portmap daemon to 
> register with it
> > the ports it's using. The clients also consult portmap to 
> find out how
> > to talk to an arbitrary service. If the service isn't 
> registered, that
> > normally means the daemon (mountd) never started.
> > --
> > Cameron Simpson, DoD#743        [EMAIL PROTECTED]    
http://www.zip.com.au/~cs/


-- 
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.


-- 
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.

Reply via email to