ASP.Net Browser Compatibility

Question

If I use IE to connect to my ASP.Net site and let the browser stand idle for a minute or so, and then try to click on the new element, the link, whatever it is, IE looks like it is trying to load, but never does anything.

If I connect to the site using Chrome and do the same, Chrome pulls up the next item as expected without delay. I tried to make changes to web.config for sessionState and httpRuntime, in ASP and pool settings in IIS, and I can not do anything to fix the problem in IE.

Is there another option somewhere, possibly on Windows, to fix IE, since this seems like a browser-specific issue and not related to an ASP or IIS site? I'm running out of ideas, and most users will use IE, not Chrome, so this is actually not a problem that I can ignore.

Here is my web.config file if this helps:

<?xml version="1.0"?> <!-- For more information on how to configure your ASP.NET application, please visit http://go.microsoft.com/fwlink/?LinkId=169433 --> <configuration> <connectionStrings> <add name="ApplicationServices" connectionString="data source=.\SQLEXPRESS;Integrated Security=SSPI;AttachDBFilename=|DataDirectory|\aspnetdb.mdf;User Instance=true" providerName="System.Data.SqlClient"/> <add name="TaskSystemConnectionString" connectionString="Data Source=REPORTSERVER;Initial Catalog=TaskSystem;Integrated Security=True" providerName="System.Data.SqlClient"/> </connectionStrings> <system.web> <sessionState timeout="3600"/> <httpRuntime executionTimeout="3600" maxRequestLength="2000000"/> <compilation debug="true" targetFramework="4.0"/> <authentication mode="Windows" /> <customErrors mode="Off"/> <membership> <providers> <clear/> <add name="AspNetSqlMembershipProvider" type="System.Web.Security.SqlMembershipProvider" connectionStringName="ApplicationServices" enablePasswordRetrieval="false" enablePasswordReset="true" requiresQuestionAndAnswer="false" requiresUniqueEmail="false" maxInvalidPasswordAttempts="5" minRequiredPasswordLength="6" minRequiredNonalphanumericCharacters="0" passwordAttemptWindow="10" applicationName="/"/> </providers> </membership> <profile> <providers> <clear/> <add name="AspNetSqlProfileProvider" type="System.Web.Profile.SqlProfileProvider" connectionStringName="ApplicationServices" applicationName="/"/> </providers> </profile> <roleManager enabled="false"> <providers> <clear/> <add name="AspNetSqlRoleProvider" type="System.Web.Security.SqlRoleProvider" connectionStringName="ApplicationServices" applicationName="/"/> <add name="AspNetWindowsTokenRoleProvider" type="System.Web.Security.WindowsTokenRoleProvider" applicationName="/"/> </providers> </roleManager> <pages controlRenderingCompatibilityVersion="3.5" clientIDMode="AutoID" validateRequest="false"/> </system.web> <system.webServer> <defaultDocument> <files> <add value="Home.aspx"/> </files> </defaultDocument> <modules runAllManagedModulesForAllRequests="true"/> 

Answer 1

So ... after continuing research and driving, I found a Microsoft article that fixed the problem. It seems that these special people at Microsoft decided that one timeout was a suitable default ... http://support.microsoft.com/kb/813827 . After I added the two necessary registry entries for KeepAliveTimeout and ServerInfoTimeout, the problem disappeared.

Answer 2

Maybe something has to do with database permissions. Did you try to specify the SQL login in your connection strings? Can the account running IIS access these databases?

Also check your IIS settings to make sure authentication mode = Windows.

I am having problems with Windows authentication when I am not using IE. For example, Chrome does not pass the user ID, and I have to enter my credentials every time I access the intranet.