Yes, so in this instance you have to configure your final gateway to _only_ accept requests from the squid server, and _not from the other machines on your network_....
Bob ----- Original Message ----- From: "Kenn Murrah" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, January 24, 2003 12:19 PM Subject: Re: [squid-users] forcing users to access Squid ... > I guess I should have supplied more details ... i AM running a transparent > proxy, but that simply saves me from having to configure everyone's browser > .. they can STILL hit the gateway directly if they know the address ... > isn't that right? > > > ----- Original Message ----- > From: "Gavin Hamill" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Friday, January 24, 2003 11:04 AM > Subject: Re: [squid-users] forcing users to access Squid ... > > > > On Friday 24 January 2003 4:58 pm, Bob Avery-Babel wrote: > > > Yep. Transparent Proxy. > > > > > However, if you can't use or don't want to use transparent proxy then it > > > becomes a little more complicated. > > > > If not, then possibly the best way would be to apply a registry policy to > the > > Windows machine and make sure the user of the machine actually only has > 'User > > Rights' - this is a more broad general sysadmin topic... > > > > It means the user can use applications to do their job - they don't need, > and > > shouldn't be able to modify network, proxy, hard disk or system settings. > > > > Configuring each local user into the "Administrator" group is asking for > > trouble, even if it does mean a little less inconvenience re: ActiveX > > controls and installing new software. > > > > But that doesn't change the fact I still administer networks where > everyone > > has a password of "password" <sigh>.... don't worry, the yearly > maintenance > > fee makes up for it :) > > > > Cheers, > > Gavin. > > > >
