From: Robert Myers <rmyers1400@comcast.net>
To: will supat <willsupat@hotmail.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: nfs connection refuse
Date: Sun, 24 Aug 2003 11:23:45 -0400 [thread overview]
Message-ID: <3F48D881.1090804@comcast.net> (raw)
In-Reply-To: <Law11-OE20biNh0Ow0w0002c234@hotmail.com>
will supat wrote:
> I set up nfs on redhat linux 9. I created dir and mount locally, It’s
> work. But when I try to mount remotely from another redhat linux 9, I
> got error message RPC: connection refuse. I can ping both ways. I also
> replace host name with the IP address to eliminate DNS problem. But I
> still get the same error message.
>
> Please suggest what else I need to do to resolve this error message.
>
You probably need to punch some holes in your firewalls. In fact you
will pretty much need to allow the two machines to exchange information
on any port they want, since the RedHat portmapper can put NFS
communication on nearly any port. You will probably want to read about
securing NFS in the RedHat Linux Security Guide.
RM
-------------------------------------------------------
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines
at the same time. Free trial click here:http://www.vmware.com/wl/offer/358/0
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-08-24 15:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-23 17:18 nfs connection refuse will supat
2003-08-24 15:23 ` Robert Myers [this message]
2003-08-25 11:07 ` Steve Dickson
-- strict thread matches above, loose matches on Subject: below --
2003-08-25 11:43 Dennis, Richard
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=3F48D881.1090804@comcast.net \
--to=rmyers1400@comcast.net \
--cc=nfs@lists.sourceforge.net \
--cc=rmyers@rustuck.com \
--cc=willsupat@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.