WPAD Help

killmasta93

I think the issue is your lightppd if you let pfSense handle WPAD files and the DHCP and DNS either pfSense or windows server your good to go. Why dont you start first doing exactly from the guide that aGeekHere shows.

fifouch

@killmasta93:

I think the issue is your lightppd if you let pfSense handle WPAD files and the DHCP and DNS either pfSense or windows server your good to go. Why dont you start first doing exactly from the guide that aGeekHere shows.

thank's for your replay
As i have already said before i did try his solution before i post here but i got the same issue
Client dont auto detect proxy

KOM

Create a firewall rule to prevent browsing via the usual HTTP and HTTPS port 80 445 ensuring all browsing is via proxy

It's ports 80 and 443, not 445.

Can your clients resolve wpad.yourdomain.tld? Can your browsers fetch http://wpad.yourdomain.tld/wpad.dat? What is the contents of your wpad.dat file?

Bear in mind that wpad.dat must be served from an HTTP server, not HTTPS.

fifouch

@KOM:

Create a firewall rule to prevent browsing via the usual HTTP and HTTPS port 80 445 ensuring all browsing is via proxy

It's ports 80 and 443, not 445.

Can your clients resolve wpad.yourdomain.tld? Can your browsers fetch http://wpad.yourdomain.tld/wpad.dat? What is the contents of your wpad.dat file?

Bear in mind that wpad.dat must be served from an HTTP server, not HTTPS.

Thank's for replay yea sorry its port 443 and yea client can resolve wpad.mydomain.local also wpad they can also download the 3 files
the content of my wpad.dat files is

function FindProxyForURL(url, host) 
{ 
    if (isPlainHostName(host) ||
        shExpMatch(host, "*.local") ||
        isInNet(dnsResolve(host), "192.168.1.0",  "255.255.255.0"))
        return "DIRECT";

    return "PROXY 192.168.1.1:3128";
}

aGeekhere

Try clearing web browser cache

Bear in mind that wpad.dat must be served from an HTTP server, not HTTPS.

Very important and can be easily missed.

fifouch

@aGeekHere:

Try clearing web browser cache

Bear in mind that wpad.dat must be served from an HTTP server, not HTTPS.

Very important and can be easily missed.

Well
I did install new clean pfsense follow all your setps
Clear cache in web browsers
I have some client who can autodetect and others who still have the same issue :o

aGeekhere

I have some client who can autodetect and others who still have the same issue

Are these other people using firefox? then add automatic proxy configuration url to the url of the wpad (like http://pfsense.mylocaldomain.local/wpad.dat) etc

fifouch

@aGeekHere:

I have some client who can autodetect and others who still have the same issue

Are these other people using firefox? then add automatic proxy configuration url to the url of the wpad (like http://pfsense.mylocaldomain.local/wpad.dat) etc

Thank's for your replay again
Those clients users are using Chrome and IE

killmasta93

hmm..what operating system? the clients that have the issue can they resolve wpad? are these clients in a GPO environment? If so Could you try pushing them the proxy settings though GPO?

fifouch

@killmasta93:

hmm..what operating system? the clients that have the issue can they resolve wpad? are these clients in a GPO environment? If so Could you try pushing them the proxy settings though GPO?

hey the users are using windows 7, 8 and 10 (x64) and they are not in gpo environment
thank's for reply

killmasta93

But you know whats odd…If i put pfSense as HTTPS internet explorer keeps blocking the sites but not chrome or firefox soo odd..but anyway Also which computers exactly are not auto detecting? WPAD is pretty powerful and forces all client to the proxy ONLY IF the auto detect proxy settings is checked