Hello, I have been told by SuSE support that they will not support this problem in their base system so I am hopping that someone here can answer the problem or pass it on to someone at SuSE who won't just write it off as unsupported. We have an ldap server at work hosting user accounts and automount settings. It has worked fine for a while now, with both Redhat and Debian clients..but SuSE is another story completelly. Running /etc/init.d/autofs status returns the list of automount points correctly as follows: Configured Mount Points: ------------------------ /usr/sbin/automount /home ldap:ou=auto.home,dc=optitech,dc=com /usr/sbin/automount /optitech ldap:ou=auto.optitech,dc=optitech,dc=com But, after starting autofs (it claims to be successfull) I see the following error in /var/log/messages: automount[2058]: starting automounter version 3.1.7, path = /home, maptype = ldap:ou=auto.home,dc=optitech,dc=com, mapname = none automount[2058]: cannot open lookup module ldap:ou=auto.home (/usr/lib/autofs//lookup_ldap:ou=auto.home.so: cannot open shared object file: No such file or directory) automount[2060]: starting automounter version 3.1.7, path = /optitech, maptype = ldap:ou=auto.optitech,dc=optitech,dc=com, mapname = none automount[2060]: cannot open lookup module ldap:ou=auto.optitech (/usr/lib/autofs//lookup_ldap:ou=auto.optitech.so: cannot open shared object file: No such file or directory) Now, it seems to be trying to open the lookup_ldap.so module, but what's with that :ou=auto.home string thrown into there? I'm assuming this is the root of my autofs problems, anyone have any ideas? Thanks for any help, Sébastien