Jump to content

Recommended Posts

Posted

Hi all,

 

Trying to configure our proxy via DHCP (something we did a while back but have since not used) and I am struggling to work out where I am going wrong. The code so far is below. It is fairly simple and should just return the proxy for all website (will add exceptions for local addresses once I have this working).

 

function FindProxyForURL(url, host) {
return "PROXY http://ad.quantum.exa-networks.co.uk:3128";
}

 

This is pushed out using IIS (MIME type correctly set) and set in DHCP (definitely the correct URL) as well as being tested manually using the URL in 'Use Setup Script'.

 

Interestingly, the script does seem to be doing something, as manual proxy setting now does nothing (entering gibberish in as the url still works), but it seems to be going DIRECT rather than using the actual proxy. Any ideas where I may be going wrong?

Posted

just looked at a proxy pac here which doesnt have the http:// in front of the proxy server but not sure thats the issue

 

However, I recall wpad and the like were considered dodgy security-wise - google dnsserverglobalqueryblocklist as you might have to allow it in DNS

 

to see if that helps.

 

Additionally, for troubleshooting

 

enter edge://net-export

 

Start it, do a bit of browsing and then upload the log - it's quite nice at showing proxy in use per URL

Posted
just looked at a proxy pac here which doesnt have the http:// in front of the proxy server but not sure thats the issue

 

However, I recall wpad and the like were considered dodgy security-wise - google dnsserverglobalqueryblocklist as you might have to allow it in DNS

 

Same here (no http) and same vague memories about WPAD.

 

What's your url for "use setup script"?

 

 

^^^and this.

Posted

The site https://findproxyforurl.com/ has a lot of good info on pac files.

 

And as some have mentioned, clients need to be able to resolve the hostname only of wpad and resolve that to the system hosting the proxy.pac/wpad.dat file. In MS DNS services, the WPAD hostname is blocked by default - it has to be removed from that and then an alias or hostname of wpad needs to be added to your DNS.

 

It's important that clients can resolve the hostname only of wpad, not just the full host and domain name like wpad.mydomain.local. You may need to add search domains to DHCP as well.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...