SFR NB6V WiFi Box Disconnection - DNS_PROBE_STARTED Messages...
MauriceJ
Posted messages
2
Status
Member
-
brupala Posted messages 111188 Registration date Status Member Last intervention -
brupala Posted messages 111188 Registration date Status Member Last intervention -
Hello,
For the past few weeks, when I browse the Internet, certain pages are erroring out.
The most common messages are DNS_PROBE_STARTED sometimes followed by DNS_PROBE_FINISHED_NO_INTERNET and sometimes by ADDRESS OF namedsit NOT FOUND.
The problem is infrequent (about 1 error per "hour"), browser-independent, unrelated to the accessed site, and not reproducible (a page may load and then not load an hour later).
By clearing the Windows DNS cache (ipconfig /flushdns) as well as the browsing data, I have not achieved any greater reproducibility.
The issue only occurs when connected via WiFi to the box
The issue resolves itself, taking about 1 to 30 seconds. If I cut the WiFi connection in the Internet access menu and reconnect, the issue is immediately resolved.
During this delay of 15 to 20 seconds, a ping to my box's address from my PC fails, which makes sense.
During this same period, pings from another PC (a much slower PC that I use rarely) are successful, and I can display pages and access the Internet from this second PC as well as from my smartphone connected to my box.
It seemed to me that by continuously pinging, certain pings fail (sometimes 1 out of 4), as if there is a "permanent" instability of the WiFi connection.
This problem is not new, and numerous posts have appeared on this forum and SFR's, with many suspicions of SFR problems... particularly their DNS server, but especially the WiFi router of their NB6 box.
I don’t really believe in the DNS server hypothesis as I never have issues when I am connected via Ethernet.
Does anyone know what could be behind the first message "DNS_PROBE_STARTED"....
My hypothesis is that it is not the DNS that is at fault but the "session" between the browser (or more likely the network layers of "Windows") and the remote DNS server.
Maybe this session fails due to interruptions on the WiFi, with timeout mechanisms... Hence something very random... which could also depend on the speed of the PC, potentially the WiFi congestion...
For the past few weeks, when I browse the Internet, certain pages are erroring out.
The most common messages are DNS_PROBE_STARTED sometimes followed by DNS_PROBE_FINISHED_NO_INTERNET and sometimes by ADDRESS OF namedsit NOT FOUND.
The problem is infrequent (about 1 error per "hour"), browser-independent, unrelated to the accessed site, and not reproducible (a page may load and then not load an hour later).
By clearing the Windows DNS cache (ipconfig /flushdns) as well as the browsing data, I have not achieved any greater reproducibility.
The issue only occurs when connected via WiFi to the box
The issue resolves itself, taking about 1 to 30 seconds. If I cut the WiFi connection in the Internet access menu and reconnect, the issue is immediately resolved.
During this delay of 15 to 20 seconds, a ping to my box's address from my PC fails, which makes sense.
During this same period, pings from another PC (a much slower PC that I use rarely) are successful, and I can display pages and access the Internet from this second PC as well as from my smartphone connected to my box.
It seemed to me that by continuously pinging, certain pings fail (sometimes 1 out of 4), as if there is a "permanent" instability of the WiFi connection.
This problem is not new, and numerous posts have appeared on this forum and SFR's, with many suspicions of SFR problems... particularly their DNS server, but especially the WiFi router of their NB6 box.
I don’t really believe in the DNS server hypothesis as I never have issues when I am connected via Ethernet.
Does anyone know what could be behind the first message "DNS_PROBE_STARTED"....
My hypothesis is that it is not the DNS that is at fault but the "session" between the browser (or more likely the network layers of "Windows") and the remote DNS server.
Maybe this session fails due to interruptions on the WiFi, with timeout mechanisms... Hence something very random... which could also depend on the speed of the PC, potentially the WiFi congestion...
For your information, here are some details about my configuration:
ACER PC running Windows 10 home
Version 10.0.19042 Build 19042
Windows is updated; Restorehealth sfc /scannow revealed no issues
Qualcomm Atheros Communications WiFi card, version is up to date.
SFR NB6V box (fiber)
Maybe it would be relevant to test the connection with tools more sophisticated than simple burst pings?
Let's see if you can give me some leads (not necessarily solutions but leads for work, references to similar issues…)
Thank you in advance and have a great day.
4 answers
-
Hi,
it's simply connectivity issues between the PC and the box (packets that are not passing through).
You can try restricting the Wi-Fi to Wi-Fi N on the box.
--
and ... There you go! -
Hello
The problem is actually quite complex, and I've just realized that it has been mentioned many times on this forum (just type DNS_PROBE_STARTED).
There have been suspicions regarding SFR, particularly regarding their NB6 fiber box (and the WiFi router).
But there are also suspicions related to updates of Windows 10, and I have just implemented Microsoft's recommendations available at this link (including resetting TCP IP layers, reinstalling drivers...)
https://support.microsoft.com/fr-fr/windows/r%C3%A9soudre-wi-fi-probl%C3%A8mes-de-connexion-dans-windows-9424a1f7-6a3b-65a6-4d78-7f07eee84d2c
I will continue my tests and keep the community informed
Best regards -
In my opinion,
the DNS_PROBE_MACHIN messages do not come from Windows, but are rather typical of Chrome doing its own thing.
Microsoft Edge is based on Chrome.
--
and ... There you go! -
Hello
Yes, it's indeed a browser error management mechanism.
Initially, it must be a call from the browser to a service to retrieve the IP address from the page's URL, this service fetching the address either from the Windows cache or through a call to the remote DNS server.
What is confusing is that even after clearing the browsing data and the Windows DNS cache, there is no reproducibility.
Despite days of analyzing the problem, I can't reproduce an error case simply.
It's as if there's another cache...
Or it's a "unfortunate" combination of Windows processes (related to how the browser functions) coupled with other processes managing communication, with error management, retries, timeouts in both cases, and maybe all of that glitches "in certain cases."
All of this could potentially be linked to Windows updates... (that's what SFR sometimes said, and they might actually be right)
It might take several more days to gain clarity.
I will continue cross-testing this weekend (I access my neighbor's box from my PC and vice versa, my neighbor accesses my box on my PC). If we manage to reproduce an error case, we'll have made progress...
Best regards.-
No, I don't think so.
SFR is definitely at fault since this happens often with their boxes.
A good test for system resolution is nslookup, you can even choose the resolver.
A temporary but recurring connectivity issue, as I mentioned earlier, is probably the cause.
At first, it's true that we don't really know which DNS resolver Chrome is testing on its own, and we still don't know if it's a DNS resolver; it could just be access to some Google or Microsoft server.
Today it becomes very complicated and unpredictable with DOT and DOH techniques that are implemented in browsers in addition to traditional resolutions.
It's good to have workarounds through the browsers, but we shouldn't fall into obscurantism on their part either.
Check with nslookup that everything is fine at the DNS contacts level already.
-
