B
Bradley Walker
This is an issue I just started having after I reformatted WinXP SP2 this
weekend. After a clean format on my P4 box and after installing all of the
software I need, (i.e. - Office, IM's, email, etc) when I went to load
webpages in IE, instead of the near instant response of loading it from my
DSL line, it sat there for nearly a minute with the status bar showing
"Detecting Proxy Settings...".
Finally after 45-60 seconds it transfers the pages fast and everything is
loaded. Previously before the format IE was loading pages within a second
or two. Well I double checked my router, I double checked the DSL line, all
of that was OK. I decided to load up FireFox 1.0 and within the moment I
loaded it it had loaded the homepage within 2 seconds maximum. I even got
frustrated enough that I reformatted AGAIN and yet again the same problem
persisted. I do not have any sort of firewall software installed, nothing
installed that would inhibit the network drivers, protocol stack or
anything. Does anyone have ANY idea why IE is doing this when Firefox
isn't? Again this is on a clean machine.
Brad
weekend. After a clean format on my P4 box and after installing all of the
software I need, (i.e. - Office, IM's, email, etc) when I went to load
webpages in IE, instead of the near instant response of loading it from my
DSL line, it sat there for nearly a minute with the status bar showing
"Detecting Proxy Settings...".
Finally after 45-60 seconds it transfers the pages fast and everything is
loaded. Previously before the format IE was loading pages within a second
or two. Well I double checked my router, I double checked the DSL line, all
of that was OK. I decided to load up FireFox 1.0 and within the moment I
loaded it it had loaded the homepage within 2 seconds maximum. I even got
frustrated enough that I reformatted AGAIN and yet again the same problem
persisted. I do not have any sort of firewall software installed, nothing
installed that would inhibit the network drivers, protocol stack or
anything. Does anyone have ANY idea why IE is doing this when Firefox
isn't? Again this is on a clean machine.
Brad