From owner-freebsd-questions Sat Oct 25 18:06:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA04015 for questions-outgoing; Sat, 25 Oct 1997 18:06:13 -0700 (PDT) (envelope-from owner-freebsd-questions) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA03986 for ; Sat, 25 Oct 1997 18:05:59 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.8.7/8.8.5) id LAA21730; Sun, 26 Oct 1997 11:35:43 +1030 (CST) Message-ID: <19971026113542.60338@lemis.com> Date: Sun, 26 Oct 1997 11:35:42 +1030 From: Greg Lehey To: Troy Settle Cc: "(ML) FreeBSD Questions" Subject: Re: NFS help References: <01bce178$0d18de70$2ced63ce@abyss> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84e In-Reply-To: <01bce178$0d18de70$2ced63ce@abyss>; from Troy Settle on Sat, Oct 25, 1997 at 02:58:59PM -0400 Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Fight-Spam-Now: http://www.cauce.org Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, Oct 25, 1997 at 02:58:59PM -0400, Troy Settle wrote: > Hey all, > > I'm having a bit of a problem with NFS between 2 FreeBSD boxes. The > server is a 2.2-STABLE box, and the client is a 2.2.1-RELEASE. > > NFS has been working between these 2 boxes for nearly 10 months, and just > started screwing up after changing the IP addresses. I've checked through > /etc/host.conf, /etc/hosts, DNS entries, and everything checks out fine. > But I still can not get NFS working again. (All other IP stuff such as > telnet, ftp, dns are working fine) > > What happens, is that when I try to mount the remote filesystem, mount_nfs > just hangs, locking up the whole machine in a matter of minutes. I have > no idea what's going on, there's no syslog messages of any sort, no > console messages, nothing to indicate where the problem is. > > If anyone has any clues to offer me, I would be very grateful. Use tcpdump to see what it's trying to talk to. You'll probably find it's still looking for an old IP address, and the output of tcpdump should be immediately enlightening. If not, let's see it. Greg