From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: "Ozy Ali" <ozzeee@hotmail.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: (no subject)
Date: 22 Mar 2002 15:45:46 +0100 [thread overview]
Message-ID: <shslmckr78l.fsf@charged.uio.no> (raw)
In-Reply-To: <F109h6wT8DDQA6y4wlD00002bbc@hotmail.com>
>>>>> " " == Ozy Ali <ozzeee@hotmail.com> writes:
> hi,
> ive got a system running on redhat 6.2. i am attempting to
> get another 2 pcs connected up top it as a network. i am
> currently trying to install via nfs as i only have 1 cd in
> the main pc. i have trawled through many HOWTO's and tried
> their ideas. (ie. change the file etc\exports) my problem is
> no matter wot i try i always get the same message wen i boot
> up the netboot.img floppy in the 2nd pc. the error reads " i
> could not mount that directory from the server, mount: RPC:
> port mapper failure - RPC:timed out.
> im going out of my minds with this as ive been at it for about
> 2 weeks. any help would be greatly appreciated.
The error message is fairly explicit: the portmapper program
(a.k.a. "/sbin/portmap") on your server appears not to be accessible
to this client.
Is portmap not running on the server, or is there anything in
/etc/hosts.deny or in /etc/sysconfig/ipchains for instance that might
be blocking access to that client?
Cheers,
Trond
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2002-03-22 14:45 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-22 14:06 (no subject) Ozy Ali
2002-03-22 14:45 ` Trond Myklebust [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-03-25 11:03 Ozy Ali
[not found] <15484.3052.362597.167779@notabene.cse.unsw.edu.au>
2002-03-27 13:36 ` shalini jain
2002-04-03 11:03 Ozy Ali
2002-04-25 9:41 Tina Arora
2002-07-24 11:53 Nir Cohen
2002-07-30 11:10 Nir Cohen
2003-01-10 10:29 Adam.Szabo
2003-01-27 14:23 Emanuel.Quass
2003-01-27 15:17 ` Trond Myklebust
2003-03-09 19:58 Steve Salazar
2003-03-10 16:32 Lever, Charles
2003-04-23 18:38 gb
2003-04-23 19:11 ` Spencer Shepler
2003-04-23 19:20 ` Trond Myklebust
2003-06-04 1:59 xiyu
2003-10-14 19:50 Ralph Churchill
2003-10-16 19:42 ` Ralph Churchill
2005-11-14 21:58 Kyle Perkins
2006-01-17 21:37 Jonas Lihnell
2006-01-17 21:41 ` Trond Myklebust
2006-01-17 22:18 ` Jonas Lihnell
2006-07-08 22:27 潘思广
2006-07-26 10:47 Bernd Schubert
2006-07-26 11:43 ` Trond Myklebust
2006-09-11 3:38 qinping
2007-04-24 16:25 Fabio Olive Leite
2007-06-07 17:05 [PATCH] locks: provide a file lease method enabling cluster-coherent leases J. Bruce Fields
2007-06-08 22:14 ` (no subject) J. Bruce Fields
2007-06-20 9:00 sun lu
2007-07-14 14:24 Cummings
2007-07-16 9:48 Riccardo Bini
2007-07-24 14:41 Bella
2007-07-24 14:42 Dennis
2007-07-25 14:36 Eldridge
2007-07-26 9:27 Olive Crosby
2007-08-02 0:08 Mahoney O.Becky
2007-08-02 7:24 Piotr Kandziora
2007-08-02 15:45 ` Jeff Layton
2007-08-06 13:45 Piotr Kandziora
2007-08-08 20:15 采购成本降低技巧及供应商管理
2007-08-10 7:16 grikxd
2007-10-19 3:44 Neil Brown
2007-10-26 21:38 『晴れたらいいね』
2007-10-31 20:59 immanuel lily
2007-11-08 15:36 Willis
2009-06-05 10:41 Mike Brodbelt
2010-07-16 13:40 Tom H
2010-11-10 18:10 Russell Cattelan
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=shslmckr78l.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=nfs@lists.sourceforge.net \
--cc=ozzeee@hotmail.com \
/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;
as well as URLs for NNTP newsgroup(s).