On Wed, 2011-04-27 at 08:41 -0500, Mike Hendrie wrote: > Alright. Please let me explain. > > I am implementing squid in the school. > > Squid box 172.20.0.3 > All workstations gateway are 172.20.0.3 > All workstations proxy settings are 172.30.0.3:8080 > Ah, that makes more sense. > The proxy settings are working fine for blocking content, however, I > am having the following issues: > > The school's web server is hosted locally. Locally where? On the same server as Squid (172.20.0.3)? > When the workstations try > to access the site via the public domain name, it fails. Okay... well there could be a lot of reasons: Your workstations will be requesting the URL from the Squid server which will be resolving the public IP address of the website. The Squid server will therefore need to access the public IP address, which comes back to the question above as to where on the network the website is hosted. You might need to set the DNS on the proxy server to resolve the website to the local IP address. Depending where you host your public DNS, you may also have to make adjustments to that. The web server itself will need to be listening on the right port to serve the request - it may only be serving requests on the public facing interface. In short, more information is needed about your exact set up to answer the question. > Also, there are several applications the school uses. These > applications range from port 5000-5005. > Where are the applications hosted? On the internal network, on the public internet, on the proxy server? Andy -- To unsubscribe from this list: send the line "unsubscribe netfilter" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
