DROPPED in HL Pick screen

Technical Support
Had this issue last TL game for no reason was doing fine no ms drop or anything then out of nowhere it said i was dropped and my only option was exit to desktop after relaunching the game the option to rejoin showed but was blacked out then the menu disappeared and i could que while already in game.
DirtyD,

I checked your tests out, and whatever's happening there appears to be happening between your computer and router or modem. Can you power cycle your connection, update your network drivers and router firmware (you'll need to look firmware updates for your modem up online), and if all that fails swap to ethernet? It could just be unstable wifi, or something not being handled well by the drivers. If none of that helps, send a new MTR and I'll see if anything's changed.

Did all of that that I could (no firmware updates available for modem and I am on Ethernet)

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 0 | 1837 | 1837 | 0 | 52 | 985 | 0 |
| 10.80.184.1 - 3 | 1677 | 1637 | 5 | 48 | 1003 | 7 |
| 100.127.71.10 - 3 | 1681 | 1642 | 6 | 58 | 1014 | 8 |
| 70.169.74.150 - 3 | 1697 | 1662 | 6 | 59 | 1017 | 11 |
| langbprj01-ae1.rd.la.cox.net - 3 | 1677 | 1637 | 18 | 72 | 1029 | 19 |
| 70.191.61.10 - 3 | 1689 | 1652 | 20 | 71 | 992 | 24 |
| 37.244.0.35 - 3 | 1689 | 1652 | 68 | 122 | 1077 | 70 |
| 24.105.31.5 - 3 | 1681 | 1642 | 69 | 120 | 1078 | 70 |
| 37.244.1.103 - 3 | 1693 | 1657 | 70 | 125 | 1080 | 72 |
| 24.105.62.129 - 3 | 1673 | 1632 | 59 | 116 | 1048 | 60 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
All righty Augustus, we'll go with that from here!

As for what's in that link, what's being said here is typically only true for networks where some form of denial of service mitigation is taking place. This kind of mitigation is usually something you see at very high levels of packet loss - usually an about-even percentage, or a simple fraction (like 1/3 or 33%). Usually I start thinking about this as a possibility when we see 30% or more packet loss. You have to think about the loss with the symptoms you're seeing, too, because with 50% or more packet loss as shown in those examples - you typically wouldn't be able to connect to our servers at all (or stay connected very long.)

In this case, however, we're seeing smaller amounts of loss which are normal for your someone with your symptoms. They're seemingly random amounts, affecting certain nodes throughout the test. When you see that, what you want to focus on usually is the first thing you see packet loss at and get that resolved. If it persists, you go on to the next thing that shows packet loss.

The last hops won't always show packet loss in our tests because we mask our servers from certain packets to protect against Denial of Service attacks. That's also why your test is covered in timeouts at the end. You can only see most of the test - not all of it, because past the last hop you see we do 100% mitigation of these types of test packets. People like to exploit ICMP packets and such to ruin people's day, so unfortunately we can't have nice things. :<

In our case, we don't necessarily care what the exact loss % is. Our problem is more that there is a somewhat significant amount of packet loss. One thing you can do to test what the problem is would be using a VPN client. We can't suggest exact clients to you or support how to set them up, but you seem pretty tech savvy based on the research you were doing. If the VPN fixes the problem, it's probably the connection path and you need to talk to your ISP about it. If not, it could be your modem causing the problem and you'll need to troubleshoot that (with your ISP if you're renting it.)
Now let's talk more about DirtyD's new test.

Based on the changes I see there, I'm thinking the problem could possibly be your router itself. You can see in the new test that the packet loss in the first hop seems to be missing, but you still have an extremely high WRST (Worst) and pretty high AVRG (Average) latency at that hop.

This points to a failing router or network card - or potentially just a bad ethernet cable. What I'd try, in order:

    1. Bypass your router entirely to see if it still happens on just the modem. If this fixes it, it may be RIP for your router. You can try factory resetting the router to fix it but it doesn't always work.
    2. Get a new ethernet cable to wire into your router if it fails. In some cases a bad cable can do this.
    3. If that doesn't work, you can try troubleshooting the NIC itself - just do step 3 at this link, you've already handled the others.


If none of that helps, let's grab a new MTR with you wired into your modem to look for other problems.
Alright I used a VPN, and here are the results of the test:

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 172.18.12.1 - 0 | 601 | 601 | 74 | 78 | 148 | 75 |
| 107.170.32.254 - 0 | 601 | 601 | 75 | 80 | 138 | 76 |
| 138.197.248.154 - 1 | 597 | 596 | 75 | 80 | 151 | 76 |
| nyk-b6-link.telia.net - 1 | 585 | 581 | 75 | 78 | 138 | 76 |
| nyk-bb1-link.telia.net - 0 | 601 | 601 | 75 | 89 | 250 | 77 |
| nyk-b3-link.telia.net - 0 | 601 | 601 | 75 | 79 | 129 | 75 |
| blizzard-ic-322963-nyk-b3.c.telia.net - 0 | 601 | 601 | 76 | 80 | 145 | 76 |
| 37.244.3.33 - 0 | 601 | 601 | 98 | 101 | 201 | 98 |
| No response from host - 100 | 121 | 0 | 0 | 0 | 0 | 0 |
| 37.244.1.103 - 0 | 601 | 601 | 99 | 104 | 161 | 107 |
| 24.105.62.129 - 0 | 601 | 601 | 98 | 103 | 202 | 100 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

There's a very small amount of loss there in the middle, but it's significantly better than my regular connection. So in this case, it's an issue with the ISP then?
Augustus,

That would be my best guess based on everything you've presented. It looks like you have much more minor packet loss. There are still some potential issues around here:

| 138.197.248.154 - 1 | 597 | 596 | 75 | 80 | 151 | 76 |
| nyk-b6-link.telia.net - 1 | 585 | 581 | 75 | 78 | 138 | 76 |

But they're significantly better than on your normal connection path. You can try a couple different VPNs or servers on your VPN and see if it improves further. Each server location will take you to a different location before going towards our servers, which could result in better routes. In the mean time, you can contact the ISP and let them know about the loss you're seeing. You may need to escalate your call to speak with a higher tier technician - most ISPs don't teach their front line reps how to read MTRs or pathping tests and will just have you run speed tests, which don't help for your purposes.
Alright I spoke with a Comcast rep, and apparently according to him there's an issue with my modem. I'll get a replacement soonish, and hopefully that'll fix the issues.
Understood. Let's get a new MTR from you if you still have problems after the modem swap and we can pick back up from there. Hopefully just swapping the hardware gets you fixed up, though!
Hi, an update :)

After raging at Rogers ISP, they looked into it and they had given me a wrong Modem/Router.

Once it was replaced, I quickly noticed that in my MTR didn't have the sporadic ping to my router anymore.

and subsequently, haven't had the drop issue any more :)

While my issue is fixed, I still think HOTS is BRUTALLY punishing towards people who genuinely disconnect for a milisecond, during draft...

Join the Conversation

Return to Forum