Home All Groups Group Topic Archive Search About

probable cause web based app timeout page does not display must refresh

Author
11 Sep 2006 12:23 AM
JDJ
I started a new job at a company with no in house IT department (has
outside consultants).

I'm not a network engineer but know more about computers than my
co-workers.

Mission critical app we all use all day long is a web based contact
management system.

I figure the app is actually running in house on the server, but maybe
not. I know we have a T1.

Anyhow, many times when we mouse on a link in the application we will
get an Internet Explorer white page with some error message (which I
will try to document tomorrow).

I figure we get the error because of a timeout of some sort.

A right click refresh or go back / go forward displays the needed
page.

What is the possible / probable causes for this error (as opposed to
just a slow loading of the page)?

--

"J. J."

Author
11 Sep 2006 3:47 PM
Chuck
On Sun, 10 Sep 2006 20:23:25 -0400, JDJ <jj@invalid.invalid> wrote:

Show quoteHide quote
>I started a new job at a company with no in house IT department (has
>outside consultants).
>
>I'm not a network engineer but know more about computers than my
>co-workers.
>
>Mission critical app we all use all day long is a web based contact
>management system.
>
>I figure the app is actually running in house on the server, but maybe
>not. I know we have a T1.
>
>Anyhow, many times when we mouse on a link in the application we will
>get an Internet Explorer white page with some error message (which I
>will try to document tomorrow).
>
>I figure we get the error because of a timeout of some sort.
>
>A right click refresh or go back / go forward displays the needed
>page.
>
>What is the possible / probable causes for this error (as opposed to
>just a slow loading of the page)?

If Internet Explorer is trying to access a distant server thru the Internet, I'd
suspect an MTU setting problem.  Or vaguely possible a DNS problem.
<http://nitecruzr.blogspot.com/2005/06/internet-connectivity-problems-caused.html>
http://nitecruzr.blogspot.com/2005/06/internet-connectivity-problems-caused.html
<http://nitecruzr.blogspot.com/2006/05/identifying-dns-problem-in-your.html>
http://nitecruzr.blogspot.com/2006/05/identifying-dns-problem-in-your.html

If this is an internal error, and you have no IT support, we may have to do some
intensive analysis here.  Read some of my articles, and start by providing
diagnostic details.
<http://nitecruzr.blogspot.com/2005/06/background-information-useful-in.html>
http://nitecruzr.blogspot.com/2005/06/background-information-useful-in.html
<http://nitecruzr.blogspot.com/2005/05/dealing-with-physical-network-problems.html>
http://nitecruzr.blogspot.com/2005/05/dealing-with-physical-network-problems.html

--
Cheers,
Chuck, MS-MVP [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My        email         is          AT         DOT
   actual       address    pchuck       mvps        org.