Hi

this morning I've tried to rollout my new Intranet DNN portal based on the AD authentication with Single Sign On functionality.
My portal is based on 4 webservers running DNN 4.7 in a webfarm (broadcast mode).

Looking inside the configuratiion I see the DotNetNuke.Authentication.ActiveDirectory.dll is version 4.6.0.0, frankly speaking I'm not able to find out which version of provider I'm using....

The facts, this morning everythng was running fine and up to 900 - 950 users I had no problems. Around at 1000 the authentication was quite "frozen" users already authenticated had no problem to navigate and use the site, but none was able to login again.

For unauthenticated users, I placed in the navigation menu a button calles "Portal Login" to be pressed if for any reason they should not get the Single sign on operational (link to windowssignin.aspx).

IIS reset on the servers fixed the problem, up to 2000 users. Please note I say 2000 ffrom the number of the accounts automatically created in DNN. many of them after the login went out from the my portal.

At the 2009 new user created, I had again a frozen authentication and at that time I rolled back to the previous version of our portal.

This is my question, in a Microsoft documentation http://support.microsoft.com/kb/315071/en-us it's written that MaxPageSize, that on the AD controller is set to 1000. 1000 again, should not this the possible reason of my today issue?

The rison of my suspect is based on the fact that when users not authenticated tried to click on the login button spent minutes waiting to be authenticated and after few minutes, they got the .NET error page on their browsers.

I've not Kerberos operational on my servers, I don't know if this may help, but before retry again with my users, I'd like to have a couple of suggestions/ideas on how sort this problem out.

Any suggestion from anyone?

Thanks in advance for your support.

Kind regards

Hi Mike

I'm back after I've identified the reason of my issue.

I supposed, at the beginning, that the problem was in the number of users, now after some tests I discovered that if I unselect  the checkbox "Syncronize Roles" I can have quite 200 concurrent users on the same box without any issue.

If I've this Checkbox selected, CPU usage goes quite to 100% (and stays at 100% constantly) and I cannot authenticate more than 30 users without getting a long list of .NET errors on windows (2003) event viewer application log. Looks like that there is a lot of requests to the SQL server (2000) that cannot be satisfied...

I'm thinking to find a way to "pre-authenticate users" if this is the only solution possible.
Are you aware of a tool already available that it's able to do this

Diggering inside the Authenticatiion forum I saw that sometinme you suggest to uncomment  identity impersonate="true" section. I don't know if this may help....

For sure with low number of users connected to the server I hah the sync roles operational without any issue. For sure it's the workload based on the hi number of users...

Thanks for your suggestions and support  

Kind regards

Daniele