ENW slow on home comp through IE

Status
Not open for further replies.
Quasqueton said:
I didn't do anything like this "manually". How would I find out if it was done "automatically"? If this problem was with all web sites, or with my IE at work, I'd figure it was my hardware/software. But this is only a problem on my home computer, through IE, and only on ENW. I figured something must have been updated/changed on this site.

Has me completely stymied.

Quasqueton


If you have automatic updates going you most likely have XP SP2 which has a pop-up blocker for IE. It has settings in Internet Options, Privacy tab at the bottom. I wouldn't think this would cause the problem, but you can check if it was installed or not.
 

log in or register to remove this ad

I've now checked the connection from 5 computers and have been unable to replicate the slowdown issue. The only help I can offer, as others already have, is the strong possibility that your computer has spyware or adware messing with the system.

You might want to post in the Computers forum on this.

At this point, I consider this report closed.
 

I've been trying to get in for an hour and a half, running Firefox on WinXP Pro. My work connection is a T1 line and the PC is Dell with 256 meg of ram and a 2.5 GHz processor. So it seems the bottleneck is "out there" somewhere.
 


IE 6 is teh broke-zors
However it runs very well on Firefox 1.0.3.

2600+ Athalon XP
512 Ram

@DMcal:

Try performing a trace route to enworld.

Start->Run->Cmd->"tracert www.enworld.org"
Without the brackets into the comand prompt.

I got 14 Hops and then 65.115.128.242 told me that the destination net was unreachable.
 

lonesoldier said:
IE 6 is teh broke-zors
However it runs very well on Firefox 1.0.3.

2600+ Athalon XP
512 Ram

@DMcal:

Try performing a trace route to enworld.

Start->Run->Cmd->"tracert www.enworld.org"
Without the brackets into the comand prompt.

I got 14 Hops and then 65.115.128.242 told me that the destination net was unreachable.


Routing problems aren't a problem I can fix on the server side. That's a problem for your ISP.
 


Since I switched to Firefox, I have had no problems. However, my first thought was "Spyware" and it remains, imho, a pretty likely cause.

My hat of IE knows no limit.
 

P-kitty has given me permission to start closing bug threads once the bug has been diagnosed. That would be the case with this one. If this continues though feel free to start up a new thread.

Diagnosis: Probable Spyware infection in Client.
Status: Closed.
 

Status
Not open for further replies.
Remove ads

Top