I have a Lenovo Gaming PC which is physically connected to a small 4-port switch which is in turn connected to port 4 on my RT-AC88U (I have given up using ports 5-8 on the router due to known RT-AC88U problem). I also have a RT-AC68U as an AiMesh with wired backhaul to port 2 on my RT-AC88U. It's a rather busy network, with 25+ devices continuously connected, and 60+ total.
The router & network is generally very reliable, I have removed all 'fluff' (QoS, Parental Controls, VPN etc) from the Router, and it generally sits at less than 15% CPU load even under heavy network traffic.
But this Lenovo seems to reliably knock out the entire network very soon after booting, or as my son goes into a game, loads a new youtube video etc. During that 'blackout' period, the responsible computer seems to have good network access, but nobody else does. For other clients it looks like DNS resolution dies first, then after a few seconds you start to see 'you are not connected to the internet' etc. Then after a while, (30+ seconds) the network recovers. The severity and duration of the problem is variable, but seems to be related to how 'busy' that computers network is at startup, but exactly the same type of tasks (loading a new game, etc) tend to not cause problems 30 minutes later - it's only during the first minutes the unreliability occurs.
The downtime also causes the Mesh node to lose the connection to the primary router, which in turn causes local name resolution failure (can't reach devices connected via the Mesh by their computer names), and the inevitable chunk of assocation/disassociation.
I have limited that computers network connection to 100Mbps on the client adapter (we have 1gbps network, and can get 800 Mbps reliably) so in theory, even if that computer was trying to steal all available bandwidth, there should still be plenty over... That combined with the 'self healing' nature of the problem makes it hard for me to figure out where to look. Checking router logs shows nothing noteworthy, and running netstat, ping -t (ping an address continuously) and task manager on that computer doesnt show anything amiss at the time the problem is occuring.
Any ideas where to start troubleshooting this?
Thanks!
The router & network is generally very reliable, I have removed all 'fluff' (QoS, Parental Controls, VPN etc) from the Router, and it generally sits at less than 15% CPU load even under heavy network traffic.
But this Lenovo seems to reliably knock out the entire network very soon after booting, or as my son goes into a game, loads a new youtube video etc. During that 'blackout' period, the responsible computer seems to have good network access, but nobody else does. For other clients it looks like DNS resolution dies first, then after a few seconds you start to see 'you are not connected to the internet' etc. Then after a while, (30+ seconds) the network recovers. The severity and duration of the problem is variable, but seems to be related to how 'busy' that computers network is at startup, but exactly the same type of tasks (loading a new game, etc) tend to not cause problems 30 minutes later - it's only during the first minutes the unreliability occurs.
The downtime also causes the Mesh node to lose the connection to the primary router, which in turn causes local name resolution failure (can't reach devices connected via the Mesh by their computer names), and the inevitable chunk of assocation/disassociation.
I have limited that computers network connection to 100Mbps on the client adapter (we have 1gbps network, and can get 800 Mbps reliably) so in theory, even if that computer was trying to steal all available bandwidth, there should still be plenty over... That combined with the 'self healing' nature of the problem makes it hard for me to figure out where to look. Checking router logs shows nothing noteworthy, and running netstat, ping -t (ping an address continuously) and task manager on that computer doesnt show anything amiss at the time the problem is occuring.
Any ideas where to start troubleshooting this?
Thanks!