Ken Thompson wrote:
>
> Hello all.
> I've been lurking for several months soaking up info as fast as I
> can but still have a problem with networking my linux boxes
> together. It seems that no matter which distro I use (RH 6.2 -
> LM 7.0 - LM 7.1b) I set it up as well as I can following the
> instructions in NET4 HOWTO and always get one of two messages.
> RPC: Unable to receive; errno = Connection refused
> netfs: Mounting NFS filesystems failed
> or
> RPC not registered.
> I am leaning towards a security problem but don't know just what
> to do or where to look.
> Can anyone shed some light on this?
>
> My exports file look like this:
> [root@boss /root]# cat /etc/exports
> /common 192,168,1.2(rw,no_root_squash,insecure)
>
I hope the commas are transcription typos!
Well, a slightly better way to do this is as follows:
In linuxconf go to networking->Control->Misc->information about
other hosts
and put a hostname with that 192.168.1.2 so /etc/hosts looks like
127.0.0.1 loopback.localhost lo
192.168.1.x boss.workgroup.org boss #Your server offering the
share
192.168.1.2 datahungry.workgroup.org data #your user of the share
# make sure the user has an /etc/hosts, too with 192.168.1.x
there
Now back up and you will find Networking-->server tasks->Exported
File Systems->
Path to export /common
Client Name datahungry.workgroup.org
tick May Write (rw)
tick Root Privileges (no_root_squash)
un-tick Request access through a secure port
Note you can add as amny users as you like--just drop out of the
share definition and go back to edit it after you fill available
slots, and more slots will be created. (If the line in
/etc/exports gets really long, you might want to use a netgroup
and give the group access)
Quit a few times and tell it to activate changes
then raise a Konsole and
/etc/rc.d/init.d/nfs restart
Now on datahungry, go to linuxconf and do
Networking->Misc->Information about Other Hosts and make sure it
knows about boss andf boss's IP
Then back out to the main menu of linuxconf and goto
Filesystems->access nfs volume->Add
BASE TAB
Server boss.workgroup.org
Volume /common
MountPoint /home/Ms_challenged_user/Desktop/Remote_Commons
OPTIONS TAB
Tick what you need I recommend User mountable and leave all else
as is
NFS OPTIONS TAB
AHA! Something to learn from by playing with AFTER you get NFS
running.
Misc
Definitely keep a comment here so you remember any tuning you
might be testing.
Quit a few times and activate changes, then login as that user
as user raise a Konsole and
mount -t nfs boss.workgroup.org:/common ~/Desktop/Remote_Commons
close the Konsole, click on your Desktop folder, and enjoy
I hope that is enough of a primer. I use it in a
mission-critical environment where every user has access to a
common share (/remotepublic) and a user-specific share (/backup)
on his desktop. The users are amazed that all their work
magically appears in /backup (where would we be without cron &
anacron?) and are happily trading files using /remotepublic or
loading killer programs onto their machines from it. I try to
train them to send messages and files through email rather than
common, because then they need only one skill to transmit data or
receive it from close by or halfway across the planet. Of
course, DLing from common using Konqueror is the same as DLig
from a remote FTP site or will be when Konqueror learns to use
passive FTP a bit better.
Best of luck
Civileme
> PS
> Most of the documentation written in an understandable manner is
> for setting up a Winderz - Linux network are there any docs on
> NFS simplified to the point that a non network administrator can
> read and understand them? Do I even need NFS, is ther another
> way to set up a linux to linux network that's as good or better?
> TIA
> Ken Thompson
> Electrocom Computer Services
> Payette, Idaho
> http://www.nwaa.com
> [EMAIL PROTECTED]
> ICQ (LICQ)#988809
