Recently I updated my Windows 10 systems to version 1511, build 10586.36 and I started to see this issue happening intermittently, and I am wondering if anyone else gets the same problem and if any workarounds exist.
The issue: After Windows 10 reboots (due to various system updates), sometimes it cannot connect to other Neorouter clients, this does not happen every time but it does very often (roughly the chance is about 40%).
Neorouter version: Free, 2.3.1.4360[1].
Let's say, I have NR client system A (Windows 10 v1511), and several other systems: B (Windows 10 v1511, NR client), C (Linux, NR server + NR client)
After system A reboots, its NR network explorer shows itself as "online", and it sees B and C (both online), somehow, 1. when A tries to ping B, A gets no replies 2. when A tries to ping C, A gets no replies
At the same time, B and C both see that A is online, but 1. when B tries to ping A, B gets no replies 2. when C tries to ping A, C gets no replies 3. when B tries to ping C, B gets replies 4. when C tries to ping B, C gets replies
system A will stay in this state and never recover itself (I waited for several hours).
However, from system A, if I right-click on the network connection tray icon and choose "Open Network and Sharing Center", a few seconds after the Network and Sharing Center dialog comes up, system A's Neorouter connections to other systems are fully recovered and working properly from that point... until next reboot.
I saw this problem on several Windows 10 systems, with various CPUs (Intel, AMD) and network card (wired, wireless, different brands, etc.)
I did not see this before Windows 10 v1511 (Windows 7 / 8.1 / 10 v1024)
Did anyone see this problem?
EDIT: I have seen this problem with the following English (US) Windows 10 builds (both Home and Pro) Windows 10 Version 1511, OS Build 10586.36 Windows 10 Version 1511, OS Build 10586.63 Windows 10 Version 1511, OS Build 10586.71 Windows 10 Version 1511, OS Build 10586.104 Windows 10 Version 1511, OS Build 10586.122 Windows 10 Version 1511, OS Build 10586.164 Windows 10 Version 1511, OS Build 10586.218 Windows 10 Version 1511, OS Build 10586.420 Windows 10 Version 1511, OS Build 10586.494 === windows 10 anniversary update, unfortunately, I still saw the same issue: Windows 10 Version 1607, OS Build 14393.10 Windows 10 Version 1607, OS Build 14393.51 Windows 10 Version 1607, OS Build 14393.82 Windows 10 Version 1607, OS Build 14393.105 Windows 10 Version 1607, OS Build 14393.187
With the new version (2.3.2.4450), this issue has been fixed.
The problem is back: Windows 10 Version: 1703, OS Build 15063.332
Last edited by ElTopo on Mon Jun 05, 2017 2:33 pm, edited 20 times in total.
|