IE Postbacks Fail after a few seconds when connecting to ASP.Net 4.0 on the local host

Question

I noticed a strange problem when developing a website project on a local hosting using ASP.Net 4.0, IIS 7.0 and IE8. Postprocessing does not work after the page has been idle for several seconds, such as 30 seconds or less. If I load the page, enter some data and immediately click the submit button, the postback will work fine, but if I let the page sit for no more than 30 seconds, the progress bar and the small pre-tension circle on the tab will end indefinitely and the answer never arises.

I can’t (or don’t know how) to use Wireshark on Windows to find out what is really happening on the network.

There is an exact copy of the website on the remote server, and there is no problem connecting to this site.

In addition, when connecting to a site on a local hosting using Firefox, the problem does not occur.

Finally, there is no problem connecting to the ASP 2.0 website on a local host using IE 8. The page can sit for an hour, and postback will still work.

Does anyone have any idea?

Answer 1

Oh wow. I think I finally found it. It seems to be AVG. I completely disabled AVG and the form post works. I turned it back on, and the submit / html 504 timeout message appears.

I narrowed it down by disabling the email scanner for incoming messages - this seems to be a criminal (I still have outgoing messages disabled, so this could also be a problem).

I suspect that automatic sending / receiving of Outlook automatically (every 30 seconds or so) starts the AVG email scanner, which for some reason prevents access of subsequent forms to the server, although Fiddler shows that it is correctly placed in the browser.

So glad I found! :)