From owner-freebsd-questions Wed Nov 3 22:32:49 1999 Delivered-To: freebsd-questions@freebsd.org Received: from everest.overx.com (everest.overx.com [63.82.145.202]) by hub.freebsd.org (Postfix) with ESMTP id 4B7F314F05 for ; Wed, 3 Nov 1999 22:32:31 -0800 (PST) (envelope-from dayton@overx.com) Received: from polo.overx.com (polo.overx.com [63.82.145.204]) by everest.overx.com (Postfix) with ESMTP id 57A6D1F93 for ; Sun, 31 Oct 1999 14:09:17 -0600 (CST) Received: by polo.overx.com (Postfix, from userid 1001) id 2DE683EFA; Wed, 3 Nov 1999 14:09:09 -0600 (CST) From: Soren Dayton Reply-To: dayton@overx.com To: freebsd-questions@freebsd.org Subject: complete Solaris 7/FreeBSD 3.3 NFS interoperability failure Date: 03 Nov 1999 14:09:08 -0600 Message-ID: <86iu3j49sr.fsf@polo.overx.com> Lines: 26 User-Agent: Gnus/5.070095 (Pterodactyl Gnus v0.95) XEmacs/21.1 (Big Bend) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Whenever I mount a directory from a FreeBSD 3.3 machine onto a Solaris 7 machine, the FreeBSD 3.3 machine hangs. That is to say _ALL_ NFS requests fail, I can't log in as root, etc. If I set use NFS version two on the server (mountd -r -2), automount on the Solaris machine fails due to a version mismatch. Then if I mount by hand (with -overs=2), I get the same failure behavior, which is that after the mount request (succeeds), the NFS server completely freezes up. Has anyone seen this kind of thing before? (Noting the comment in the handbook, dmesg reports that the ethernet device is: fxp0: rev 0x08 int a irq 19 on pci0.9.0 which I suspect doesn't have the problem mentioned in the handbook) Any clues? Thanks Soren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message