Windows 10: wpad issues

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 Edgechromium 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 https://kb.k12usa.com/Knowledgebase/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.

:)

 

AMD FX OC'ers Club

That's what the auto setting will do since you're over the 1333 mark it jumps to the next step which isn't listed or officially supported I assume by that ram.

At this point though I would suggest dropping the multi one step or .5 so that we can get something stable and possibly take the heat issue out of the picture for now.

 

Edge Search Does Not Permit Change of Region


I got these suggestions from the Microsoft Community forum.No. 1 worked for me:

Thank you for posting the query on Microsoft Community. I am glad to assist you on this.
We have reproduce the issue here and we are able to access non-regional search for google using Microsoft Edge.
I would suggest you to try the below steps and check if it helps.
Step 1:
Clear browsing data option of Microsoft Edge and check if you face the issue. To do so perform the steps below.

1. Click on the More actions icon next to the feedback icon present on top right corner of the Project Spartan homepage.
2. Select Settings and click on Choose what to clear.
3. Check the boxes Browsing history, Cookies and saved website data and Cached data and files and click on Clear.

Step 2:
I suggest you to create a new user account and check if the issue occurs.

1. Go to Settings.
2. Choose Accounts and then select Family and other users.
3. Select add someone else on this PC.
4. Enter a user name and hit next.
5. Click on Finish.
6. Sign out from the current Account and Log into the new account.

Step 3:
It could also happen because of network issue. I suggest you to try with different network connection and check if it helps.

 

DHCP option 252 wpad issue

This is more of a bug report now I've located a fix, would be nice if someone could weigh in on whether this will be patched or not.

Deploying option 252 in a dhcp scope deploys proxy.pac location to the client registry:

HKEY_USERS\S-1-5-19\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Wpad

when moving to a new scope without option 252 this location is not forgotten and proxy continues to prompt for authentication until registry key is manually deleted.

Is this by design or a bug?