Forum Discussion

Peter0510's avatar
Peter0510
Tuning in
17 days ago

T3 error

I have a Hub 3 in modem mode. On the 26 December it lost connection. On 25/12/2025 00:05:3 I got a "No Ranging Response received - T3 time-out" error. 

This continued until 28 December when I reset the Hub.

This was very inconvenient as I was not at home at the time.
From The logs:

From the above I am still receiving the T3 error. Will this happen again?
How do I stop this from happening again? Also, I would be interested in what caused the error. 

4 Replies

  • legacy1's avatar
    legacy1
    Alessandro Volta

    Not seen that problem before but could be any number of reasons

    Are you back in modem mode and is fine?

    your router might of got a bad WAN IP from VM DHCP server (which can happen in router mode) and VM updated the DHCP server wrong and so your router stayed of that bad IP which when you changed to router mode  changed IP again. 

    or maybe the 10. backend Docsis server was updated wrong causing your WAN to be blocked

      

  • Yes, I have been using it in modem mode for a couple of years with no issues. A reboot solved the problem, but the downtime was very inconvenient.

    • legacy1's avatar
      legacy1
      Alessandro Volta

      So it was a reboot that fixed it not a reset

      I would think this does not happy much I know when I had the super hub 1 for it worked fine even on a IP change no reboot needed.

      So with the newer hub who knows whats stops them it can be your IP changed and your router was on a old lease that really should mean good but if VM pull the subnet for that area and they can't wait for your router to get a new IP that could happen. Or its the same IP you had but VM clear the DAI meaning you need to DHCP. Or VM was doing maintenance in your area and so docsis was up and down and maybe if down for too long the hub gives up trying to reconnect to the docsis network which really it should just keep on trying.

      So maybe for all we known you just need to unplug Ethernet then back in for your router to DHCP.

       

    • Steven_L's avatar
      Steven_L
      Icon for Forum Team rankForum Team

      Thanks for coming back to us, Peter0510, and we're glad that your issues have now been resolved, but apologise for the downtime that you experienced. Additionally, if you have any issues or questions now or in the future, please don't hesitate to let us know here, and we'll be happy to assist you.

      Kind Regards,

      Steven_L