Checked the FAQ and the nutshell NFS book but didn't see anything, and I  
suspect that this is Solaris-specific anyway.  I'm experienced with SunOS but  
not with Solaris, so be kind.  If I missed this in the faq just let me know.

Thanks!
Tim
tr...@gun.com

Run snoop on the 2.4 machine and take a look at the traffic
between client and server.  That will probably give you
a pretty good indication of the problem.

        Brent

'snoop' just show the LAN traffic, but won't solve the problem.  Try this,

(1) If you have multiple LAN connection, i.e. multiple LAN card in the system,
    make sure /etc/inet/netmasks was set correctly.

(2) If you use 'other' DNS,

    (a) Make sure there is no conflict IP address with your local
        /etc/inets/hosts file.

    (b) Put NFS serve name-address in the local hosts table, and set
        nsswitch.conf to check files first.

If you find other fix that works, please let me know.  I had this problem
before, but was fixed by the above actions.

Joseph

        mount -o rsize=1024 nextstep_server:/Users /Users

worked for me.  wsize seemed to have no effect, although I did verify that  
large files are getting written OK from the Solaris client to the NEXTSTEP  
server.  I expect NFS reads to be a little slower than they could be on the  
Sparc side, but slower than perfect is better than not at all, IMO.  Since most  
of the server responsibilities will be moving to a Solaris server, I'm not as  
concerned about this as others might.

I'm going to continue testing this.  If I find out anything else, the net will  
be the second to know.

Thanks to Brent Callaghan and Joseph Shyanwee Jao for responding.
Regards,
Timothy Reed
tr...@gun.com