KB867801 Page 2

[Nobody Special]

I had been having trouble with Internet Explorer
connecting to anything after the latest Microsoft Update
(KB867801), so I kept doing System Restore to the pre-
867801 configuration. This morning, however, I noticed
that I had a similar situation with my old configuration
too. That is, it acted as though it wasn't going to
connect to anything. After several minutes of trying
various links, it finally connected. Hmmm. Very interesing
says I. Wonder if it would behave in the same way with the
new update installed. So I re-installed the 867801 update
again. This time I allowed several minutes and attempted a
number of favorite links, when again, it connected.
So, apparently the delay problem wasn't caused by anything
867801 did to my system. It's got to be something else.
But what? Not a virus or trojan (unless my Avast!
antivirus doesn't know about it yet), not spyware (several
anti-spyware programs [including an online one] didn't
find anything), so what do you think is causing this
initial delay in connecting to the Internet after a
reboot? Once it's gone through this 'initialization', I
can leave IE, and after five minutes or so reconnect again
almost instantly (I'm on cable). It's only after a reboot
that the problem occurs. Anyone heard of this problem
before? Can I fix it? or do I just have to live with it?

 

[WinGuy]

I had been having trouble with Internet Explorer
connecting to anything after the latest Microsoft Update
(KB867801), so I kept doing System Restore to the pre-
867801 configuration. This morning, however, I noticed
that I had a similar situation with my old configuration
too. That is, it acted as though it wasn't going to
connect to anything. After several minutes of trying
various links, it finally connected. Hmmm. Very interesing
says I. Wonder if it would behave in the same way with the
new update installed. So I re-installed the 867801 update
again. This time I allowed several minutes and attempted a
number of favorite links, when again, it connected.
So, apparently the delay problem wasn't caused by anything
867801 did to my system. It's got to be something else.
But what? Not a virus or trojan (unless my Avast!
antivirus doesn't know about it yet), not spyware (several
anti-spyware programs [including an online one] didn't
find anything), so what do you think is causing this
initial delay in connecting to the Internet after a
reboot? Once it's gone through this 'initialization', I
can leave IE, and after five minutes or so reconnect again
almost instantly (I'm on cable). It's only after a reboot
that the problem occurs. Anyone heard of this problem
before? Can I fix it? or do I just have to live with it?

Just a guess, not at all knowing how you connect to networks, but ...
Sometimes the "Automatically detect settings" option being selected that can
cause delays like that (IE/Tools | Internet Options | Connections Tab | LAN
Settings button). You might want that selected if sometimes you use ethernet
and sometimes you use dialup (such as with a notebook/laptop or if using a
multiple ethernet adapter machine), but if you're only on a LAN or a
broadband connection (ethernet) then network things usually initialize
faster if you have that option disabled. Initialization problems with DHCP
or DNS can cause delays. Maybe changing the order of DNS entries provided by
your ISP (if manually assigned) might help.

 

[Nobody Special]

Always connected cable modem so I have that setting de-
selected. DNS entries are automatically assigned. Thanks
for the input. Once connected I have a nice 3850kbps
connection. Not too shabby. I can live with the delay if
it isn't indicative of a problem that's going to
eventually jump up and bite me.

-----Original Message-----

I had been having trouble with Internet Explorer
connecting to anything after the latest Microsoft Update
(KB867801), so I kept doing System Restore to the pre-
867801 configuration. This morning, however, I noticed
that I had a similar situation with my old configuration
too. That is, it acted as though it wasn't going to
connect to anything. After several minutes of trying
various links, it finally connected. Hmmm. Very interesing
says I. Wonder if it would behave in the same way with the
new update installed. So I re-installed the 867801 update
again. This time I allowed several minutes and attempted a
number of favorite links, when again, it connected.
So, apparently the delay problem wasn't caused by anything
867801 did to my system. It's got to be something else.
But what? Not a virus or trojan (unless my Avast!
antivirus doesn't know about it yet), not spyware (several
anti-spyware programs [including an online one] didn't
find anything), so what do you think is causing this
initial delay in connecting to the Internet after a
reboot? Once it's gone through this 'initialization', I
can leave IE, and after five minutes or so reconnect again
almost instantly (I'm on cable). It's only after a reboot
that the problem occurs. Anyone heard of this problem
before? Can I fix it? or do I just have to live with it?

Just a guess, not at all knowing how you connect to networks, but ...
Sometimes the "Automatically detect settings" option being selected that can
cause delays like that (IE/Tools | Internet Options | Connections Tab | LAN
Settings button). You might want that selected if sometimes you use ethernet
and sometimes you use dialup (such as with a notebook/laptop or if using a
multiple ethernet adapter machine), but if you're only on a LAN or a
broadband connection (ethernet) then network things usually initialize
faster if you have that option disabled. Initialization problems with DHCP
or DNS can cause delays. Maybe changing the order of DNS entries provided by
your ISP (if manually assigned) might help.



.

 

[WinGuy]

That is good, I just get a consistent 1.31 down and 331 up; but I'm ADSL.
You could try an experiment. Instead of launching IE, go to a cmd box and
try a ping of yahoo.com and after that launch IE and see if it still has the
same initial delay problem. I'm suspecting it won't then exhibit that delay,
which would probably mean it's some sort of networking initializing (perhaps
with the ISP, and that initialization delay might be on the ISP end instead
of on yours).
http://www.microsoft.com/technet/security/bulletin/MS04-025.mspx
That link explains the patches, and a couple of caveats if you'd gotten any
hotfixes before that update. It does seem odd that you didn't have the
problem before the update though and that's suspicious, but I've no more
ideas unless you're SP2 (if so, you should ask in the appropriate SP2
newsgroup since it's still not yet an official release). Nothing weird in
the Event Viewer or Device Masnager?

 

[Nobody Special]

Strange. I tried the experiment. I'm getting 'general
failure' for both ping and tracert, yet command line ftp
is connecting to sites just fine. Actually, my IE6 is
identified as sp2, but I haven't a clue as to which update
dis that. Help >About Internet Explorer shows the version
as
6.0.2800.1106.xpsp2.030422-1633
Yeah, that's suspicious alright. Thanks for your thoughts.

 

[Nobody Special]

I went over to the sp2 newsgroup and took a look. Seems
there's lots of people over there having fits over this
one. I've installed seven or so quickfixes since sp1 and
I'm thinking perhaps I'd better uninstall this puppy until
things shake out a tad more.

 

[dwicker]

I went over to the sp2 newsgroup and took a look. Seems
there's lots of people over there having fits over this
one. I've installed seven or so quickfixes since sp1 and
I'm thinking perhaps I'd better uninstall this puppy until
things shake out a tad more.

I installed it 3 days ago
when I booted up the following morning, all my network settings were
hosed
couldnt connect to the internet, get mail, ping etc etc
tried a restore that didnt work

called my isp, ntl, who were very helpful
they got me to remove tcpip etc and reboot and add services etc
now working fine, but.....

my wife's pc along the corridor, which is w2000 and is networked to
mine, which has the cable modem connected etc, cant access the
internet or get email either
am going to investigate tomorrow

regards

David M Wicker