[389-users] Several issues with 389 DS

[Ellsworth, Josh]

We are working on transitioning from Sun Directory Server 7 (SDSEE) to 389DS and are having trouble in one of our environments. We have had success in 2 environments simply exporting the directory from SDSEE, importing it into 389, and then putting the 389 server on the same IP as the old SDSEE box. 

In one environment, however, we are having issues with logins on a few boxes which are now pointing at 389.

1. On some boxes that I can still log into using SDSEE I am having to go in and use authconfig-tui to enable LDAP configuration. These are CentOS 5.5 with the following SSH packages installed:

openssh.x86_64                            4.3p2-41.el5_5.1             installed
openssh-clients.x86_64                    4.3p2-41.el5_5.1             installed
openssh-server.x86_64                     4.3p2-41.el5_5.1             installed

2. On one box that uses chroot for , I am unable to login against the 389 DS. I continually get "access denied" at the command prompt. This box is running centos 5.4 with the following versions installed:

openssh.x86_64                         4.3p2-36.el5_4.3                installed
openssh-askpass.x86_64                 4.3p2-36.el5_4.3                installed
openssh-clients.x86_64                 4.3p2-36.el5_4.3                installed
openssh-server.x86_64                  4.3p2-36.el5_4.3                installed

Does anyone have any idea why this might be failing?