Timed out problem - NFS
This is a discussion on Timed out problem - NFS ; Hi,
after changing of subnet from 192.168.95 to 192.168.101 I tried to mount:
mount 192.168.101.198:/mnt/vol1 /fs/vol1
instead of mount 192.168.95.198:/mnt/vol1 /fs/vol1
and received:
RPC MNT RPC Timed out
What could be the reason for that?
Bye...
-
Timed out problem
Hi,
after changing of subnet from 192.168.95 to 192.168.101 I tried to mount:
mount 192.168.101.198:/mnt/vol1 /fs/vol1
instead of mount 192.168.95.198:/mnt/vol1 /fs/vol1
and received:
RPC MNT RPC Timed out
What could be the reason for that?
Bye
-
Re: Timed out problem
Carsten Buschina wrote in message news:...
> Hi,
>
> after changing of subnet from 192.168.95 to 192.168.101 I tried to mount:
>
> mount 192.168.101.198:/mnt/vol1 /fs/vol1
>
> instead of mount 192.168.95.198:/mnt/vol1 /fs/vol1
>
> and received:
>
> RPC MNT RPC Timed out
>
> What could be the reason for that?
>
> Bye
Hi,
I am trying to do a similar thing and get a similar error
mount: RPC : Time out
Here is what I am trying to do:
1. I have a computer setup with a private lan- 10.1.1.0/24
Computer 1 (C1) has address 10.1.1.1
C2 10.1.1.2
and I donot have any name services running (neither NIS nor DNS).
C1 has a route to C2 added using route add and simarly C2 has a route
to C1.
When I do rpcinfo -p 10.1.1.1 from C2's terminal, I do get the
information about C1's nfs daemons.
However when I try to mount folders in C2 from C1, I get an error
mount: RPC : Time Out
What seems to be wrong? What can I do to eliminte this error. My
question would be, does NFS work without name servers? I ask this
because when I tried doing the same stuff using a DNS server, I was
able to mount the directories without any problems.
Thanks in Advance.
VS