I thought that if that box was ticked and the proxy info was entered that the two settings would conflict. Naturally if it says "Automatically detect settings" and the proxy info is the common sense would say that it would detect and use the proxy info but we are talking about Microsoft here.
When I first setup Smoothwall on our network with the help of Smoothwall support I was told to make sure that the "Auto detect" was unticked.
The automatic detection will only conflict if it has something to detect in the first place. However, it can slow down initial browser opening, as it tries to detect but fails.
my pc has it ticked, as do others in the network, never had a conflict with it.
Its not an issue for me, I was just following the thread and wanted to ask a question. I looked at the reg settings out of interest and wondered how "Automatically detect settings" box was unticked, but it appears it doesn't make a difference from everyones reports. :)
tested it today.. it wokrs for windows 7, doesn't seem to work for xp, any ideas?? (yes we still have some xp but we simply haven't had the budget to replace all of them)
Check whether your XP workstations have the GPP client extensions update installed.
GPP's will then work for XP as they do for Vista or later out the box. If required, you can deploy this update using WSUS.
I've gone down the WPAD route. So much easier for everyone. Worth the time and effort to get up and running.
Re the wpad/PAC route:
How do clients access this from offsite? For example I add a line that for home router IP ranges it forces direct connection so staff don't need to turn it off.
Does the client system "cache" a copy of the wpad/PAC file or does the we server it's hosted on need to be publicly accessible?
If they're off site, they don't need it. The browsers will automatically use direct connection.
It caches it. You could always make a public one too.
And if they then connect via VPN it works Gain?
If so: awesome. Why have I wastes the past year with GPPs!