The answer was that NFS had been started on the Solaris server with '-x tcp'
which says to exclude tcp. That got removed, the daemon restarted, and now
I can mount -o tcp just fine.
As to the error messages in /var/adm/messages, we'll have to see if
NFS-mounting with tcp fixes the problem.
Thanks,
Andy
-----Original Message-----
Hi,
We do an NFS mount on our Tru64 server of a directory on a Solaris server.
We routinely receive the following errors in the T64 /var/adm/messages file:
Mar 18 11:15:16 sif vmunix: NFS3 server nova not responding still trying
Mar 18 11:15:16 sif vmunix: NFS3 server nova ok
and these pairs of messages will spew out for hours as we try to copy files
to this location. This severly slows down what we're doing though it does
eventually finish.
Last week I saw a summary from Udo Grabowski concerning NFS errors. I found
this informative and very helpful.
When I issue the mount with the -v switch (verbose) I see that it is
utilizing udp and not tcp so I'd like to try switching to tcp. However, I
can't get the syntax right.
When I issue:
mount -t nfs -v proto=tcp
I receive a usage error message.
When I issue:
mount -t nfs -v -o tcp
I receive:
-o tcp
NFS Portmap: RPC: Program not registered
and it hangs until I ctrl-c it.
Anybody have an idea of how I should proceed? Do I need to do something on
the Solaris side?
Thank you.
Andy Cohen
Database Systems Administrator
Cognex Corporation
1 Vision Drive
Natick, MA 01760-2059
voice: 508/650-3079
pager: 877-654-0447
cell: 508/294-0863
fax: 508/650-3337
Received on Mon Mar 19 2001 - 20:21:45 NZST