On Thursday, February 06, 2003 12:27 PM, Laurie Brown wrote:
NTL run transparent caches and proxies, and they are known to break. Try using another proxy, which will cause you to bypass the transparent NTL ones, and see what happens. This doc:
http://homepage.ntlworld.com/robin.d.h.walker/cmtips/trancache.html
...explains all.
Hi Laurie,
Thanks for your suggestion. I went to the webpage you suggested and tried the http://www.broadband-help.com/cm_diagnose.asp?init=1 link. It said:
Proxy IP 213.107.224.5 [WHOIS] Proxy Name(Raw) HTTP/1.1 ntl-site[D56BE005] (Traffic-Server/5.1.3-50227-50963-51463 [uSc ]) Proxy Name(R-DNS) cache2-colc.server.ntli.net
When I tried the http://www.all-nettools.com/pr.htm link it said: You came via: HTTP:/1.1 ntl-site[D56BE004] (Traffic-Server/5.1.3-50227-50963-5146 Remote Address: 213.107.224.4 Remote Host: 213.107.224.4
The "Remote Host IP Address" above is however different from the ISP assigned IP Address of my cable modem.
I think I need to stop and take some time to read through that http://homepage.ntlworld.com/robin.d.h.walker/cmtips/trancache.html webpage you suggested in order to suss out what the above information means, and how I should therefore adjust my Mozilla (or general Linux) settings. Unfortunately I have however just started getting an earful about spending too much time playing with my PC and why isn't lunch cooking yet, so must leave this for a while...
Ian.