2009/11/16, Amos Jeffries <squid3@xxxxxxxxxxxxx>: > On Mon, 16 Nov 2009 15:25:30 +0100, Werner Müller > <w.muellerr@xxxxxxxxxxxxxx> wrote: >> 2009/11/16, Silamael <Silamael@xxxxxxxxxxxxxx>: >>> >>> On 11/16/2009 01:45 PM, Werner Müller wrote: >>>> The Problem is, that i cannot reach a Server over the IP: >>>> >>>> with this cache_peer entry i get a failure: >>>> cache_peer 1.1.1.1 parent 3128 0 default no-query no-digest >>>> >>>> The localhost entry was only a test. But it's very strange that it >>>> works with the localhost entry (localhost 1.1.1.1) and if i change the >>>> cache_peer entry in squid.conf it will not work. >>>> >>>> >>>> Here the entries from cache.log: >>>> ... >>>> | TCP connection to 1.1.1.1 (1.1.1.1:3128) failed >>>> Detected DEAD Parent: 1.1.1.1 >>>> | TCP connection to 1.1.1.1 (1.1.1.1.1:3128) failed >>>> | temporary disabling (Gateway Time-out) digest from 1.1.1.1 >>>> TCP connection to 1.1.1.1 (7.21.32.137:3128) failed >>>> ... >>>> >>>> (I changed the real IP for this post to 1.1.1.1) >>> >>> Hm, that must not be a Squid specific problem. Can you reach the server >>> manually? Works a telnet on the other server on port 3128? >>> >>> -- Matthias >>> >> >> Yes, i can reach the server manually. >> >> I've also installed SQUID and the Internet Traffic Virus Scan software >> on the same server, for testing. >> >> With this config it works: >> cache_peer 127.0.0.1 parent 3128 0 default no-query no-digest >> cache_peer localhost parent 3128 0 default no-query no-digest >> >> This config make problems: >> cache_peer 1.1.1.1 parent 3128 0 default no-query no-digest >> >> (1.1.1.1 is his own Server-IP) > > Sounds to me like the AV is either only accepting stuff from > localhost/127.0.0.1 or there is a firewall or routing table between the > boxes doing some blocking. > > Amos > > The Problem is solved with a setting in the AV software. Thank you for the support.
