Mr Wells wrote:
Tests:
A) set a PC to x.x.x.104 using X-cable connect directly to proxyEXT external NIC - configure Firefox to x.x.x.103:3128 - Works
B) from home - ping x.x.x.103 - Works
C) from home - VNC into proxyEXT - Works
D) tracert to x.x.x.103 - Works 17 hops
E) from home - configure web browser to x.x.x.103:3128 - not working
Test E) above. In Firefox I get a general error telling me the server took too long to respond. IE gives the DNS error page.
These errors in E)above can be reproduced by configuring the web browser to a non-existent proxy. e.g. x.x.x.104:3128
Thanks
step 1) is port 3128 open on the router? ie telnet x.x.x.103 3128
Unable to test as yet - Telnet not installed.
step 2) is the router actually forwarding traffic from that port to
proxtEXT? wireshark/tcpdump will show this.
I have no access to the router - it's ISP maintained - will forward your checks though.
You say earlier 'ISP sent replacement part', I took from that it was
maintained by them but housed with you. If so you can test with a
machine spoked from a HUB on the in/out cables of the router and watch
the traffic.
step 3) is squid proxy listening on pubic-facing IP (10.1.1.61) or
wildcard IP (0.0.0.0) at that port? netstat -antp
Yes, netstat proved that it's listening on x.x.x.103 3128, and see test A above.
But no traffic exiting the router to the proxy machine?
Amos
--
Please use Squid 2.6STABLE17+ or 3.0STABLE1+
There are serious security advisories out on all earlier releases.
