Linux NFS development
 help / color / mirror / Atom feed
From: BigShamy24@aol.com
To: nfs@lists.sourceforge.net
Subject: NFS Server:7.1/Client: Sol8
Date: Mon, 10 Jun 2002 18:40:09 EDT	[thread overview]
Message-ID: <126.11f11e17.2a3684c9@aol.com> (raw)

Hello,
I am using Redhat 7.1 as my NFS server. I have edited /etc/exports and when I 
ran "rpcinfo -p localhost" I got all the daemons and their ports correctly.

On the client side, I have Solaris 8. Everytime I try to mount I get the 
following error.
nfs mount: x.x.x.x: : RPC: Rpcbind failure - RPC: Unable to receive nfs 
mount: retrying: /dump
And it keeps on trying.I have checked everything that I can think off. From 
portmap to hosts.allow/.deny

I am clueless! Any help plz>Thanks  


_______________________________________________________________

Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink

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

                 reply	other threads:[~2002-06-10 22:40 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=126.11f11e17.2a3684c9@aol.com \
    --to=bigshamy24@aol.com \
    --cc=nfs@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox