Hi!
I have a major issue with FreeBSD 7.1 i386.
We did a change in our Unix env where we exchanged home storage from a NetAPP running udp to a NetAPP running tcp.
Now I cant mount homedirs since NFS/AMD seem to fallback to udp 
Trying to force it with amd options nfs_proto=tcp and so on.
I can manually mount my homedir if I use "mount_nfs -T ...."
how do I force AMD to use the "mount_nfs -T" command?
Does any one know what "type nfs, state not responding" means?
does it have to do with statd?
Sep 27 09:16:26 MASKEDHNAME amd[1558]/info: find_nfs_srvr: force NFS version to 3
Sep 27 09:16:26 MASKEDHNAME amd[1558]/info: find_nfs_srvr: force NFS protocol transport to tcp
Sep 27 09:16:26 MASKEDHNAME amd[1558]/warn: fileserver filer.ourdomainmasked is already hung - not running NFS proto/version discovery
Sep 27 09:19:05 MASKEDHNAME amd[1558]/map: matched default selectors "type:=nfs;opts:=rw,grpid,nosuid,utimeout=600"
Sep 27 09:19:05 MASKEDHNAME amd[1558]/map: key maskedusr: map selector host (=MASKEDHNAME) did not match filer.ourdomainmasked
Sep 27 09:19:05 MASKEDHNAME amd[1558]/map: Map entry host==filer.ourdomainmasked;type:=link;fs:=/vol/volh04006/x1/0/32/maskedusr for /home/maskedusr did not match
Sep 27 09:19:05 MASKEDHNAME amd[1558]/info: find_nfs_srvr: force NFS version to 3
Sep 27 09:19:05 MASKEDHNAME amd[1558]/info: find_nfs_srvr: force NFS protocol transport to tcp
Sep 27 09:19:05 MASKEDHNAME amd[1558]/info: get_nfs_version: returning NFS(3,tcp) on host filer.ourdomainmasked
Sep 27 09:19:05 MASKEDHNAME amd[1558]/info: Using NFS version 3, protocol tcp on host filer.ourdomainmasked
Sep 27 09:19:05 MASKEDHNAME amd[1558]/info: initializing filer.ourdomainmasked's pinger to 30 sec
Sep 27 09:19:05 MASKEDHNAME amd[1558]/map: Trying mount of lnhome2:/vol/volh04006/x1/0/32/maskedusr on /.amd/lnhome2/vol/volh04006/x1/0/32/maskedusr fstype nfs mount_type non-autofs
Sep 27 09:19:11 MASKEDHNAME amd[1558]/map: last message repeated 3 times
Sep 27 09:19:11 MASKEDHNAME amd[1558]/info: file server filer.ourdomainmasked, type nfs, state not responding
Sep 27 09:19:11 MASKEDHNAME amd[1558]/map: Trying mount of lnhome2:/vol/volh04006/x1/0/32/maskedusr on /.amd/lnhome2/vol/volh04006/x1/0/32/maskedusr fstype nfs mount_type non-autofs
Sep 27 09:19:14 MASKEDHNAME amd[1558]/map: last message repeated 2 times
Sep 27 09:19:14 MASKEDHNAME amd[1558]/info: file server filer.ourdomainmasked, type nfs, state not responding
Sep 27 09:19:15 MASKEDHNAME amd[1558]/map: Trying mount of lnhome2:/vol/volh04006/x1/0/32/maskedusr on /.amd/lnhome2/vol/volh04006/x1/0/32/maskedusr fstype nfs mount_type non-autofs
Sep 27 09:19:17 MASKEDHNAME amd[1558]/info: file server filer.ourdomainmasked, type nfs, state not responding
Sep 27 09:19:17 MASKEDHNAME amd[1558]/info: file server filer.ourdomainmasked, type nfs, state starts down
Without nfs_proto=tcp and nfs_vers=3 set I get the following, and thats true, udp is not usable on the new filer.
Sep 27 10:02:37 MASKEDHNAME amd[950]/info: get_nfs_version: returning NFS(3,tcp) on host filer.ourdomainmasked
Sep 27 10:02:43 MASKEDHNAME amd[950]/info: get_nfs_version NFS(3,udp) failed for filer.ourdomainmaskedRPC: Timed out
Sep 27 10:02:43 MASKEDHNAME amd[950]/info: get_nfs_version trying a lower version: NFS(2,udp)
Br /D.