View this page in English

Censornet - internet filtering on your terms

BECTA Accredited products VMWare Certified Virtual Appliance Members of the Internet Watch Foundation Shortlisted for the BETT 2008 Awards Computer Security Awards finalist
Chat online now or call +44 (0) 845 230 9590 for help & advice

Search knowledge base

Product specific

Home » Knowledge base » Troubleshooting Web Proxy Auto Discovery

Troubleshooting Web Proxy Auto Discovery

September 06, 2011 • Customer Services       
Synopsis

Web Proxy Auto Detection can sometimes be difficult to debug. The suggestions in this article can help you find out where the problem is.

Article

The following suggestions can help you to debug a problem when using Web Proxy Auto Detection:

  • Determine if the problem is with the wpad.dat script itself or the way in which it is served to the browser (DHCP or DNS method). To do this, configure a web browser to use the wpad.dat file directly. In Interent Explorer, this can be done by setting the Use Automatic configuration script option to the location of your wpad.dat file, e.g. http://censornet.local/wpad.dat. Close the browser and restart it. Check if the browser is now using the proxy by browsing to a site that would normally be blocked. If it is blocked correctly, then the problem is with the DHCP or DNS configuration. If it does not work, you should double check your wpad.dat script for mistakes and syntax errors. Check out the example wpad.dat file in the Related Articles section for reference.
  • Make sure the browser can resolve the address of the wpad.dat location. Try and go to the address in your web browser and see if there are any errors.
  • Review this article and follow the steps in DHCP or DNS section depending on what is relevant for your set up. http://technet.microsoft.com/en-us/library/cc302643.aspx

 

Related articles


Last modified on Tue, September 06, 2011 « Back