Here is some information about my network to start with. We have all XP pro clients. All servers are Windows 2003 except a Red Hat Linux proxy/firewall. For anyone internal to see the web/outside world, they need to have all of the proxy info in their LAN settings. We have some computers in the building that we do not want to have internet access. I set up a GPO to define the proxy info and that worked great. I isolated the computers that weren't to have internet access into an OU by themselves so they didn't get the proxy policy. That worked great also.
Now here is the problem: We now have handfull of individuals with laptops and there are most likely only going to be more. When these users take their laptops home they can get to the internet if they connect to our VPN, however, if they just plug into their network at home or if the plug into a customers network they can not get to the internet because IE is trying to find our proxy server. So this is what I'm looking for.....I need a way for a pc to determine if it is on our network locally or if it is external to our network and then I need the proxy information defined depending on where the user is. What I mean I guess is I need the proxy defined if the users are in the building but I don't need any proxy information defined if they are out of the building.
I've been reading about my different options for defining proxy info. Apparently my options are Group Policy, WPAD (web proxy auto-discovery), or DHCPINFORM. Obviously the group policy isn't working for me. I'm just not sure what exactly the differences in behavior are for WPAD vs. DHCPINFORM. Is anyone currently utilizing either of these methods and if so can anyone shed some light on which would work better for my scenario?
|
