NFS question

[deadpoint]

how is the nfs share exported on the nfs server, 'cat /etc/exports'? 
are you able to nfs mount that share on the nfs server? on the nfs 
server do 'mount localhost:/media/usbdrive /mnt'. if this fails then the 
nfs daemons are probably not running, nfsd and mountd.

Cyber Source wrote:
> first start with a simple ping to the ip of the box/share your trying to 
> mount, then proceed from there with other options.
> 
> Stephen Burke wrote:
> 
>> Thanks all for the advice.
>> I tried the /etc/hosts trick with no luck:
>>
>> (try "mount ip_of_server:/home /mnt/home replace "ip_of_server" with 
>> its IP
>> address (i.e .192.168.0.10)
>> You can use a name if you add a host alias of hte server in /etc/hosts
>> i.e. in /etc/hosts add:
>> 192.168.0.10 nfs-server"
>> Then you could use "mount nfs-server:/home /mnt/home"
>>
>> Dave J. Andruczyk)
>>
>> and it still gives me mount: RPC: Remote system error - No route to host
>>
>> should I get rid of that line in /etc/hosts now? does it matter?
>> all adresses are dhcp from the router.
>>
>> so on to next:
>>
>>
>> kobear at sharedbrain.net wrote:
>>
>>> 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).
>>
>>
>> same subnet (192.168.0.102 here, 192.168.0.104 there)
>>
>>> 3) Do a simple test: ping 192.168.0.104. Can it ping the server? 
>>
>>
>>
>> no problem.
>>
>> # ping 192.168.0.104
>> PING 192.168.0.104 (192.168.0.104) 56(84) bytes of data.
>> 64 bytes from 192.168.0.104: icmp_seq=1 ttl=64 time=1.02 ms
>> 64 bytes from 192.168.0.104: icmp_seq=2 ttl=64 time=0.523 ms
>> 64 bytes from 192.168.0.104: icmp_seq=3 ttl=64 time=0.523 ms
>> 64 bytes from 192.168.0.104: icmp_seq=4 ttl=64 time=0.447 ms
>> 64 bytes from 192.168.0.104: icmp_seq=5 ttl=64 time=0.415 ms
>>
>> --- 192.168.0.104 ping statistics ---
>> 5 packets transmitted, 5 received, 0% packet loss, time 4006ms
>> rtt min/avg/max/mdev = 0.415/0.585/1.020/0.222 ms
>>
>>> 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.
>>
>>
>> not sure about "route"
>>
>> # route add -net 192.168.0.104 netmask 255.255.255.0 dev eth0
>> route: netmask doesn't match route address
>>
>> I tried, 255.0.0.0, 255.255.0.0, 255.255.255.0
>> nada.
>> No fancy routing here: one 7-port D-Link router
>>
>> I just tried adding the route to the router's "routing" config page , 
>> also.
>> nada.
>>
>>
>>
>>> 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.
>>
>>
>>
>> Actually, the system I use most (like, the one with this mailbox)is 
>> suse 8.2. It is, however, on a removable hard drive so that I can 
>> taste ALL the different flavors from here. I am still trying to make 
>> the BLAG system more useful, but there's a whole thunderbird tweaking 
>> adventure there that I have been putting off. I am hoping that I can 
>> find a solution to the NFS thing that is not distro dependant, since 
>> they sort of come and go around here.
>>
>>> Check it via the command "iptables -L". 
>>
>>
>> # iptables -L
>> Chain INPUT (policy ACCEPT)
>> target prot opt source destination
>>
>> Chain FORWARD (policy ACCEPT)
>> target prot opt source destination
>>
>> Chain OUTPUT (policy ACCEPT)
>> target prot opt source destination
>>
>> 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.
>>
>>
>> Which, naturally, would involve knowing how to toy around with them, 
>> so I am off, for the moment, to here: 
>> http://iptables-tutorial.frozentux.net/iptables-tutorial.html
>>
>> at least now I know where I should be looking (maybe)
>>
>>>
>>> Oh, and HTH = Hope this helps. ;) 
>>
>>
>> New TLAs every day ;)
>>
>>>
>>> Kyle
>>
>>
>>
>>
>> Thanks,
>> S.
>>
>>
>>
>>>
>>>
>>> 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.
>>>
>>>
>>
>