If you’ve been following along, you already know the beast. Awesome piece of hardware, frankly, with decent firmware/software to boot. Buuuuut… One of the “updates” (I’ve forgotten which, and do not feel like looking it up) upgraded NFS from version 3 to 4. By default, NFS v. 4 adds “security”.
Which is fine and wonderful, except that I’m on an isolated network anyway, and NFS3 worked fine, and VMWare wasn’t ready for NFS 4 at the time. Thus, it had no provision for the directive NEED_SVCGSSD=yes found in the /etc/default/nfs-kernel-server configuration file.
So, to work around this, fast and dirty, enable “diagnostic mode”, then change this entry using vi (you do know how to use vi, right?) to “no”, and then restart the service with /etc/init.d/nfs-kernel-server restart
Baddaboom baddabing.
I’m not saying this is the RIGHT way to fix the problem; only that it works.
Oh, bad news. You have to re-do this each time the server is restarted (unless you can figure out how to get this change into the squashfs, which I’m not going into here).
sypak 