[BusyBox] NFS: mount program didn't pass remote address!
Joel Buckley
leojava at comcast.net
Thu Mar 31 23:58:53 UTC 2005
Remco,
Just a typo issue...
Replace:
# mount -t nfs -o nolock,ro,nfsvers=2 192.168.1.1/tmp /mnt
With:
# mount -t nfs -o nolock,ro,nfsvers=2 192.168.1.1:/tmp /mnt
Cheers,
leoj
John Williams wrote:
> Remco van Strien wrote:
>
>> Hi,
>>
>> I'm using linux kernel 2.6.11.3 with buildroot with BusyBox v1.00 for
>> my target. I'm trying to connect to the host share at
>> 192.168.1.1:/tmp. This directory is shared succesfully, i can connect
>> there locally with the host. However when i try to connect with my
>> client I get the following:
>>
>> # mount -t nfs -o nolock,ro,nfsvers=2 192.168.1.1/tmp /mnt
>> nfs warning: mount version newer then kernel
>> NFS: mount program didn't pass remote address!
>> mount: Mounting 192.168.1.1/tmp on /mnt failed: Invalid argument.
>>
>>
>> I also tried:
>> # mount 192.168.1.1:/tmp /mnt
>> nsf warning: mount version older than kernel
>> portmap: server localhost not responding, timed out
>> RPC: failed to contact portmap (errno -5).
>> portmap: server localhost not responding, timed out
>> RPC: failed to contact portmap (errno -5).
>> lockd_up: makesock failed, error=-5
>> portmap: server localhost not responding, timed out
>> RPC: failed to contact portmap (errno -5).
>>
>> Any suggestions??
>
>
> Have you run portmap?
>
> $ portmap &
>
> $ mount -t nfs .....
>
> Regards,
>
> John
>
>------------------------------------------------------------------------
>
>_______________________________________________
>busybox mailing list
>busybox at mail.busybox.net
>http://busybox.net/mailman/listinfo/busybox
>
>
More information about the busybox
mailing list