Frequently failing to connect to new zones

"

MaxTheLimit wrote:

I'd like to see what sort of results WinMTR comes back with to different locations. It's a bit odd to see the results depicted in the results so far. Such huge packet loss at every hop but the packet loss doesn't show on the destination results. There is a high value for the worst, so that could be a sign of problem somewhere along the way, but with none of the hops showing useful information, I'd like to see if a different route to a different destination yield similarly 'interesting' results.

Most of the time when I see MTRs like was posted (with a lot of packet loss in individual nodes but not destination) it's something with the router acting up. This is also often accompanied with the hops being out of order due to the way MTR asks for the nodes.

To get more technical, MTR sends out a specific packet with an increasing TTL (starting at 1) to identify each node. If these replies come back out of order, MTR doesn't really handle it well, and thinks the nodes are ACTUALLY out of order... which isn't the case... it's just mistaken identity on the node discovery portion.

But usually when these things go together, it's been the router acting up, or something in the ISP itself (like the gateway) acting up... but I've only seen one case of that due to a shoddy ISP with a horrible internal network and router setup. Once the issue was reported, the ISP fixed it.

But before getting to the ISP, I generally like to rule out local hardware issues. First step is usually the easiest which is to just power-cycle the thing. That's usually why the first thing the ISP does when you call them is to attempt to restart the devices (or ask you to). It's the easiest thing to do, and actually clears up quite a bit of the time.. so it's worth trying.

Doing more traces certainly wouldn't be a bad thing for comparison as well.

At least it hasn't killed you yet. Let us know how the results to the Texas location. Good luck!

I might have missed this since I didn't read the whole thread again, but why are you not using the California server?

Seems like you're near San Jose, and the PoE servers for California are in San Jose.... you'd likely decrease your hop count by 50%.

Try running a WinMTR trace to sjc.login.pathofexile.com and see how many hops it takes. I'm guessing it won't take more than 10 or so.. which is quite a bit less than you have now. Other problem I can see as a potential issue is the immediate latency leaving at the ISP level (3rd hop). Could just be jitter, or could be signs of other issues. Nothing to worry about yet, but I'd certainly keep an eye on it.

"

Slachi wrote:

Someone wanted me to run the MTS with another server. Whatever the issue was seems to have just gone away...

Ahh, that's right. I apologize. There are a lot of various connection threads going on at once, and as they get longer, they get harder to track properly without going back and re-reading the entire thread. Sorry for that.

Hopefully it was just a reset of the equipment, or an ISP issue that cleared up. Let us know if the problem returns and continue doing traces if it does. Hopefully with more data we can isolate an issue or through your own diagnostics can determine if it's simply an issue of needing to reset the hardware.

Good luck on your travels =]