Linux NFS development
 help / color / mirror / Atom feed
From: steven sagerian <steven_sagerian@attbi.com>
To: nfs <nfs@lists.sourceforge.net>
Subject: rpc time outs
Date: Thu, 31 Oct 2002 00:12:40 -0600	[thread overview]
Message-ID: <3DC0C9D8.9060302@attbi.com> (raw)

Hello,
Im trying to set up a simple nfs server for my home network, Ive got a 
old p2 system running Linux version 2.4.18-3. from my machine (waseca) I 
can get rpcinfo from both my machine and the server (oddly enough called 
"server" ;->).
but when I try to mount fs on server I get the following rpc time outs..
[root@waseca steven]# mount -t nfs server:/home/share /mnt/share
mount: RPC: Timed out

my exports file on server is simply one line..
/home/share waseca(rw,no_root_squash)

I can ping either machine from either host.

the /var/log/messages file on server says rpc.mountd authneticated mount 
request from waseca for /home/share

Every thing looks good..oh...one more bit..when I try to run rpcinfo 
from server (rpcinfo -p waseca) I get a "can contact mapper remote 
system error, connection refused".

Ok can anyone suggest a solution?

Thanks in advance...

Steve
-- 
                 Steven Sagerian
       Unemployed Telcom embedded Developer
"Will code for food (and health insurance :->)"



-------------------------------------------------------
This sf.net email is sponsored by: Influence the future 
of Java(TM) technology. Join the Java Community 
Process(SM) (JCP(SM)) program now. 
http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

                 reply	other threads:[~2002-10-31  6:09 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=3DC0C9D8.9060302@attbi.com \
    --to=steven_sagerian@attbi.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