Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!news.kei.com!bloom-beacon.mit.edu!spool.mu.edu!torn!ccshst05.cs.uoguelph.ca!ccshst01.cs.uoguelph.ca!rmacklem From: rmacklem@uoguelph.ca (Rick Macklem) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: FBSD 2.0.5R: "Port mapper failure" and NFS lockups Date: 3 Jul 1995 15:59:06 GMT Organization: University of Guelph Lines: 23 Message-ID: <3t944a$ln7@ccshst05.cs.uoguelph.ca> References: <1995Jun30.214222.10887@tellab5.tellabs.com> NNTP-Posting-Host: ccshst01.cs.uoguelph.ca X-Newsreader: TIN [version 1.2 PL2] Mike Borowiec (mikebo@tellabs.com) wrote: [stuff deleted] : What's more, one of the NFS servers I use is multi-homed. Coincident : with the above failures, I was suddenly unable to mount my home : directory partition via the interface I had been using for several : days. The mount hung my boot sequence, so I booted single user and : changed /etc/fstab to reflect a different interface on the same : server and - voila - it worked just fine. I should point out that : there are many other NFS clients using this server and none have had : these problems. See the Sniffer trace of the problem below, which : seems to indicate a problem with port numbers (?). Normally NFS will expect the server to reply from the same IP address that the reuest was sent to and this could cause grief for a multi-homed server. Try the "-c" mount option to turn off the "UDP connect", so that any reply to the client's IP address/port # will be seen by the mount point. (If the server is not on the same LAN as the client, I would also suggest taking a close look at "netstat -r" to see that your route(s) to the server make sense.) Good luck with it, rick