Have you looked in the Tomcat logs? Frequently they will contain information on LDAP related problems.

Here's what I would do next
Install Wireshark on the Jazz server
See this tecnhnote for instructions on using it.

Start Wireshark as described in that technote.
Attempt to log in one or two times as a user in the LDAP registry.
Stop the capture
Type ldap into the filter box on the top left and click apply
This should be all the traffic to your ldap server and might give a clue as to what the problem is.

Check your teamserver.properties files to make sure none of them have been changed recently.
The top 2 lines in the file should indicate when it was changed and by who if it was done through RTC.
Otherwise you will need to rely on the time stamps.

You can also verify that the LDAP settings look correct in those files

Check the tomcat server.xml file in the ...\server\tomcat\conf directory for the  className="org.apache.catalina.realm.JNDIRealm  element.
If it is there make sure the values look ok.
(not to be confused with the className="com.ibm.team.repository.localgroups.realm.LocalMappingJNDIRealm" element)

I don't think you can re-enable the ADMIN account once you switch to LDAP but you can give it a try by setting com.ibm.team.repository.ws.allow.admin.access=true in the jts teamserver.properties file and restarting the server.

Hi Jagdish,

You might want to try disable LDAP from teamserver.properties file and revert back the to tomcat-user.xml in server/tomcat/conf.