Indeed - First, Try to discount client side issues - Try different browser, check proxy settings (ensire site is being accessed directly), endure that whatever endpoint protection is on the clients you are using is not interfering., also disable add-ons in the browser.
Ensure the Intranet server is being accessed directly from the PC (that it is not a reflected connection through your firewall and back into the LAN, or through an internal router - this should not be the issue as long as they are on the same network segment and subnet, and no proxy is set on the browser).
Some other thoughts - Use the F12 tools in IE (or Firebug in Firefox) to profile the page request - is any particular element of the pages causing the issue?
Use a network monitoring tool on a client to see the response is coming back from the server.. Is it complete?
If you did not want to install a network monitoring tool you could used telnet. Let's say that you wanted to test if the page "MyPage.htm" is retrievable from host "intranet1" you could (within a command prompt) issue the command
telnet intranet1 80
Then in the telnet session type (carefully - backspace will not work)
GET /MyPage.htm HTTP/1.0
and hit enter again to add another a blank line
You should get the complete HTML of the requested page back - is it complete?
Alternatvely in the telnet window you could have used
GET /MyPage.htm HTTP/1.1
and again hit enter to add a blank line
That should have the same effect as the first command in simple implementations.
Hopefully one of these suggestions will help us understand the area in which the issue lies (or at least if the server really is returning incomplete responses)
Edited by x64, 01 October 2014 - 07:09 AM.