Advertisement

07.17.2008 at 08:14AM PDT, ID: 23573484
[x]
Attachment Details

Winbind ADS client configuration problem

[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

9.1
Hello Experts,

Need your help desparetly.

We are on the job of configuring  Windows 2k3 ADS winbind clients in the RHEL ES 4 machines. In the attached document, I have given the steps which we follow to do this. We've followed the same procedure for RHEL 5 version and it works perfectly fine. But when we start doing it for RHEL 4, it gave some issues.  First, winbind service isn't starting properly, it gave "winbindd dead but subsys locked" error and finally we made it running by upgrading all the Samba packages and by executing the following commands:
 setsebool -P "winbind_disable_trans"=1
 setenforce 0

And then, we were able to join the RHEL 4 Linux host to ADS server and 'wbinfo' provides the user account informaion. But when we try to connect the server using ADS account, its throwing out the error: "Server unexpectedly closed network connection" but when i try to connect using Linux local user account, it works (but not ADS user accounts).

I believe this problem is happening only because of PAM configuration file (/etc/pam.d/system-auth).
Could you please verify this file?  FYI, the same configuration is working fine with RHEL 5 version.

Please let me know if you require more inputs on this issue.

Thanks in advance.

Ashok
Attachments:
 
Binding Linux host with ADS server steps
 
 
Expert Comment by Nopius:

All comments and solutions are available to Premium Service Members only. Start your 7-day free trial to view the solution to this question.

Already a member? Login to view this solution.

 
 
Accepted Solution by Nopius:

All comments and solutions are available to Premium Service Members only. Start your 7-day free trial to view the solution to this question.

Already a member? Login to view this solution.

 
 
20081119-EE-VQP-46 / EE_QW_2_20070628