ASP.NET Authentication To LDAp

We have a web site that we have moved to LDAP authentication. But we are getting many "server not available" LDAP errors, even though the LDAP server remains in service. Do I need to worry about multiple users, each in their own thread causing concurrent authentication requests to the LDAP server and or causing too much authentication traffic for the LDAP server?. Does an (OSI) application accept 开发者_如何学Pythonmultiple connections on the same incoming port at the same time or does it have to process them sequentially? Does it accept multiple connections from the same client (my web server) at the same time? If either of these are concerns, how do I architect my solution to overcome them? Should I be creating an single authentication object that is attached to the application object? Or is it o.k. to create it in each individual session/thread?

The FirstClass email system can provide LDAP services on port 389 out the 'front' of the application, and out the back, it can retrieve data from a different LDAP server.

What I would suggest is find out if there is a back end LDAP server and ask for permission to use that directly instead of proxying through FirstClass.

Man its been a while since I last saw FirstClass! Good to see they are still around!