The auto proxy detection system works by downloading a file called wpad.dat from the host wpad. First confirm this host exists from a command prompt:
If it doesn’t exist, you may have to put the correct DNS suffix. In the same command prompt, type
You should see a Primary DNS Suffix and a DNS Suffix Search List
Try appending each of these with a. to wpad :
If any of these work, then in your browser enter http://wpad. suffix /wpad.dat. This will download the proxy auto configuration file you can open in notepad.exe
Toward the bottom of this file, you should see a line saying
It might be repeated if you have multiple proxies available. The host and port are what you need.
If this file doesn’t exist, then either there is no proxy server, or the proxy server is being provided by dhcp (note that this would only work with IE, so if firefox can surf, this is not the method being used). If you don’t have access to the dhcp server to see what it is sending, the easiest way would be to open a site in ie, then go to a command prompt. Type
This will provide a list of connections made with the process id of each process. Go to Task Manager, and select View/Select Columns and enable PID (Process Identifier). Look for the PID of iexplore.exe in the list returned by netstat -ban This will reveal the proxy ip and port.
answered Oct 14 ’11 at 1:22
It probably works on some systems, but there s no host called wpad here (with or without the DNS suffix). I think this might be configured through some sort of domain policy or logon script, since it s greyed out in IE and cannot be changed. Anyway, I ended up writing a little C# program to get it instead. Hopefully your answer will help someone though! Mike Christensen Oct 14 ’11 at 15:04
The following command also seems to work. As a bonus it avoids contacting lots of DNS servers that might or might not work, and it avoids querying the registry, so it functions even in fairly locked-down environments:
Windows Vista or later:
Windows XP or earlier:
Some additional work is required to extract the proxy address from the output, so the registry approach is simpler if you know it’s going to be available.
I’ve found that on windows 7 netsh sometimes returns different results depending on how I call it. If I run the above command manually in a prompt, I get ‘Direct Access – No Proxy’. However, calling netsh from SAS results in an actual proxy being listed!
answered Sep 23 ’14 at 11:17
sais: Direct access no proxy server . but i definetly am behind a proxy. only shows WinHTTP Proxys philx_x Mar 20 ’15 at 13:11
The question is tagged [windows] – are you in a windows environment with a non-WinHTTP proxy? user3490 Mar 20 ’15 at 13:35
I m seeing the Direct Access line also. What did you mean by calling netsh rom SAS ? Ben Jun 15 ’15 at 17:36
netsh winhttp show proxy shows system proxy settings (Default user). A user may have different settings. xmedeko Dec 8 ’15 at 9:19
I m definitely behind a proxy and when I call netsh command I get: Direct access (no proxy server). . What is SAS? iaforek Oct 18 ’16 at 21:37
If you are using an auto-detect proxy settings then do in the address bar of you browser (no matter which one you have installed)