Barnufus - Attempting to Reconnect

Hello! Can I add my issue into this thread or would it be more useful to put somewhere else?

I am consistently disconnecting around 5 minutes into games, trying US East, Central, and West servers to the same results. I am using an ethernet (powerline) connection but my housemate has the same issue on the wifi.

Here is our WinMTR readout:

Blockquote
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 10.0.0.1 - 0 | 1219 | 1219 | 3 | 17 | 123 | 25 |
| 96.120.70.217 - 2 | 1165 | 1151 | 9 | 19 | 87 | 31 |
| 68.87.152.205 - 2 | 1165 | 1151 | 9 | 19 | 106 | 14 |
| 96.110.22.85 - 2 | 1165 | 1151 | 11 | 22 | 161 | 15 |
|be-7015-cr02.newyork.ny.ibone.comcast.ne t - 2 | 1165 | 1151 | 17 | 29 | 98 | 40 |
|be-10396-pe01.60hudson.ny.ibone.comcast.ne t - 2 | 1165 | 1151 | 17 | 27 | 98 | 38 |
| 50.208.232.150 - 2 | 1165 | 1151 | 17 | 31 | 110 | 40 |
| ae1-br01-eqny8.as57976.ne t - 2 | 1165 | 1151 | 37 | 51 | 188 | 45 |
| et-0-0-2-br02-eqch2.as57976.ne t - 2 | 1165 | 1151 | 37 | 52 | 158 | 41 |
| et-0-0-1-pe02-eqch2.as57976.ne t - 2 | 1165 | 1151 | 37 | 49 | 188 | 43 |
| chi-eqch2-ia-bons-02.as57976.ne t - 2 | 1165 | 1151 | 39 | 50 | 139 | 42 |
| 24.105.62.129 - 3 | 1121 | 1096 | 37 | 46 | 169 | 43 |
|____________|||||||
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

For the other points you mentioned:

  • I can’t find QoS in my xfinity/comcast router admin tools
  • Router: ARRIS Group, Inc. model number TG3482G (Hardware Revision: 15, Processor Speed 3999.87 MHz, DRAM Total Memory 667… Flash Total mMemory 4857 MB - other info here if you need)
  • Internet Provider: xfinity/comcast

Hey, Barnufus! I just wanted to move you over to another thread so that we can look into this separate from the other reports. While we are seeing the issue mostly with Comcast & Spectrum, the most consistent thing across the reports were with Netgear routers specifically. The issue may be related, but I wanted to separate this so that we can gather more reliable data on the situation :slight_smile:

It looks like this is a modem, do you happen to have a router attached to the modem or is it just the modem? If another device is attached, is it a netgear router?

There is another slight variance compared the the other reports. The WinMTR tests are completely clean without any packet loss for the Netgear routers, while here, we are seeing packet loss after the home network.

| 96.120.70.217 - 2 | 1165 | 1151 | 9 | 19 | 87 | 31 |

Another concern is that the average latency on the home network is quite high reaching 17ms, which is very high even for a wireless connection and extremely high for a wired connection.

| 10.0.0.1 - 0 | 1219 | 1219 | 3 | 17 | 123 | 25 |

With this in mind, this will need to be referred to Comcast as there’s a consistent 2-3% loss throughout the test, which looks like mitigation or prioritization (such as QoS or WMM) of the connection packets being sent.

I have a few suggestions for you to try out and hopefully it’ll help out with the disconnections.

  • QoS Setting - This is not something that we can assist with directly, but try looking for the WMM (Wireless Multimedia) setting as well. Some devices may have one or the other, some may not have either setting. This will need to be referred to Comcast if you’re unable to find the setting.

  • Try a wired connection if wireless. If you are already wired, try a different cable if available.

  • Let’s try clearing out the TCP/IP & Winsock in case it may improve the latency on the PC network.

    1. Right click on your Windows Start Menu, and select “Command Prompt (Admin)” or just search for Command Prompt and right click, run as administrator.
    2. Now type in or copy and paste, “netsh int ip reset” Press Enter.
    3. Then do the same for “netsh winsock reset”

    Once it’s complete, you’ll need to restart the computer to complete the reset.

If it continues, please include a new WinMTR test until the disconnections occur.