IE 6 SP1 only works after a refresh

[Guest]

Windows 2000 IE 6 SP1
The 1st time an IE session is open the page will time out., but if you hit
refresh the page loades and you con continue to sure. If you close the
current session and reopen a new session it will time out until you refresh
again.

have Ihave removed and reinstalled IE installed windows sp 4, updated the
nic
drivers, dumped cache, removed the sygate firewall, ran addware,
manually checked the registry for spy ware, set I.E. automatically check
for new pages on EVERY visit.
This happens on both the DSL line and my corporate LAN

Site note Netscape is not having this problem.

 

[Frank Saunders, MS-MVP IE/OE]

Windows 2000 IE 6 SP1
The 1st time an IE session is open the page will time out., but if
you hit refresh the page loades and you con continue to sure. If you
close the current session and reopen a new session it will time out
until you refresh again.

have Ihave removed and reinstalled IE installed windows sp 4,
updated the nic
drivers, dumped cache, removed the sygate firewall, ran addware,
manually checked the registry for spy ware, set I.E. automatically
check for new pages on EVERY visit.
This happens on both the DSL line and my corporate LAN

Site note Netscape is not having this problem.

Click Start, and then click Run.
In the Open box, type:

regsvr32 urlmon.dll

--
Frank Saunders, MS-MVP, IE/OE
Please respond in Newsgroup only. Do not send email
http://www.fjsmjs.com
Protect your PC
http://www.microsoft.com/security/protect/

 

[Guest]

I tried that one, after reading through a bunch on these posts, but it didn't
work either. I re-imaged the machine, somethings just are not worth fighting
for hours over, but would still love to know what the casue was.

Thank you

 

[Robert Aldwinckle]

The 1st time an IE session is open the page will time out., but if
That sounds like spyware at work to me.
E.g. spyware tries to "phone home" for first connection attempt.
"Home" is either not listening or overloaded so timeout occurs.

To test the idea you could have done a packet trace which covered
the time of your "time out" symptoms, examined the requests
which went out, and then compared them with what you thought
should be happening.

It could also be the case that such a site does not have good
visibility in a DNS lookup and the delay doing that is what is
causing a problem symptom. Once you know what it is you
could try pre-finding the site manually using nslookup or putting
an override for it into your HOSTS file.

For either case it might be interesting to try an

ipconfig /displaydns

after your "timeout".


Since you are mostly interested in addresses instead of other data
you could try the NTx Port Reporter tool as a compromise to a full
packet trace

<title>KB837243 - Availability and description of the Port Reporter tool</title>


FYI

Robert Aldwinckle