Breezewood wrote:
UPDATE: Got the Neorouter client to work again by having the following conditions set:
1. DHCP range set back to "
10.0.0.0/255.255.255.0"
2. Media Status of the Neorouter Network Adapter set to "
Always Connected"
3. Changed Compatibility of the Neorouter Client in Windows 10 set to "
Windows 8"
However, this created the issue of some clients showing in the Windows 10 client as being offline when those clients are actually confirmed to be connected.
Attachment:
weird.png
"Media Status of the Neorouter Network Adapter set to "Always Connected""
This has been a known issue for a couple of Windows 10 builds and was posted on the forum in the past. You shouldn't have to mess with DHCP range or anything else. If the forum wasn't basically abandoned and getting daily spam, then they should have made a sticky topic so that people would just know about this workaround and not have to discover that setting on their own.
The free versions haven't received any updates in almost 3 years. And the last free version they released was missing a number of bug fixes that were mentioned in the release notes. The free version still uses old, broken SSLv3! And Neorouter is happy to leave free versions on this encryption... *sigh*
They are only doing updates for Pro versions. If you're only using the free version and do not need to support Win XP machines, you may want to migrate to something else still getting updates as there will only ever be more and more bugs since no more updates to free.