IIS Hosting a .Net Web Application

Hi,

I have Hosted a VB.Net application in IIS using Form Authentication and intermettinently we are facing (LDAP ) AD Authentication issue suddenly .While logging through web application got "Incorrect USername and Password" .If i restart the IIS, Issue was resolved.

If i change the IIS Idle Timeout and Session State settings will Solve this problem? Now IIS Idle Timeout set to 20 mins and Session State set to 30 mins.

We have checked AD logs and Server logs we couldnt find any cause. Please give some idea how to analyze this issue.

Review Application Code: Start by reviewing your VB.NET application's code responsible for LDAP or AD authentication. Ensure that there are no issues in your code that might cause intermittent authentication failures.
Check for Exceptions: Implement proper exception handling in your code to capture any exceptions that might occur during the authentication process. This can help you identify specific issues causing authentication failures.
Check for Connection Pooling: If your application is making LDAP or AD queries, ensure that you are using connection pooling appropriately. Connection leaks or improper management of connections can lead to authentication issues over time.
IIS Idle Timeout: Increasing the IIS Idle Timeout might help if the issue is related to the application pool or session timeouts. A longer idle timeout means the application pool remains active for a longer period, reducing the chance of timeout-related issues.
Session State Settings: Adjusting session state settings might help if the issue is related to sessions expiring too quickly. Increasing the session timeout can help maintain user sessions for a longer period.
Event Logs: Check both the Application and Security event logs on the server for any relevant error messages or warnings related to your application, IIS, or AD. Look for patterns or specific error messages that might provide clues.
LDAP or AD Server Logs: Examine the logs on your LDAP or AD server for any authentication failures or issues. These logs might provide more insight into what is happening during the intermittent failures.

1 Reply

Know the answer? Post it — somebody with the same question will find it here.

Tahir Ansari2y ago
Accepted answer
1. Review Application Code: Start by reviewing your VB.NET application's code responsible for LDAP or AD authentication. Ensure that there are no issues in your code that might cause intermittent authentication failures.
2. Check for Exceptions: Implement proper exception handling in your code to capture any exceptions that might occur during the authentication process. This can help you identify specific issues causing authentication failures.
3. Check for Connection Pooling: If your application is making LDAP or AD queries, ensure that you are using connection pooling appropriately. Connection leaks or improper management of connections can lead to authentication issues over time.
4. IIS Idle Timeout: Increasing the IIS Idle Timeout might help if the issue is related to the application pool or session timeouts. A longer idle timeout means the application pool remains active for a longer period, reducing the chance of timeout-related issues.
5. Session State Settings: Adjusting session state settings might help if the issue is related to sessions expiring too quickly. Increasing the session timeout can help maintain user sessions for a longer period.
6. Event Logs: Check both the Application and Security event logs on the server for any relevant error messages or warnings related to your application, IIS, or AD. Look for patterns or specific error messages that might provide clues.
7. LDAP or AD Server Logs: Examine the logs on your LDAP or AD server for any authentication failures or issues. These logs might provide more insight into what is happening during the intermittent failures.
0