• Welcome to Tux Reports: Where Penguins Fly. We hope you find the topics varied, interesting, and worthy of your time. Please become a member and join in the discussions.

IE8 & connection problems with internal network web app

A

ACQ

Flightless Bird
I am testing our network web apps with IE8, and only one is coming up with
"Cannot display the webpage" message, and a diagnosis tool. The server is
listed in our DNS server, I have 2 other apps on that server that don't give
me this error. When I click "Diagnose Connection Problems", the web app
suddenly works, even though I have the diagnosis tool still running and not
having done anything.

Environment: WinXP SP2, IE8, group policy manages some IE settings, web app
written in asp.net (unsure of version yet, can't reach developer to confirm).

Having users click the "Diagnose" button is not an option, and going back to
IE7 is not an option, either. Since our corporation is a Microsoft shop,
using a different browser is not an option, either.

Thanks ahead of time for the help!

ACQ
 
R

rob^_^

Flightless Bird
Hi,

Tools>Internet Options - Security Tab, Intranet Zone

Check your Intranet zone settings and Sites. Check that you do not also have
sites listed in both your Intranet and Trusted sites zone.

You troublesome page probably contains mixed content? You may have to add
the domains of external content to your trusted sites zone.

(Google Adsence?) Also check that you do not have InPrivate filtering turned
on.

Regards.

"ACQ" <ACQ@discussions.microsoft.com> wrote in message
news:8E606826-F49F-4ABC-BB13-B30FE0045B32@microsoft.com...
> I am testing our network web apps with IE8, and only one is coming up with
> "Cannot display the webpage" message, and a diagnosis tool. The server is
> listed in our DNS server, I have 2 other apps on that server that don't
> give
> me this error. When I click "Diagnose Connection Problems", the web app
> suddenly works, even though I have the diagnosis tool still running and
> not
> having done anything.
>
> Environment: WinXP SP2, IE8, group policy manages some IE settings, web
> app
> written in asp.net (unsure of version yet, can't reach developer to
> confirm).
>
> Having users click the "Diagnose" button is not an option, and going back
> to
> IE7 is not an option, either. Since our corporation is a Microsoft shop,
> using a different browser is not an option, either.
>
> Thanks ahead of time for the help!
>
> ACQ
>
 
R

rob^_^

Flightless Bird
Also

Download fiddler (http://www.fiddlertool.com ) and check that all your
resource files (external css and js) have completed downloading.

If your page is not being cached, the marshalling of your external resources
may be taking too long.

Regards.

"ACQ" <ACQ@discussions.microsoft.com> wrote in message
news:8E606826-F49F-4ABC-BB13-B30FE0045B32@microsoft.com...
> I am testing our network web apps with IE8, and only one is coming up with
> "Cannot display the webpage" message, and a diagnosis tool. The server is
> listed in our DNS server, I have 2 other apps on that server that don't
> give
> me this error. When I click "Diagnose Connection Problems", the web app
> suddenly works, even though I have the diagnosis tool still running and
> not
> having done anything.
>
> Environment: WinXP SP2, IE8, group policy manages some IE settings, web
> app
> written in asp.net (unsure of version yet, can't reach developer to
> confirm).
>
> Having users click the "Diagnose" button is not an option, and going back
> to
> IE7 is not an option, either. Since our corporation is a Microsoft shop,
> using a different browser is not an option, either.
>
> Thanks ahead of time for the help!
>
> ACQ
>
 
R

Robert Aldwinckle

Flightless Bird
"ACQ" <ACQ@discussions.microsoft.com> wrote in message
news:8E606826-F49F-4ABC-BB13-B30FE0045B32@microsoft.com...
> I am testing our network web apps with IE8, and only one is coming up with
> "Cannot display the webpage" message, and a diagnosis tool. The server is
> listed in our DNS server, I have 2 other apps on that server that don't
> give
> me this error. When I click "Diagnose Connection Problems", the web app
> suddenly works, even though I have the diagnosis tool still running and
> not
> having done anything.



Yes you did do something. You created a connection using a diagnosis tool.
So you need to look at the connectivity from an even lower level than HTTP.
Fiddler won't be enough to see how it works. Use something like WireShark.
The sort of thing you might see, depending on the connection type, is PPPoE
having to create an Internet connection before your DNS will work but IE
being made to think that it is using a LAN connection so no provision for
delays to allow such setup before your DNS is usable. Etc.


>
> Environment: WinXP SP2, IE8, group policy manages some IE settings, web
> app
> written in asp.net (unsure of version yet, can't reach developer to
> confirm).
>
> Having users click the "Diagnose" button is not an option, and going back
> to
> IE7 is not an option, either. Since our corporation is a Microsoft shop,
> using a different browser is not an option, either.
>
> Thanks ahead of time for the help!
>
> ACQ
 
A

ACQ

Flightless Bird
Thanks for the ideas. Here's an update, which is the part I don't understand:

After 4 hours of testing yesterday, which included just opening the web
app's site, I no longer get the connectivity error message. It's almost like
IE8 was in "learn mode", but I couldn't find anything that looked like that
kind of feature.

So, what I'm wondering is, is there a way to make IE8 recognize the site as
valid? Are trusted & intranet site zones the options I should change to not
have this message appear?

I'll definitely check out the InPrivate filtering option, but not having the
problem reproduce itself on my test machine will make this goose hunt that
much more goosey. :p

Thanks guys! I'll keep you posted!


"Robert Aldwinckle" wrote:

> "ACQ" <ACQ@discussions.microsoft.com> wrote in message
> news:8E606826-F49F-4ABC-BB13-B30FE0045B32@microsoft.com...
> > I am testing our network web apps with IE8, and only one is coming up with
> > "Cannot display the webpage" message, and a diagnosis tool. The server is
> > listed in our DNS server, I have 2 other apps on that server that don't
> > give
> > me this error. When I click "Diagnose Connection Problems", the web app
> > suddenly works, even though I have the diagnosis tool still running and
> > not
> > having done anything.

>
>
> Yes you did do something. You created a connection using a diagnosis tool.
> So you need to look at the connectivity from an even lower level than HTTP.
> Fiddler won't be enough to see how it works. Use something like WireShark.
> The sort of thing you might see, depending on the connection type, is PPPoE
> having to create an Internet connection before your DNS will work but IE
> being made to think that it is using a LAN connection so no provision for
> delays to allow such setup before your DNS is usable. Etc.
>
>
> >
> > Environment: WinXP SP2, IE8, group policy manages some IE settings, web
> > app
> > written in asp.net (unsure of version yet, can't reach developer to
> > confirm).
> >
> > Having users click the "Diagnose" button is not an option, and going back
> > to
> > IE7 is not an option, either. Since our corporation is a Microsoft shop,
> > using a different browser is not an option, either.
> >
> > Thanks ahead of time for the help!
> >
> > ACQ

>
> .
>
 
R

Robert Aldwinckle

Flightless Bird
"ACQ" <ACQ@discussions.microsoft.com> wrote in message
news:1DE7A20B-BE7F-4341-8989-1748F4DE07B0@microsoft.com...
> Thanks for the ideas. Here's an update, which is the part I don't
> understand:
>
> After 4 hours of testing yesterday, which included just opening the web
> app's site, I no longer get the connectivity error message. It's almost
> like IE8 was in "learn mode", but I couldn't find anything that looked
> like that kind of feature.
>


> So, what I'm wondering is, is there a way to make IE8 recognize the site
> as valid? Are trusted & intranet site zones the options I should change
> to not have this message appear?



If it's a DNS issue you could add entries to your HOSTS file.
Also, supposedly IE has its own temporary DNS cache,
so as long as you don't close a complete instance of it,
you may find it reconnecting better because of that.
And depending on where the DNS records originate
and how your ISP's DNS server caches them you might
get some performance benefit that way too.


Robert
---
 
Top