Menu
Reply
  • 2
  • 0
  • 0
koberk
Joining in
70 Views
Message 1 of 3
Flag for a moderator

Superhb crashes every night

My superhub crashes every night, if I leave any devices connected to the ethernet ports. Why is this, and is there a fix?

0 Kudos
Reply
  • 2
  • 0
  • 0
koberk
Joining in
68 Views
Message 2 of 3
Flag for a moderator

Re: Superhb crashes every night

01/12/2016 07:42:47 GMT 01/12/2016 07:42:47 GMT Error (4) 68010302 DHCP WAN IP - 82.13.226.35 01/12/2016 07:41:56 GMT 01/12/2016 07:41:56 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out 01/12/2016 07:41:53 GMT 01/12/2016 07:41:53 GMT Error (4) 68000407 TOD established Time Not Established Time Not Established Critical (3) 82000200 No Ranging Response received - T3 time-out Time Not Established Time Not Established Notice (6) 84000510 Downstream Locked Successfully Time Not Established Time Not Established Critical (3) 82000200 No Ranging Response received - T3 time-out Time Not Established Time Not Established Notice (6) 84000510 Downstream Locked Successfully 01/12/2016 07:37:35 GMT 01/12/2016 07:37:35 GMT Error (4) 68010302 DHCP WAN IP - ******** 01/12/2016 07:36:39 GMT 01/12/2016 07:36:39 GMT Error (4) 68000407 TOD established Time Not Established Time Not Established Notice (6) 84000510 Downstream Locked Successfully 30/11/2016 11:54:59 GMT 30/11/2016 11:54:59 GMT Error (4) 68010302 DHCP WAN IP - ******** 30/11/2016 11:54:24 GMT 30/11/2016 11:54:24 GMT Error (4) 68000407 TOD established 30/11/2016 11:54:02 GMT 30/11/2016 11:54:02 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out 30/11/2016 11:54:00 GMT 30/11/2016 11:54:00 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out 30/11/2016 11:53:54 GMT 30/11/2016 11:53:54 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out 30/11/2016 11:53:50 GMT 30/11/2016 11:53:50 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out 30/11/2016 11:53:49 GMT 30/11/2016 11:53:49 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out 30/11/2016 11:53:42 GMT 30/11/2016 11:53:42 GMT Notice (6) 84000510 Downstream Locked Successfully 30/11/2016 11:53:30 GMT 30/11/2016 11:53:30 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out 30/11/2016 11:53:30 GMT 30/11/2016 11:53:30 GMT Critical (3) 82000700 Unicast Ranging Received Abort Response - initializing MAC

 [MOD EDIT: Personal and private information has been removed from this post. Please do not post personal or private information in your public posts. Please review the Forum Guidelines]

0 Kudos
Reply
  • 3.88K
  • 120
  • 203
Forum Team (Retired) Adam_L
Forum Team (Retired)
44 Views
Message 3 of 3
Flag for a moderator

Re: Superhb crashes every night

Hi koberk, 

Thanks for the post! I am sorry to learn that your Super Hub crashes every night, I apologise for any troubles incurred.

I have tested things from here and I can see that everything looks great! No errors or time outs inside the Hubs logs and all of your power levels are where they should be.

Are you still having these issues? If so, how are you connected wired or wireless?

When the connection drops is there any noticeable change to the Hubs light sequence?

When the ethernet devices are connected, do any of the lights come on the back of the ethernet ports?

Speak soon, 

Thanks, 

Adam.


Tech fan? Have you read our Digital life blog yet? Check it out


0 Kudos
Reply