Maybe it doesn't help much here. It just *could* be that it doesn't have to do anything with the network being up, but with DNS resolution?
I have had the problem on one computer (don't know why), and spotted the following line in /var/log/syslog:
mount[859]: mount.nfs: Failed to resolve server kerberos: Temporary failure in name resolution
So I tested a bit, and found that if I put "kerberos" with the right IP into /etc/hosts, it works perfectly.
So maybe it is the problem that the name resolution at the boot time when NFS shares should be mounted, does still not work.
Maybe it doesn't help much here. It just *could* be that it doesn't have to do anything with the network being up, but with DNS resolution?
I have had the problem on one computer (don't know why), and spotted the following line in /var/log/syslog:
mount[859]: mount.nfs: Failed to resolve server kerberos: Temporary failure in name resolution
So I tested a bit, and found that if I put "kerberos" with the right IP into /etc/hosts, it works perfectly.
So maybe it is the problem that the name resolution at the boot time when NFS shares should be mounted, does still not work.