Date: Mon, 27 Oct 1997 05:53:28 -0500 From: "Troy Settle" <rewt@i-Plus.net> To: "(ML) FreeBSD Questions" <freebsd-questions@FreeBSD.ORG> Subject: NFS revisited - is it just me, or is this messed up? Message-ID: <01bce2c6$8e862810$2ced63ce@abyss>
next in thread | raw e-mail | index | archive | help
Ok, after much playing around, I finally got NFS working again. Here's
what happened:
Originally, I was mounting NFS volumes between 2 machines, and everything
worked fine. After a network renumbering, NFS refused to work, and would
crash the client machine.
I finally found the problem:
inet 208.24.67.2 netmask 0xffffff00 broadcast 208.24.67.255
inet 208.24.67.15 netmask 0xffffffff broadcast 208.24.67.15
.2 is the primary IP on the NSF server, .15 is an aliased IP
I was trying to NFS mount useing the aliased IP, which was causing
problems. I was only successful after trying the primary IP.
What gives? Shouldn't this work either way? I stumbled on the solution
when trying to use tftpd on the same server. trying to load a firmware
image to a terminal server, tftpd kept refusing connection. Finally in a
fit, I typed in the actual IP address of the machine (as opposed to the
name for the aliased IP), and it worked. Scratching my head, I tried this
with NFS, and it too worked.
Could someone please explain to me what's up with this? Why it's gotta be
so frustrating? My shell server was down for days while I sat around
scratching my head trying to figure it out. (No mention of this stuff in
the manpage, handbook, or FAQ)
Thanks,
--
Troy Settle -- - -- - -- -- Got 'Net? --
Network Administrator | This space | Explore the world with
st@i-Plus.net | for rent | iPlus Internet Services
ICQ: 1625842 -- - -- - -- http://www.i-Plus.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?01bce2c6$8e862810$2ced63ce>