NFS question

[kobear at sharedbrain.net]

By asking you to resolve the name, what I meant was to run a command like
"nslookup master" and seeing if it returns a IP address.  But your new error
tells us more.  No route to host basically means just that:  it cannot find a
route to the host.  So, a couple things to look for:

1)  What is the IP address of the machine that you are running this command on? 
Is it on the same local subnet as the target machine (eg: 192.168.0.x).
2)  If it is not on the same subnet, do you have a router setup as your default
gateway?
3)  Do a simple test:  ping 192.168.0.104.  Can it ping the server?
4)  Check your routes on the requesting server via the "route" command.  You
either need to have a route explicitly for 192.168.0.0, or a default route
using the default gateway.
5)  Lastly, make sure you do not have IPTABLES getting in your way.  If I
remember correctly, FC3, which it sounds like your distro is based off of, has
a default firewall/iptables policy that lets you do almost nothing networkwise.
 Check it via the command "iptables -L".  If it is more than one or two rules
per chain, then clear it via "iptables -F" followed by "iptables -X".  This
removes all firewalling rules from your machine.  Of course, this means that
you should not leave it in this state - this is just a troubleshooting step. 
You should figure out which rule is the problem and remove only that.  This
does not sound like a IPTABLES problem so it should not come to that, but I
have seen it do some weird things.

Oh, and HTH = Hope this helps.  ;)

Kyle


Quoting Stephen Burke <qfwfq at adelphia.net>:

> Not sure what you mean by resolve the name of the server using IP gives:
>
> # mount 192.168.0.104:/media/usbdrive /home/qfwfq/usbdrive/
> mount: RPC: Remote system error - No route to host
>
> Not sure what HTH means either
>
> ;-),
> S.
>
> kobear at sharedbrain.net wrote:
> > It looks like it just cannot resolve the address for the server who's fs
> you are
> > trying to mount.  See if you can resolve the name of the server, or try
> > mounting by using the IP address:
> >
> > mount 10.0.0.1:/home  /mnt/home
> >
> > HTH,
> > Kyle
> >
> > Quoting Stephen Burke <qfwfq at adelphia.net>:
> >
> >
> >>While I have not yet been able to completely abandon M$ around here, at
> >>least whatever hard drive has windows on it is also now dual-booted with
> >>some flavor of GNU/Linux against the inevitable time when the M$ side
> >>simply crashes and burns for no apparent reason (which seems to be
> >>happening regularly).
> >>
> >>One of the final hurdles has been to find a flavor  of linux that would
> >>play nicely with my usb2 external hard drive.
> >>
> >>I have found that flavor here: http://www.blagblagblag.org/
> >>I have mentioned BLAG here before, but that was fc1, and this is 3.
> >>
> >>It's sort of a FC3 without the hassle for those of us hammering on
> >>ancient hardware and unwilling to replace it while it still works.
> >>BLAG3000 works beautifully on it.
> >>
> >>The main job of that PII is just to share what's on the usb drive, which
> >>it does a pretty good job of. I have been sharing the drive with samba,
> >>but I would rather not, if I can help it.
> >>
> >>The Linux NFS-HOWTO (which is about all I've been able to find on the
> >>subject -copies availble far and wide) uses the command
> >>
> >># mount master.foo.com:/home /mnt/home
> >>
> >>but I don't know the command for mounting in a workgroup setting without
> >>the .com. Trying just mount master:/media/usbdrive /home/qfwfq/usbdrive
> >>gives me:
> >>
> >>mount: can't get address for master
> >>
> >>I was using "mount -t smbfs //master/usbdrive /home/qfwfq/usbdrive"
> >>before without difficulty (except with fedora, where they apparently
> >>were determined to break the samba that had been working perfectly in
> >>RH9 -another reason to need NFS), so I am not sure what that address
> >>error means.
> >>
> >>Any tips would be greatly appreciated.
> >>
> >>Thanks,
> >>
> >>S.
> >>
> >>
> >
> >
> >
> >
> >
> > ----------------------------------------------------------------
> > This message was sent using IMP, the Internet Messaging Program.
> >
> >
>
>




----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.