Not sure if this is an IE specific problem.

In the very early morning and very late at night, I am able to access
any web site, including yahoo, hotmail, google, etc.. During heavy
traffic hours, I am unable to access sites like Yahoo, hotmail and
many other frequently used sites. I am, however, able to connect to
AIM and other sites with no problem during those hours.
It's as though my browser is timing out too quickly if it has to wait
to connect to those busy sites.
I've done all the Ad-aware scans and Norton AV scans.
I was told it may be corrupt files and I should insert the Windows
2000 disc to see if it uploads, however I don't have that disc.
Does this problem sound like a browser problem, a Windows problem?
Thank you.
Becky

On Mon, 14 Feb 2005 03:35:56 GMT, Starlight
<(E-Mail Removed)> wrote:

>Not sure if this is an IE specific problem.
>
>In the very early morning and very late at night, I am able to access
>any web site, including yahoo, hotmail, google, etc.. During heavy
>traffic hours, I am unable to access sites like Yahoo, hotmail and
>many other frequently used sites. I am, however, able to connect to
>AIM and other sites with no problem during those hours.
>It's as though my browser is timing out too quickly if it has to wait
>to connect to those busy sites.

I should add to this that we have 3 other computers in this house, all
of us connected to a router, and this is the only computer that has
the problem. It will attempt to connect to the site, lag for awhile,
then show the cannot connect page.

On Mon, 14 Feb 2005 03:35:56 GMT, Starlight
<(E-Mail Removed)> wrote:

>Not sure if this is an IE specific problem.
>
>In the very early morning and very late at night, I am able to access
>any web site, including yahoo, hotmail, google, etc.. During heavy
>traffic hours, I am unable to access sites like Yahoo, hotmail and
>many other frequently used sites. I am, however, able to connect to
>AIM and other sites with no problem during those hours.
>It's as though my browser is timing out too quickly if it has to wait
>to connect to those busy sites.
>I've done all the Ad-aware scans and Norton AV scans.
>I was told it may be corrupt files and I should insert the Windows
>2000 disc to see if it uploads, however I don't have that disc.
>Does this problem sound like a browser problem, a Windows problem?
>Thank you.
>Becky

I tried something I read here:
~~~~~~~~~~~~~~~~~~~~~~
Make sure the following registry entry is not corrupt:
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet
Settings]
"User Agent"="Mozilla/4.0 (compatible; MSIE 6.0; Win32)"

Note: "Win32" = Windows 98\ME
Other versions = (compatible; MSIE 6.0; Windows NT 5.0

To check your "User Agent":
Paste the below into the Address Bar and view the output:

javascript:navigator.userAgent

[Example WinME output]
Mozilla/4.0 (compatible; MSIE 6.0; Windows 98; Win 9x 4.90)
~~~~~~~~~~~~~~~~~~~~~~~~~

MY RESULT is Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET
CLR 1.1.4322)
I'm not sure how to tell if the entry is corrupt.

"Starlight" <(E-Mail Removed)> wrote in message news:(E-Mail Removed)...
> On Mon, 14 Feb 2005 03:35:56 GMT, Starlight
> <(E-Mail Removed)> wrote:
>
>>Not sure if this is an IE specific problem.

It's not. Better help on a newsgroup which specializes in networking
for your OS. Be sure to include information about your hardware
especially your Internet link.

You have an *intermittent* problem so it can't be User-Agent
which would only cause a *consistent* problem at a *few* sites.

Have you contacted your ISP? Asked for a different connection?
E.g. if you get information via DHCP and you use Dial-up
try using an alternate number or try hanging up and reconnecting.
Otherwise NT5 users can use (in a command window):

ipconfig /registerdns

for a similar effect. Etc.


(More...)


>>
>>In the very early morning and very late at night, I am able to access
>>any web site, including yahoo, hotmail, google, etc.. During heavy
>>traffic hours, I am unable to access sites like Yahoo, hotmail and
>>many other frequently used sites. I am, however, able to connect to
>>AIM and other sites with no problem during those hours.
>>It's as though my browser is timing out too quickly if it has to wait
>>to connect to those busy sites.

I agree but when I tried to bring the idea up the only timeout values
I was pointed at had granularity of seconds. This problem needs
timeout values with much finer granularity. Also we don't know where
the timeout is: DNS or HTTP server? Is a caching server involved?
You really need some packet traces to refine your symptom description
to pursue this tack.


>>I've done all the Ad-aware scans and Norton AV scans.
>>I was told it may be corrupt files and I should insert the Windows
>>2000 disc to see if it uploads, however I don't have that disc.

Wrong analysis IMO but why don't you have a Windows 2000 CD?
You may need it if somebody tells you to reinstall networking,
or communication drivers, for example.


>>Does this problem sound like a browser problem, a Windows problem?

Have you tried a different browser? For DNS issues it sometimes seems
that tracert does more reliable lookups than ping does which in turn
seems better able to do its lookup than IE. Perhaps a different browser
can have a similar effect? Better timeout handling for downloading
data files could be even more likely I suspect.


>>Thank you.
>>Becky


Good luck

Robert Aldwinckle
---


>
> I tried something I read here:
> ~~~~~~~~~~~~~~~~~~~~~~
> Make sure the following registry entry is not corrupt:
> [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet
> Settings]
> "User Agent"="Mozilla/4.0 (compatible; MSIE 6.0; Win32)"
>
> Note: "Win32" = Windows 98\ME
> Other versions = (compatible; MSIE 6.0; Windows NT 5.0
>
> To check your "User Agent":
> Paste the below into the Address Bar and view the output:
>
> javascript:navigator.userAgent
>
> [Example WinME output]
> Mozilla/4.0 (compatible; MSIE 6.0; Windows 98; Win 9x 4.90)
> ~~~~~~~~~~~~~~~~~~~~~~~~~
>
> MY RESULT is Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET
> CLR 1.1.4322)
> I'm not sure how to tell if the entry is corrupt.

Looks fine for coming from IE6 running on Windows 2000 (aka NT50)