The page cannot be displayed - message received after being idle

[jason]

I just purchased a new computer (with Win XP), and installed my DSL
software on it. It seems to be working fine, most of the time.
Usually after I am idle for a time (i.e., over night), I cannot get
any connectivity through IE6. I get the error message 'The page
cannot be displayed' when I try to bring up any (valid) webpage. I
have found the only way to solve the problem is to reboot the
computer. I know that I have not lost connectivity to my ISP
completely, because my Instant Messaging program continues to run
uninterrupted.

I spoke with my ISP and they feel it is some type of system setting,
since I am not losing connectivity completely, and a reboot corrects
the problem.

Any ideas?

 

[Kenrick Fu]

Try this MS KB Article for help:
- Error Message:"Page Cannot be Displayed" When You Browse the Internet
http://support.microsoft.com/default.aspx?scid=kb;en-us;812336

 

[Robert Aldwinckle]

I have found the only way to solve the problem is to reboot the

computer.

Before rebooting try testing the interface e.g. using the
XP Net Diagnostics (Run... winmsd; then first item in Tools menu)

I would activate all Scanning options even though that causes the
scan to take longer. Also I think it would help to have previously
saved the same report created when the interface was working normally.
The generated report is XML and it nicely highlights failures but
unfortunately may not expand all the levels of detail that are available.
(Click on entries which have [+] in front of them to expand them.)

When this problem has been reported previously I have suggested
that perhaps an

ipconfig /release
and
ipconfig /renew
or
ipconfig /registerdns

would be sufficient to kick the interface back into life.
(E.g. try the latter when it appears that only your DNS is the problem.
Your mention that msmsg is still active could be an indication of that.
E.g. netstat -an may be showing a connection which existed prior
to the problem and which therefore does not require any more resolution.)
So far nobody has given me any feedback about either idea
so perhaps a diagnostic driven approach is better.

Hmm... I just poked around in the Network Connections Control Panel
applet and noticed that the Network Bridge component has an intriguing
item in its Network Tasks menu called "Repair this connection".
The XP Help (Win-F1,repair connection) has an item which sounds like
it would be doing the same sort of thing that my ipconfig commands
would be doing but perhaps using the menu item would be a preferred
approach.

BTW You are probably posting in the wrong newsgroup.
I imagine that a newsgroup which specializes in networking for XP
may have more proven suggestions, including if necessary steps for
restarting the TCP/IP process. FWIW I would be confident only that
something may be possible to restart the interface but in order to find out
what that is you would have to diagnose the problem and even after that
the resolution could turn out to be more effort than just rebooting.
E.g. stopping and restarting the TCP/IP process might cause a cascade
of failures in other processes and services.


Good luck

Robert Aldwinckle