I doubt that's the issue. Its far more likely that he just pasted an irrelevant portion of the log. His next post did have relevant errors.

towbes, if there's an issue it's likely nothing you can fix on your system. Its likely to either be an EQEmu bug or an issue with your ISP / your ISP's ISP (Tier1 networks)

Too many missing files probably slowing down connecting too much.

H

That's the message the client gives when it timesout negotiating the session. For some reason your client never saw the reply from P99 and quit. The rest of the log is 100% irrelevant.

I'll focus more on packet logs and see if anything turns up.

towbes, I've been having a very similar issue as you since yesterday. Took me about 20 attempts to get logged in on my character. NGREP showed that my packet loss was significant. Sometimes about 30% of the expected UDP packets never arrived.

I've been having the issue with both P99 and the loginserver, which suggests its not P99's issue, but instead possibly due to XO.net or NTT.net.

Failure packet dump (gist.github.com)
Success packet dump (gist.github.com)

Heroes of the Storm has been having widespread problems for users that route through XO.net so this might be another game that is affected by XO's shitty network nodes.
http://us.battle.net/heroes/en/forum/topic/18000364944
http://us.battle.net/heroes/en/forum...6329?page=2#23 (blue post on the issue)

Can you paste your results from WinMTR using host 66.55.145.2 to this thread?

Mine for example are...

Would like to add that I suspected XO.NET to be the root issue. NordVPN has a server (US2) which allows me to entirely bypass ptr.us.xo.net with a slightly longer route. (still routes through ntt.net).

Issue resolved immediately after that. My ping is 15ms higher, sure, but I'm not disconnecting during almost every attempt to connect to 66.55.145.2; virtually zero issues at all so far.

Wisteso, thank you for that information, here's a dump of WinMTR, same exact servers, although I obviously have some issues before it crosses the Pacific Ocean as well. But having 27% loss at a server right before the gameserver is probably not helpful at all.

And another when I utilize Singapore VPN, now it's 87% loss at that ae-8 node in NYC. However I am connected and successfully zoned twice. Still having some crashes on zone, and timing out past char select, packets showing my client sending data to server, but getting nothing back.

Guys,

There are idiosyncrasies about the way that MTR (and, by extension, WinMTR) reports packet loss. 87% packet loss to ae-8.r23.nycmny01.us.bb.gin.ntt.net (129.250.2.148) means nothing if you consistently get 9% to a node past that. It just means that the router is de-prioritizing ICMP ECHO but forwarding normally.

Here's my MTR report to 66.55.145.2:

We know that 66.55.145.2 doesn't respond to ICMP and speculate that it's hop 16. We can't know that for sure, since it could be 128.241.2.250 refusing to forward upstream ICMP to us. But presumably once we've arrived at 129.250.* network there won't be much additional loss to 66.55.145.2, so the average packet loss to the most reliable node in this network is our most accurate assessment of the packet loss.

I'll just use the farthest visible hop as it's about the same:

So the real packet loss here is 0.4%.

The problems I am seeing are not caused by packet loss to the server. According to Wireshark, both Emerald Jungle and Trakanon's Teeth use 66.55.145.2, and I have problems only in TT. If I had a terrible connection to that IP, then I'd see the same issues in both zones.

Wisteso, you may have slightly more packet loss than I do, but not significantly so.

towbes, you are seeing packet loss issues, but the problem shows up very early in your network route. Run some manual pings like I did in my example; are you seeing any consistently low loss to any hops along the way? Either you're looking at an anomaly (maybe your VPN hates ICMP) or else you're getting loss at the third hop. Try pinging with TCP to an open port with tcping if you have access to linux.

I had the same issue with TT, after about 30s in zone ping spiked up to 4k then eventually d/ced me. I was however able to log back in eventually and make my way to the seb orb and zone in. That makes sense on the MTR analysis. I know I'm seeing packet loss, I'm not questioning that. I just think the server is severing the connection too quickly, and the client is missing the message that the connection was severed so it just keeps trying. What's especially frustrating is circumstances where the character client never loads into a zone (just sits at the previous zone screen with the busy cursor), however when you manually close the client and attempt to log back in, it says you still have a character in zone. So what's happening there? Why isn't the client being sent messages telling it that it zoned? Probably the only way to pinpoint the issue is to setup a local server, and monitor the connection to that local server to find out what it's supposed to look like, and use something like burpsuite to kill certain packets and find that one that is causing the problems. (Not even sure it would be capable of performing quickly enough to allow a game session to occur though, just theorizing)