Compatibility issue: dns integration check failed: did not receive test query after 45s #1720
Comments
|
Greetings and welcome to our community! As this is the first issue you opened here, we wanted to share some useful infos with you:
|
|
hey @Knubbel you should look into your ALE Flow Customization, in the debug info I only see that you have it enabled, but not what changes you made. The conflict is probably there. https://learn.microsoft.com/en-us/windows/win32/fwp/ale-flow-customization ALE Flow Customization refers to the specific configurations that affect how network traffic is processed in a network environment, typically dealing with protocols, inspection, or redirection of data flow for various purposes such as security or performance optimization. When it comes to interference with Portmaster, this depends on how ALE Flow Customization is implemented. Since Portmaster operates as a network firewall and privacy tool that monitors and controls connections, any external traffic manipulation (like that done by ALE customization) could potentially conflict with Portmaster’s own handling of network traffic. Which is why we do the network checks! and why you get the notification. |
I have previously never heard of such thing and as a simple user I am not aware of anything like that that I would have done. The PC was set up freshly by me and so far only limited stuff has been changed be me. I have not changed anything in windows' own firewall. Can you describe where/how I could "look into my ALE customization"? There is Avast One Antivirus running, but this is not the issue, as it didnt pose an issue on the old Win 10 PC and I now have uninstalled it for a while and the "compatibility issue" still showed up. The one thing I am testing now is if the traffic monitor here (https://github.com/zhongyang219/TrafficMonitor/blob/master/README_en-us.md) is causing the problem. Other than Adguard Home, Avast and the TrafficMonitor I am not aware of anything I have installed or done which has to do with internet connectivity. |
|
I could now identify the root cause of the issue. It stems from an incompatibility (I would actually call it a bug) of Portmaster with standard Windows 11 functionality to use DNS-over-HTTP (DoH). I would expect Portmaster to either be able to work with the given standard Windows 11 setting or at least be able to identify this setting precisely as causing problems. |
You are right, the error message in that regard might need some improvement. It is a bit vague and we maybe can look into improving it. That being said, this is not a default setting, but a change you made to that network interface. In the end, Portmaster is designed to work well on a "default" windows machine, that is what we can build for - any user changes are in the responsibility of that user. |
What happened:
After 3-10 min of running on Windows 11 Pro 64bit Portmaster 1.6.10 starts reporting a "compatibility issue".
The freshly installed windows PC is behind a router which gets its DNS resolving from a Raspi Adguard Home instance (which did not cause any issues a day before with the old Win 10 PC).
Both Portmaster and windows 11 also have been directed to use Adguard Home as DNS resolver via DoT/DoH.
What did you expect to happen?:
No compatibility issue.
How did you reproduce it?:
Anytime the new PC starts and after waiting a couple of minutes.
Debug Information:
The text was updated successfully, but these errors were encountered: