On Wed, 2007-03-14 at 17:24 +1000, Brendan Kelly wrote: > The only thing I've managed to get working so far under sles9sp3 on z is > export to *, ie > /opt *
I've seen the kind of thing Brendan mentions here, but usually it happens because I have hostnames (well domains actually, such as *.example.com) instead of IP addresses in my /etc/exports, and at the time the new client connected her DNS name was not yet set, but the NFS server remembers that and needs to be recycled after the DNS is fixed. I have also seen situations where a client was trying to mount a directory and getting rejected, the error message claiming that "/" was not exported. This seemed to reflect on the different way that exports and mounts are done in NFSv4, but I couldn't see that the client would have been trying to use v4. Anyway, more recent releases of NFS seem to be trickier than they used to be. Now, I need to include all kinds of options on my Linux server in order for my Mac OS X machine to mount its exports. One client needs one setting, which breaks someone else. And don't get me started on automount. :) [1] Someone did mention the way to export to a subnet, which should work for the OP's VPN connection. You may also need to use the "insecure" option on the /etc/exports line; like my Mac, your client might be getting rejected because it's using high ports. The server's log should tell you about why the client is being rejected. The other thing to check is that all the appropriate NFS support daemons (portmap, lockd, mountd, statd) are running on both client and server (rpc.mountd shouldn't be needed on the client, but if something that *is* needed isn't there you're likely to get strangeness). Cheerio, Vic Cross [1] I do like autofs very much, but I want mount maps in my LDAP, which took WAY longer than it should have to get working consistently across distros (and it *still* doesn't work on Mac OS X). Looks like things might be on the mend though -- I put some Ubuntu Edgy in my network recently and they Just Worked. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
