M
Mavack1
I have an odd issue that i am unable to track down sort out. Have put this under windows instead of IE11 because it seams to stem from windows internet options.
In our business we have a very long proxy.pac file because there are internal domains that are only reachable via specific proxies they are not publicly resolvable. One of these sites is old and runs on aspx so requires IE (we are migrating it along eventually)
Across multiple devices Edge(chromium) or chrome the wpad lookup works correctly and the site opens, unfortunately it doesn't function correctly (aspx)
However on some devices when opening in IE11 it works fine.
On another subset we get DNS not found, as thou it is totally skipping the wpad process.
Another interesting side effect on these hosts that don't work if we try to open URLs in edge that are not FQDN ie http://internalsite (which is also http://internalsite.internaldomain)
We get
No authority could be contacted for authentication
unless we go to local intranet zone and check Automatically detect intranet network (on the other set of devices that IE11 works fine this doesn't need to be checked)
We are awkwardly in a split domain network (in transition) so these sites would normally use NT login (sharepoint) however these devices are no longer part of that domain so we have to authenticate domain1\username when the login pops up.
We have tried disabling AutoproxyResult cache (https://support.microsoft.com/en-au...-automatic-proxy-caching-in-internet-explorer)
wpad override (Proxy Auto Detect (WPAD) Issues With IE & Windows 7)
The wpad key is empty otherwise not showing a cached entry that i can see.
Now if i manually set the proxy statically ie http://wpad/wpad.dat it works fine, but this obviously breaks the host when we move backwards and forward between on VPN and off VPN.
Have checked the dev console (F12) however this doesn't show the pre GET/CONNECT process.
I'm also in a situation that currently devices are at home, so wireshark to check what dns lookups occur for wpad are encrypted out the interface so no idea if the lookup fails, but given nslookup from cmdline wpad resolves, wpad.internaldomain resolves and http://wpad/wpad.dat works i'm a bit lsot.
It's like something has told it to skip the wpad process in IE11 but works fine in edge, or something wrong with resolution of internaldomain stuff.
This is on different identical hardware and fresh installs, we have only been on this platform for a few weeks overall so devices are very fresh.
Continue reading...
In our business we have a very long proxy.pac file because there are internal domains that are only reachable via specific proxies they are not publicly resolvable. One of these sites is old and runs on aspx so requires IE (we are migrating it along eventually)
Across multiple devices Edge(chromium) or chrome the wpad lookup works correctly and the site opens, unfortunately it doesn't function correctly (aspx)
However on some devices when opening in IE11 it works fine.
On another subset we get DNS not found, as thou it is totally skipping the wpad process.
Another interesting side effect on these hosts that don't work if we try to open URLs in edge that are not FQDN ie http://internalsite (which is also http://internalsite.internaldomain)
We get
No authority could be contacted for authentication
unless we go to local intranet zone and check Automatically detect intranet network (on the other set of devices that IE11 works fine this doesn't need to be checked)
We are awkwardly in a split domain network (in transition) so these sites would normally use NT login (sharepoint) however these devices are no longer part of that domain so we have to authenticate domain1\username when the login pops up.
We have tried disabling AutoproxyResult cache (https://support.microsoft.com/en-au...-automatic-proxy-caching-in-internet-explorer)
wpad override (Proxy Auto Detect (WPAD) Issues With IE & Windows 7)
The wpad key is empty otherwise not showing a cached entry that i can see.
Now if i manually set the proxy statically ie http://wpad/wpad.dat it works fine, but this obviously breaks the host when we move backwards and forward between on VPN and off VPN.
Have checked the dev console (F12) however this doesn't show the pre GET/CONNECT process.
I'm also in a situation that currently devices are at home, so wireshark to check what dns lookups occur for wpad are encrypted out the interface so no idea if the lookup fails, but given nslookup from cmdline wpad resolves, wpad.internaldomain resolves and http://wpad/wpad.dat works i'm a bit lsot.
It's like something has told it to skip the wpad process in IE11 but works fine in edge, or something wrong with resolution of internaldomain stuff.
This is on different identical hardware and fresh installs, we have only been on this platform for a few weeks overall so devices are very fresh.
Continue reading...