this is a classic gotcha with solaris and padl migration tools.
you have the answer in the log...
On Thu, 2003-09-11 at 16:28, Tibbetts, Ric wrote:
Sep 11 11:31:44 meeng3 slapd: [ID 902418 local4.debug] conn=47
op=1 SRCH base="ou=people,dc=ldap-test,dc=com" scope=2
Sep 11 11:31:44 meeng3 slapd: [ID 706578 local4.debug] conn=47
op=1 SRCH attr=uid userpassword shadowflag
Sep 11 11:31:44 meeng3 slapd: [ID 362707 local4.debug] conn=47
op=1 SEARCH RESULT tag=101 err=0 nentries=0 text=
Solaris requires that each account has objectclass: shadowAccount. Add
this objectclass to each account and all will be well. A small
adjustment to the PADL script will prevent this happening again.
Good luck with the solaris clients, theres nothing too tricky...
If logged into a client as root, I can identify a user:
#> id [user-name]
works, and it returns the expected values.
But trying login fails with "Login Incorrect"
So it's recognises the ueser, but is not getting the password?
I can put the config file on a web site, if anyone needs to see those.
But I'm hoping that the above output will provide enough clues.
Server OS: Solaris 9
Any assistance will, as always, be greatly appreciated.
I've come a long way with this installation. Just a little more to go!