<div>
Thank you. You hit the nail on the head. I hadn't run accross that KB article before, as a bonus it actually answers another issue that has been occurring in our environment. &nbsp;Very helpful answer.
</div>


<div>
<div class="content wysiwyg-content">
We have an application which runs within a web browser.<br />
Example: <a href="http://10.10.101.190/path/application.aspx" rel="ugc">http://10.10.101.190/path/application.aspx</a><br />
The initial screen displays fine, however any form based requests tend to go through the first time.<br />
Then, after that when clicking on &quot;Submit&quot; for further requests the form does not respond.<br />
If I close the web page and reopen it, the page still remains stagnate. <br />
However, if I wait, then later I may be able to proceed again.<br />
On the ISA 2006 server I have set the local network to not cache.<br />
I have set my browser to bypass the proxy for the local network.<br />
I still get this behavior.<br />
The only workaround I've found is to add the IP address in the exceptions list in the Advanced area of LAN settings within IE on my personal computer.<br />
<br />
Anyone know why ISA would couse this type of behavior? It seems related to a TTL setting but I have caching disabled for the local network within ISA. <br />
<br />
Are there additional settings I can try within ISA to resolve this issue?
</div>
</div>


We have an application which runs within a web browser.
Example: http://10.10.101.190/path/application.aspx
The initial screen displays fine, however any form based requests tend to go through the first time.
Then, after that when clicking on "Submit" for further requests the form does not respond.
If I close the web page and reopen it, the page still remains stagnate. 
However, if I wait, then later I may be able to proceed again.
On the ISA 2006 server I have set the local network to not cache.
I have set my browser to bypass the proxy for the local network.
I still get this behavior.
The only workaround I've found is to add the IP address in the exceptions list in the Advanced area of LAN settings within IE on my personal computer.

Anyone know why ISA would couse this type of behavior? It seems related to a TTL setting but I have caching disabled for the local network within ISA. 

Are there additional settings I can try within ISA to resolve this issue?

Thank you. You hit the nail on the head. I hadn&#39;t run accross that KB article before, as a bonus it actually answers another issue that has been occurring in our environment.  Very helpful answer.

Having problems with ISA 2006 and local network http requests by IP.

We have an application which runs within a web browser.
Example: http://10.10.101.190/path/application.aspx
The initial screen displays fine, however any form based requests tend to go through the first time.
Then, after that when clicking on &quot;Submit&quot; for further requests the form does not respond.
If I close the web page and reopen it, the page still remains stagnate. 
However, if I wait, then later I may be able to proceed again.
On the ISA 2006 server I have set the local network to not cache.
I have set my browser to bypass the proxy for the local network.
I still get this behavior.
The only workaround I&#39;ve found is to add the IP address in the exceptions list in the Advanced area of LAN settings within IE on my personal computer.

Anyone know why ISA would couse this type of behavior? It seems related to a TTL setting but I have caching disabled for the local network within ISA. 

Are there additional settings I can try within ISA to resolve this issue?

Microsoft Forefront, formerly known as Internet Security and Acceleration Server (ISA Server), is a network router, firewall, antivirus program, VPN server and web cache that runs on Windows servers. It includes identity management and protection systems, and discontinued systems for threat management and network protection, along with protection for Sharepoint and Exchange. The scope of discussions includes forward and reverse proxy, application and service publishing, virtual private networks (VPNs), outbound access rules, SSL certificates and network routing within either a single node or an highly-available array pairing.

Microsoft Forefront ISA Server

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).