Detecting Proxy Settings
 

Phoned NTL today to request a new STB or modem so that we can claim our free upgrade to 2mb. Our new STB will be with us shortly but the nice lady on the helpdesk suggested we may as well try to reboot our Pace box just in case it will run with 2mb ....... and, shock horror, it did !!!

So, got 2mb, very nice but ........ one annoying problem.

When first entering IE6, my home page (Google) takes about 15 seconds to load and the message "Detecting Proxy Settings" sits in the bottom left corner. Once it has loaded, surfing is just fine.

I've looked at the connections tab in IE6 options and nothing is flagged ...... I even flagged them and then unflagged them just in case but no change.

I've not changed anything on the PC other than, when rebooting after the upgrade, I had to go through the online NTL setup procedure where it asks for your PID/password and then tells you to name your PC as it has none registered to your login (not sure why !!!).

Anybody know how to get rid of this problem ?

PS: The PC drives a wireless network via a router but has a direct bypass cable in so that shouldn't be causing a problem.

Re: Detecting Proxy Settings
 

Might be that your local proxies are being worked on during the upgrade work, you could try specifying a proxy just in case.

Re: Detecting Proxy Settings
 

Go into Internet Settings and make sure the box to "Automatically Detect Proxy Settings" or whatever it says in unchecked

Re: Detecting Proxy Settings
 

Thanks but I've already stated that they are all unchecked !!!

Re: Detecting Proxy Settings
 

Turned out to be the auto-detection in the LAN Settings that was flagged and that was causing the problem. Now unflagged and all is well !

Thanks for your help.

Re: Detecting Proxy Settings
 

So does the Pace really do 2Mb, or was it some sort of spurious indication?

Strange if it can, as it was origianally ruled out of 1.5Mb.

Re: Detecting Proxy Settings
 

Well it is definitely a PACE and an online speedcheck threw up 1.9MB as a result so I figured it must have worked !