The fact that you're seeing that in your logs shows that autofs is working fine.. your host tried to mount the directory and was denied by the server. I'm seeing the exact same thing for some new linux boxes I just installed over the weekend and some of our NetApp filers, and we're seeing the same thing from some new Solaris hosts as well.
I'm wondering if there's some kind of name/ip caching bug on the netapps that caches a deny for a very long period if you try to mount before your netgroups/dns is updated with the new host information.
If you can mount them by hand on the same box not using autofs, then it seems more likely to be an autofs issue.
Michael
_______________________________________________ autofs mailing list [EMAIL PROTECTED] http://linux.kernel.org/mailman/listinfo/autofs
