Why Does IE6 & OE6 Take Ages To Load When First Connecting To The Internet!

R

Ripperoo

Hi Guys

This happens every time I connect to the internet using IE6 or OE6.

I'm running XP Pro (all the latest patches/fixes) and have a 56K dial up
connection (with latest driver). My browser homepage is set to "Google", so
it should load pretty damn fast, but for some reason it doesn't!

It takes so long to load that usually end up closing the damn IE window in
frustration.

After a while I can then open an IE window and "Google" will load almost
instantly and all subsequent pages load fine.

Similar sort of thing happens in OE6 too. After a while that's OK too.

It seems like there's something hogging the available bandwith initially
"when first connecting to the internet). I thought at first it may may have
been "Messenger" working in the background, but the problem is still here
after uninstalling it.

I've also used a number of AV, AT and Adware/Spyware tools to check for
parasites but everything is clean.

Any ideas guys.

It's not a major problem, but more of a PITA which I could do without.

Many thanks in advance.
 
F

Frank Saunders, MS-MVP

Ripperoo said:
Hi Guys

This happens every time I connect to the internet using IE6 or OE6.

I'm running XP Pro (all the latest patches/fixes) and have a 56K dial
up connection (with latest driver). My browser homepage is set to
"Google", so it should load pretty damn fast, but for some reason it
doesn't!

It takes so long to load that usually end up closing the damn IE
window in frustration.

After a while I can then open an IE window and "Google" will load
almost instantly and all subsequent pages load fine.

Similar sort of thing happens in OE6 too. After a while that's OK
too.

It seems like there's something hogging the available bandwith
initially "when first connecting to the internet). I thought at
first it may may have been "Messenger" working in the background, but
the problem is still here after uninstalling it.

I've also used a number of AV, AT and Adware/Spyware tools to check
for parasites but everything is clean.

Any ideas guys.

It's not a major problem, but more of a PITA which I could do without.

Many thanks in advance.

For users on WinXP, when they remove windows messenger or just disable it
from starting up automatically they experience a great slow down when
launching Outlook express. Users who experience such a slow down will find a
error in the system error log saying The server
{FB7199AB-79BF-11D2-8D94-0000F875C541} did not register with DCOM within the
required timeout. The solution this problem is quite simple. Just Open up
Regedit and search for the string {FB7199AB-79BF-11D2-8D94-0000F875C541} and
modify the keys InProc32 (or InProcServer32) and LocalServer32 default key
to a empty string. After a reboot, Outlook Express will start up as quickly
as possible. See:
http://www.tweakxp.com/tweakxp/display.asp?id=108

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

Ripperoo

I've just altered the registry settings as mentioned and I'll let you know
how IE6 & OE6 react once I reboot!

Well, I rebooted after the changes to the registry and the problem is still
there. :(

What I did notice while I had "Task Manager" open was that while my modem
dialed my ISP the "SVHOST.EXE" - "NETWORK SERVICE" entry stayed at 0 in the
CPU column. When the IE did connect to the Internet, this figure shot up to
99 and stayed at that figure until the page loaded fully after which it
dropped back to zero.

Is this normal behaviour?

If the above is normal, any other suggestions?
 
R

Ripperoo

As it turns out, the problem wasn't some dodgy program hogging the CPU when initialy connected to the internet after all.

It was actually the Windows XP "DNS Client" (which is listed under "Services" and which can be found by clicking Start>Run>services.msc).

It seems the "DNS Client" caches DNS names for the PC and if disabled, the system will go "upstream". I assume the term "upstream" means that the system tries to resolve DNS names directly via the internet instead of using the the cache.

One site I visited recommended that the "DNS Client" should be diabled anyway as it's not really needed. You can see the details here:
http://www.theeldergeek.com/dns_client.htm

Well, it appears to have solved my problem AFAICT, so it seems I didn't have anything dodgy on my system after all.

Thanks for your help guys!
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top