[vox-tech] NFS:mount RPC timed out

[xiao.liang at cn.alps.com]

I use kernel 2.4.20,busybox 1.3.1,the NFS server is V4.When I try to mount 
use 

mount -t nfs 10.25.16.130:/opt/Qtopia /opt/Qtopia 

Got error ,mount: RPC time out 

When I use ethreal on both the server and client side , found that the 
server have sent SYN,ACK back to client with the TCP connection, but the 
client just do not respond. I use portmap and also inetd. The tcpdump log 
is look like this: 

10.25.16.160.794 > 10.25.16.130.sunrpc: S, cksum 0x5740 (correct), 
31406388 

10.25.16.130.sunrpc > 10.25.16.160.794: S, cksum 0x79e6 (correct), 
2533961748:2 
10.25.16.130.sunrpc > 10.25.16.160.794: S, cksum 0x79e6 (correct), 
2533961748:2 
60) 10.25.16.160.794 > 10.25.16.130.sunrpc: S, cksum 0x5614 (correct), 
31406388 
10.25.16.130.sunrpc > 10.25.16.160.794: S, cksum 0x76ff (correct), 
2533961748:2 
10.25.16.130.sunrpc > 10.25.16.160.794: S, cksum 0x76ff (correct), 
2533961748:2 
10.25.16.130.sunrpc > 10.25.16.160.794: S, cksum 0x76f8 (correct), 
2533961748:2 
10.25.16.130.sunrpc > 10.25.16.160.794: S, cksum 0x76f8 (correct), 
2533961748:2 


60) 10.25.16.160.794 > 10.25.16.130.sunrpc: S, cksum 0x53bc (correct), 
31406388 
10.25.16.130.sunrpc > 10.25.16.160.794: S, cksum 0x7123 (correct), 
2533961748:2 
10.25.16.130.sunrpc > 10.25.16.160.794: S, cksum 0x7123 (correct), 
2533961748:2 
10.25.16.130.sunrpc > 10.25.16.160.794: S, cksum 0x711c (correct), 
2533961748:2 
10.25.16.130.sunrpc > 10.25.16.160.794: S, cksum 0x711c (correct), 
2533961748:2 


10.25.16.130.sunrpc > 10.25.16.160.794: S, cksum 0x6563 (correct), 
2533961748:2 
60) 10.25.16.160.794 > 10.25.16.130.sunrpc: S, cksum 0x4f0c (correct), 
31406388 
10.25.16.130.sunrpc > 10.25.16.160.794: S, cksum 0x6561 (correct), 
2533961748:2 
10.25.16.130.sunrpc > 10.25.16.160.794: S, cksum 0x6563 (correct), 
2533961748: 


If it is the portmap and inetd's problem?
Following is some info:

In /etc/service 
sunrpc 111/tcp portmap 
sunrpc 111/udp portmap 

In /etc/inetd.conf 
#rstatd/1-3 dgram rpc/udp wait root /usr/sbin/tcpd rpc.rstatd 
#rusersd/2-3 dgram rpc/udp wait root /usr/sbin/tcpd rpc.rusersd 

Client use a random tcp port number to connect with server:111, then who 
will look after the SYN,ACK packet sent back by server, the inetd? Should 
I add a line in inetd.conf like "794    stream  tcp   nowait root portmap" 
, but it is a ramdom port number?! Or should there be a tcpd or sth run on 
my board????

Ask for help!!!!!

ps :

/usr/sbin/inetd 
/sbin/portmap
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.lugod.org/pipermail/vox-tech/attachments/20070831/64779882/attachment.htm