Community


All times are UTC - 5 hours




Post new topic Reply to topic  [ 27 posts ]  Go to page Previous  1, 2, 3
Author Message
 Post subject: Re: Windows 10 1511/1607 after-reboot issue
PostPosted: Fri Sep 30, 2016 3:13 pm 
Offline

Joined: Sun Nov 16, 2008 6:41 am
Posts: 1878
Hi guys,

The issue has been fixed in the latest release. (NeoRouter Free v2.3.2.4350, Pro v2.4.2.4460 and Mesh v2.4.3.4470 ) Please get the new build from the download page.

Let us know if you still have the issue.

Thanks,
KevinZ - NeoRouter team


Top
 Profile  
 
 Post subject: Re: Windows 10 1511/1607 after-reboot issue
PostPosted: Fri Sep 30, 2016 11:41 pm 
Offline

Joined: Thu Sep 15, 2016 3:55 pm
Posts: 3
Just in time! I planned to implement Swingtrade's semi-decision on all my domain PCs today (by the way, I want to thank him for it - great job!).

Released update worked for me! Thank you, NR Team, very much!


Top
 Profile  
 
 Post subject: Re: Windows 10 1511/1607 after-reboot issue
PostPosted: Wed Oct 05, 2016 1:33 pm 
Offline

Joined: Tue Feb 10, 2009 4:11 am
Posts: 96
With the new version (2.3.2.4450), neorouter client is much more stable and I haven't seen this "media disconnected“ problem since I upgraded.

Thank you, NeoRouter team and Kevin!

PS: I tried to edit this topic with [Fixed] label, unfortunately the forum's spam checking won't allow me to do so.


Top
 Profile  
 
 Post subject: Re: [Fixed] Windows 10 1511/1607 after-reboot issue
PostPosted: Mon Jun 05, 2017 2:29 pm 
Offline

Joined: Tue Feb 10, 2009 4:11 am
Posts: 96
This problem seems to come back after Windows 10's latest update, I've seen it on both Windows 10 Home and Pro.

Windows 10 (both Home and Pro):
Version: 1703 (OS Build: 15063.332)

Neorouter Free:
2.3.2.4450 [1]

Neorouter Network Explorer shows a list of neorouter devices (online and offline), however, ping online neorouter devices does not get replies (except ping itself).

ipconfig shows the neorouter adapter's "media state" is "media disconnected".

In most time, manually stop and restart "neorouter client service" may correct this the problematic issue, otherwise, the neorouter client service stays in this state.

I really hope neorouter add the optional feature of checking its adapter's media state and trying to ping neorouter server via neorouter IP, if somehow the media state goes to "disconnected" or the server does not reply, restart neorouter service.

Whatever causes this problem, neorouter really should not stay in this bad state... it should try to fix the problem automatically, a VPN should be solid.


Top
 Profile  
 
 Post subject: Re: [Issue] Windows 10 1511/1607/1703 after-reboot issue
PostPosted: Tue Jun 06, 2017 1:19 pm 
Offline

Joined: Sun Nov 16, 2008 6:41 am
Posts: 1878
Hi ElTopo,

The new Windows updates may take longer time to boot. Please try to adjust the following parameters in the Feature.ini file.

Here are the default values.

[Default]
TapRetryTimes=12
TapRetryPeriod=10
TapVerifyInterval=5

TapRetryTimes - Max number of retry times to activate Tap
TapRetryPeriod - Before next Tap activation, it waits for n seconds
TapVerifyInterval - Before verifying Tap status, it waits for n seconds

By default, it takes up to 3 mins ((10+5) X 12) to assign VIP to nrtap.

I think you can try to change the parameter to longer time (say 5min or 10min) see if it works for you.

Let me know if you have any question or concern.

Thanks,
KevinZ - NeoRouter team


Top
 Profile  
 
 Post subject: Re: [Issue] Windows 10 1511/1607/1703 after-reboot issue
PostPosted: Mon Jun 12, 2017 2:31 pm 
Offline

Joined: Mon Jun 12, 2017 2:28 pm
Posts: 1
sufyan hsdkla dsk sd sk lds l sdl ksdl lsd klsd lk kdsfl sadaf

_________________
Chk How to Lose Hips Fat and other Fitness Related Tips.We Working Related Research Work.


Top
 Profile  
 
 Post subject: Re: [Issue] Windows 10 1511/1607/1703 after-reboot issue
PostPosted: Tue Jun 05, 2018 7:44 pm 
Offline

Joined: Thu Sep 15, 2016 3:55 pm
Posts: 3
kevinz wrote:
Hi ElTopo,

The new Windows updates may take longer time to boot. Please try to adjust the following parameters in the Feature.ini file.

Here are the default values.

[Default]
TapRetryTimes=12
TapRetryPeriod=10
TapVerifyInterval=5

TapRetryTimes - Max number of retry times to activate Tap
TapRetryPeriod - Before next Tap activation, it waits for n seconds
TapVerifyInterval - Before verifying Tap status, it waits for n seconds

By default, it takes up to 3 mins ((10+5) X 12) to assign VIP to nrtap.

I think you can try to change the parameter to longer time (say 5min or 10min) see if it works for you.

Let me know if you have any question or concern.

Thanks,
KevinZ - NeoRouter team


After years, the problem returned to me, too. With last big update Win10Pro 1803 (build 17134.48).
Switching to longer time (20+10)x15 doesn't help at all :( Reinstalling/cleaning Neorouter doesn't help neither :(

NR Team, help us again, please!!!


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 27 posts ]  Go to page Previous  1, 2, 3

All times are UTC - 5 hours


Who is online

Users browsing this forum: No registered users and 29 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to: