HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- RHEL5.3 bindpw
Operating System - Linux
1827894
Members
1547
Online
109969
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-06-2009 07:08 AM
02-06-2009 07:08 AM
Hallo,
The server is not a member of a windows domain. But we have an AD user-account. With the clear bind password in the /etc/ldap.conf, the communication to the AD-Server work well and the login into the rhel-server with the AD account, too.
1.) We tried to crypt the password in the /etc/ldap.conf with,
bindpw {crypt} xxxx...
and
bindpw {MD5} yyyyy...
Both doesn't work.
2.) We removed the bindpw entry in the config file and wrote the clear password into the /etc/ldap.secret (600) file. It doesn't work too.
Do you have some ideas for us?
Thanks for your support, Uli
The server is not a member of a windows domain. But we have an AD user-account. With the clear bind password in the /etc/ldap.conf, the communication to the AD-Server work well and the login into the rhel-server with the AD account, too.
1.) We tried to crypt the password in the /etc/ldap.conf with,
bindpw {crypt} xxxx...
and
bindpw {MD5} yyyyy...
Both doesn't work.
2.) We removed the bindpw entry in the config file and wrote the clear password into the /etc/ldap.secret (600) file. It doesn't work too.
Do you have some ideas for us?
Thanks for your support, Uli
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-08-2009 06:54 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-08-2009 11:21 PM
02-08-2009 11:21 PM
Re: RHEL5.3 bindpw
Hallo Ivan,
a newline at the end of the ldap.secret doesn't solved the problem.
Uli
a newline at the end of the ldap.secret doesn't solved the problem.
Uli
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-09-2009 12:23 AM
02-09-2009 12:23 AM
Re: RHEL5.3 bindpw
Shalom,
There could be other problems in the /etc/ldap.secret file or other configuration files. Check to see if one of them has been replaced by the upgrade (if that is what you did) to RHEL 5.3.
Also check RH web site for errata or possibly a new rpm related to this error.
Please tell us more about your upgrade path. Hardware, system type. Whether it was a fresh cold install or an upgrade with yum.
SEP
There could be other problems in the /etc/ldap.secret file or other configuration files. Check to see if one of them has been replaced by the upgrade (if that is what you did) to RHEL 5.3.
Also check RH web site for errata or possibly a new rpm related to this error.
Please tell us more about your upgrade path. Hardware, system type. Whether it was a fresh cold install or an upgrade with yum.
SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP