Hello,
I'm struggling to set up Direct Access to allow it's clients to pick up the WPAD file. It works ok for the LAN clients, but not for DA ones.
Some information about our setup:
1) Force tunneling is used
2) There is a WPAD entry in the DNS table set up as an Alias pointing to the FQDN of our web server hosting the WPAD file. (somehow I think this might be a problem and we should use an A record for that)
3) Local name resolution is set to least-restrictive (use local DNSfor any kind of DNS resolution errors).
4) Windows 7
The problem I am having is that my browser can't pick up the WPAD file using Direct Access. And it does not matter if I use "Automatically Detect Settings" or "Use Automatic Configuration Script". I clear the browser cache, re-open it and the WPAD file is not picked up. I do the same thing on a Client on the LAN and it works like a charm.
This is also not a firewall problem because I can download the WPAD file when typing the "Auto-config script" address in the address bar.
Does anyone have any ideas? Something needs to be done in the NRPT table? The WPAD alias should be changed to a host record?
Kind regards,
Wojciech
EDIT:
To add some more confusion to this topic, something about WPAD is working.
We have 2 WPAD files:
1) Production one with the Alias in the DNS
2) Test one without a DNS entry that needs to be manually specified as the "auto-config script"
At this moment the only difference between the two is the entry for the Proxy server. The production one has it set by IP address, the test one by FQDN. And what I am unable to understand is why MS Teams are working fine with the test one, but do not work with the production one...
And why MS Teams are actually looking at the WPAD file and IE is not...