[kraaft]

[QUOTE][u]Quote by: Radiola[/u][p]kraaft, if I may ask, how did you hit on this solution? (It seems to work on my workstation, BTW.) That never came *close* to occuring to me, and I hope there’s a diagnostic lesson in this someplace. 🙂

– Aaron[/p][/QUOTE]

I read about the possibility in a post regarding other login problems so i thought I’d apply it here. The error message saying something like ‘your home directory seems to be on an afp or smb volume’ hinted to me that the system seemed to be expecting something else (nfs mount?). So disabling an unused nfs automount service seemed reasonable.
That still doesn’t explain why the error occurs at all though.

[kraaft]

The 10.4.10 update didn’t solve the problem but I finally found a solution:

change the following entry in /etc/hostconfig:
AUTOMOUNT=-YES- to AUTOMOUNT=-NO-

This disables NFS automount and solves the problem. So if you don’t need nfs mounts you’re fine.

I used the following unix command in Apple Remote Desktop to change this on all my machines:
[code]
perl -p -i.bak -e ‘s/AUTOMOUNT=-YES-/AUTOMOUNT=-NO-/’ /etc/hostconfig
[/code]

[kraaft]

The problem is strictly related to the update as i tested it on several machines (ppc and intel) before and after the update.

I tried the troubleshooting solutions from macfixit.
– Disconnecting and rebinding to the AD
– Restoring the smbfs and smbmount files that had been changed with the update (with that the network homes allways failed to mount)
– deleting loginwindow and directory access prefs

[Author]

Posts