On Saturday 18 January 2003 05:58 am, Vic Cross wrote: <Snipped> > Yes, it is. I think you're getting confused. <Good explanation snipped>
That would not be very hard... :) > None of this is your problem, however... > > The port that apt is trying to connect to (3128) gives me a clue. Check > to see that the environment variable http_proxy (might be uppercase, as in > HTTP_PROXY) is not set, or that web proxying has not otherwise been > enabled. 3128 is the port that the Squid web proxy uses by default, so > I'm guessing that somehow a HTTP proxy has been enabled. The error > message is a little misleading, but reflects normal operation when a proxy > is configured since the TCP connection is made to the proxy, not the real > web server. OK, checked that. No http_proxy or HTTP_PROXY defined in the environment. Any hints as to where else to look for proxying settings would be appreciated. > > It's as if "ftp" names resolve OK, but http does not. Can't figure this > > one out myself, that's why I'm asking for help here. > > A further hint that proxying is getting in the way. It's not that the > names are not resolving, it's just that FTP is not being proxied while > HTTP is (or actually is not, in reality, since 192.168.0.1 apparently > doesn't exist on your network). Seems like a reasonable explanation to me. Any more tips you can offer about where to look would be a great help. Peter
