if the clients got this error then i also unable to connect with ldapsearch.
28/Mar/2011:10:33:00 -0400] - => slapi_reslimit_get_integer_limit() conn=0xb023ffa8, handle=3
[28/Mar/2011:10:33:00 -0400] - <= slapi_reslimit_get_integer_limit() returning NO VALUE
[28/Mar/2011:10:33:00 -0400] - => slapi_reslimit_get_integer_limit() conn=0xb023fed8, handle=3
[28/Mar/2011:10:33:00 -0400] - <= slapi_reslimit_get_integer_limit() returning NO VALUE
[28/Mar/2011:10:33:00 -0400] - => slapi_reslimit_get_integer_limit() conn=0xb023fe08, handle=3
[28/Mar/2011:10:33:00 -0400] - <= slapi_reslimit_get_integer_limit() returning NO VALUE
[28/Mar/2011:10:33:00 -0400] - => slapi_reslimit_get_integer_limit() conn=0xb023fd38, handle=3
[28/Mar/2011:10:33:00 -0400] - <= slapi_reslimit_get_integer_limit() returning NO VALUE
[28/Mar/2011:10:33:00 -0400] - => slapi_reslimit_get_integer_limit() conn=0xb023fc68, handle=3
for the period. increased the files and restarted the srv, let me see what happens...
any other idea, advice what settings are needed for large amount of queries from 389ds ldap?