Last post Apr 09, 2008 03:31 PM by Chaplain Doug
Dec 14, 2007 08:20 PM|Chaplain Doug|LINK
VWD 2008 Express. Visual Basic. ASP.Net 2.0. I am using AD authentication, authenticating in the AD of our domain. The server on which the web site is running is our domain controller. I have timed (in code) the time that expires between when the "Logging
In" event finishes and when the "Logged In" event begins. It takes approximately 26 seconds.
My question is what could be causing the authentication step to take so long? Also, I would like to know the sequence of events that take place in my Login.aspx page (it has a login control). What is the order of the Authenticate, databinding,
disposed, init, load, logged in, logging in, login error, prerender, and unload events during the login process? Thanks for any help.
By the way, once the authenticate is complete the web site moves quickly on SQL queries and the like. I would just like to fix whatever buggaboo is making the AD authentication take up to 30 seconds on an otherwise unburdened and fast server.
Jan 02, 2008 01:04 PM|Chaplain Doug|LINK
Tried the AD authentication on the server the other day and it took 4 minutes!! Someone mentioned a network "sniffer." How would I "sniff" the network to find out why it is taking so long to authenticate? By the way, I do not believe it is a network traffic
issue. Some part of the login process is hanging. How can I debug this?
Apr 09, 2008 03:31 PM|Chaplain Doug|LINK
No answers forthcoming after months. I am using Basic Authentication rather than Form Auth and the delay issue is not there. Question still has not been answered. But close it for now.