[Date Prev][Date Next]
Re: autofs and linux client - wierdness
Thanks for the reply Andrea... yes I already have allow bind_v2 and
allow bind_anon_dn. autofs binds anonymously while it searches for the
automount maps, when it finds them it trys to bind _as the dn of the
map_ with no password.
Do you have this working then?
On Tue, 2003-07-01 at 13:42, Andrea Albert wrote:
> have you considered to allow bind_v2 in the slapd.conf file?
> Greg Matthews wrote:
> > This is driving me potty!
> > I've tried every combination I can think of to get my Linux clients
> > using ldap for autofs. User auth is working fine but autofs will not
> > play ball...
> > no matter whether I use the nisMapName/nisObject or the
> > automountMap/automount schema. Nor whether I use slapd to serve
> > auto.master (and "automount: ldap" in nsswitch.conf) or use
> > /etc/auto.master to point at the server ("automount: files" in
> > nsswitch.conf).
> > Sniffing the network traffic, the client searches for the map (This is
> > redhat9 and it looks for both schemas nis* first then automount*), finds
> > the map, and then tries to bind to the server with either
> > nismapname=auto.users,<basedn> or ou=auto.users,<basedn> depending on
> > the schema. slapd doesnt like that and so autofs complains it cant
> > contact the server.
> > Why is it trying to bind to the server with this dn?? Why is it trying
> > to bind at all?
> > I've googled for other ppls configs but whatever I try, I get the same
> > results.
> > Does someone have this combination working? Linux client, autofs over
> > ldap? Has anyone seen this behaviour? I'm willing to post ethereal
> > dumps, log messages, config files etc... Is anyone able to post configs
> > for this?
> > GREG
> > ps solaris client working well now, just linux causing headaches.
iTSS Wallingford 01491 692445