How did you determine that the problem is with pam_winbind? What do you get as output from "wbinfo -u" and
"wbinfo -g"?
Main Topics
Browse All TopicsHello
I have joined my Solaris 10 u6 box to my Win 2003 AD domain using the following process
http://nineproductions.com
now when i run 'passwd -r files root' i get
'passwd -r files root
New Password:
Permission denied'
this applies to all local user accounts on the Solaris system.
Any suggestions?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
wbinfo -u and wbinfo -g gives me the correct users and groups of my AD domain.
I determined it was pam_winbind as it works with password management.
It was set to required, the solution was to set it to sufficient. This has to do with how PAM authentication works, with sufficient if winbind.so fails, the operation fails unless a module invoked after it succeeds. Important to note is that if a 'required' module fails before a 'sufficient' one succeeds, the operation will fail anyway, ignoring the status of any 'sufficient' modules.
All is well now.
Business Accounts
Answer for Membership
by: f3tpadminPosted on 2009-04-07 at 12:38:41ID: 24091061
Just to add another piece of info, I found out that the line
'other password required pam_winbind.so'
in /etc/pam.conf seems to be causing the problem... but not sure what the solution is.