On Sat, 20 Jan 2001, Manuel Bouyer wrote:

>On Fri, Jan 19, 2001 at 03:51:11PM -0600, Ruibiao Qiu wrote:
>> NetBSD(i386) 1.4.1.
>
>Ok. Sorry, I don't have much idea. Could you try to run tcpdump to see what
>requests fails ?

Here are the tcpdump output ('tcpdump -vvv port 2049'):

tcpdump: listening on ex0
11:52:31.564170 client.2277988137 > server.nfs: 92 fsinfo [|nfs] (ttl 64, id 16154)
11:52:31.564397 server.nfs > client.2277988137: reply ok 32 fsinfo [|nfs] (ttl 64, id 2014)
11:52:31.564884 client.2277988138 > server.nfs: 92 fsstat [|nfs] (ttl 64, id 16155)
11:52:31.564984 server.nfs > client.2277988138: reply ok 32 fsstat [|nfs] (ttl 64, id 2015)
11:52:31.574290 client.2277988144 > server.nfs: 92 fsinfo [|nfs] (ttl 64, id 16161)
11:52:31.574383 server.nfs > client.2277988144: reply ok 32 fsinfo [|nfs] (ttl 64, id 2016)
11:52:31.574858 client.2277988145 > server.nfs: 92 fsstat [|nfs] (ttl 64, id 16162)
11:52:31.574951 server.nfs > client.2277988145: reply ok 32 fsstat [|nfs] (ttl 64, id 2017)
11:52:31.586281 client.2277988152 > server.nfs: 92 fsinfo [|nfs] (ttl 64, id 16169)
11:52:31.586373 server.nfs > client.2277988152: reply ok 32 fsinfo [|nfs] (ttl 64, id 2018)
11:52:31.586828 client.2277988153 > server.nfs: 92 fsstat [|nfs] (ttl 64, id 16170)
11:52:31.586923 server.nfs > client.2277988153: reply ok 32 fsstat [|nfs] (ttl 64, id 2019)
11:52:31.591715 client.2277988160 > server.nfs: 92 fsinfo [|nfs] (ttl 64, id 16177)
11:52:31.591808 server.nfs > client.2277988160: reply ok 32 fsinfo [|nfs] (ttl 64, id 2020)
11:52:31.592271 client.2277988161 > server.nfs: 92 fsstat [|nfs] (ttl 64, id 16178)
11:52:31.592364 server.nfs > client.2277988161: reply ok 32 fsstat [|nfs] (ttl 64, id 2021)
11:52:31.597161 client.2277988168 > server.nfs: 92 fsinfo [|nfs] (ttl 64, id 16185)
11:52:31.597253 server.nfs > client.2277988168: reply ok 32 fsinfo [|nfs] (ttl 64, id 2022)
11:52:31.597710 client.2277988169 > server.nfs: 92 fsstat [|nfs] (ttl 64, id 16186)
11:52:31.597801 server.nfs > client.2277988169: reply ok 32 fsstat [|nfs] (ttl 64, id 2023)
11:52:31.602578 client.2277988176 > server.nfs: 92 fsinfo [|nfs] (ttl 64, id 16193)
11:52:31.602671 server.nfs > client.2277988176: reply ok 32 fsinfo [|nfs] (ttl 64, id 2024)
11:52:31.603129 client.2277988177 > server.nfs: 92 fsstat [|nfs] (ttl 64, id 16194)
11:52:31.603221 server.nfs > client.2277988177: reply ok 32 fsstat [|nfs] (ttl 64, id 2025)
11:52:31.604694 client.2277988179 > server.nfs: 120 getattr [|nfs] (ttl 64, id 16196)
11:52:31.604793 server.nfs > client.2277988179: reply ok 28 getattr [|nfs] (ttl 64, id 2026)
11:52:31.608007 client.2277988184 > server.nfs: 92 fsinfo [|nfs] (ttl 64, id 16201)
11:52:31.608098 server.nfs > client.2277988184: reply ok 32 fsinfo [|nfs] (ttl 64, id 2027)
11:52:31.608555 client.2277988185 > server.nfs: 92 fsstat [|nfs] (ttl 64, id 16202)
11:52:31.608647 server.nfs > client.2277988185: reply ok 32 fsstat [|nfs] (ttl 64, id 2028)
11:52:31.617278 client.2277988186 > server.nfs: 120 getattr [|nfs] (ttl 64, id 16207)
11:52:31.617449 server.nfs > client.2277988186: reply ok 28 getattr [|nfs] (ttl 64, id 2033)
^C
132 packets received by filter
0 packets dropped by kernel


          Regards

            Ruibiao