Well, that's working.
Mar. 25th, 2002 07:38 pmSo it is NTL's Evil Proxies after all.
I'll probably whine at them next time I give them a call, but for the moment the web client works. I did, as promised, consult my good friend James G, and he said that he'd sorted it by just telling his browser which of their proxies to use, instead of letting them assign him the duff one that'd been getting in the way.
In my case, that's sticking the IP number of the working machine (he suggested 62.253.128.4 port 8080) into the proxies slot, under preferences in the usual way, and it does indeed seem to have done the trick. So you're not spared my inane warblings any more, I'm afraid.
Just having checked, LogJam has a space for choosing a proxy, too, so I seem to be sorted. Up until the netweork infrastructure finds another entertaining way to fail, anyway.
I'll probably whine at them next time I give them a call, but for the moment the web client works. I did, as promised, consult my good friend James G, and he said that he'd sorted it by just telling his browser which of their proxies to use, instead of letting them assign him the duff one that'd been getting in the way.
In my case, that's sticking the IP number of the working machine (he suggested 62.253.128.4 port 8080) into the proxies slot, under preferences in the usual way, and it does indeed seem to have done the trick. So you're not spared my inane warblings any more, I'm afraid.
Just having checked, LogJam has a space for choosing a proxy, too, so I seem to be sorted. Up until the netweork infrastructure finds another entertaining way to fail, anyway.