Try 'tcpdump -s 250 -w TRACE.nfs port 2049'
Make sure what ever it is you are copying over nfs is not
something that is 'secret'.

We can take a look and see if MOUNT is failing.

-Ober

Richard Chesler: [Reading a piece of paper] The first rule of Fight Club is you don't talk about Fight Club?
Narrator: [Voice-over] I'm half asleep again; I must've left the original in the copy machine.
Richard Chesler: The second rule of Fight Club - is this yours?
Narrator: Huh?
Richard Chesler: Pretend you're me, make a managerial decision: you find this, what would you do?

On Mon, 22 May 2006, Hisashi T Fujinaka wrote:

> Date: Mon, 22 May 2006 22:29:58 -0700 (PDT)
> From: Hisashi T Fujinaka <htodd@twofifty.com>
> To: current-users@NetBSD.org
> Subject: nfs in i386-current is still kind of broken, isn't it?
> 
> I have a hard time mounting nfs shares lately and I'm not sure what's
> the determining factor. My MacOS X machines can mount nothing, and my
> netbsd-3 machines can only mount one or two shares. Juggling the order
> in fstab allows me to mount different directories.
>
> Is there any debug info I can provide?
>
> -- 
> Hisashi T Fujinaka - htodd@twofifty.com
> BSEE(6/86) + BSChem(3/95) + BAEnglish(8/95) + MSCS(8/03) + $2.50 = latte
>