Continuous Linkdead

Started 23 May 2019
by pejaocb98
in Support Center
I've played on the server no issue since release. Ever since last night though I have been getting non-stop LD's. The record so far is being connected for all of 2-3 seconds. I have tried every proxy available to connect on my launcher, (EU1-3 and NA1-2). The longest I have maintained connection for tonight is maybe 3 minutes. The only info I really have right now (which is next to literally nothing) is that when I get DC'd, the second green circle goes, then first green circle goes red. Then the infamous "YOu have gone link-dead. Your client stopped receiving message from the srver. You have been disconnected"

What is happening and can anybody help me?
Thu 23 May 2019 5:25 AM by Clockwork
Sporadically for about a week or two? now we've been under DDoS attacks, not sure if your LDs are occurring directly at those times though.
Thu 23 May 2019 5:29 AM by pejaocb98
No it only started last night. I was able to play for 1-2 hours a time yesterday before experiencing an LD, but tonight (just before making this post) the longest I was connected for was maybe 5 minutes tops.
Thu 23 May 2019 5:32 AM by Clockwork
Please run CMD in your start bar and do a ping test on us while playing when you LD take a screenshot of what it says.

ping eu.playphoenix.online t- or -t (I can never remember sorry) also seek us out in our discord #support channel where smarter GMs than me can offer guidance
Thu 23 May 2019 5:35 AM by pejaocb98
Will do, thank you
Thu 23 May 2019 6:58 AM by rubberduck21
Clockwork wrote:
Thu 23 May 2019 5:32 AM
Please run CMD in your start bar and do a ping test on us while playing when you LD take a screenshot of what it says.

ping eu.playphoenix.online t- or -t (I can never remember sorry) also seek us out in our discord #support channel where smarter GMs than me can offer guidance

ping eu.playphoenix.online -t



should be correct
Thu 23 May 2019 7:03 AM by pejaocb98
I did the ping through cmd prompt with -t and never saw a difference even after LD. Acted like the connection never got terminated either as it continued to ping the server after daoc closed. Issue still hasnt been solved, and havent been able to get in contact with anyone except clockwork, so issue is not resolved...and I'd love to play as tomorrow is my last day before leaving for 2 weeks for work :/
Thu 23 May 2019 7:17 PM by Ashok
The easiest way to troubleshoot:

Use a different computer on same connection
Use a different internet connection on the same computer (like pairing with mobile)

This is not meant as solution but to narrow down the source and then moving on to the next steps whatever the results will be.

And please, don't say "that it did work 2 weeks ago".
It no longer does.

Your computer changed (Windows, AV and driver updates), your provider changed (DNS/routing tables & peering points), Phoenix changed (tunneled connection via Proxies).
We have to start somewhere and your own network is the only thing you practically have under full control.
Thu 23 May 2019 10:59 PM by Auranyte
I've had this issue since prior to the DDOS began (or was acknowledged atleast). Sometimes I can stay on for a few hours other times its every 2-5 minutes. It was killing my interest in playing, the DDOS finished it.

For awhile I thought it was bad node in the route between me and the server but my own VPNs suffered the same issue even after changing all of my networking equipment. (3 modems, 2 routers, 2 NICs) Something about the game seems to just randomly send "FIN RST packets" to my connection.
Thu 30 May 2019 2:11 PM by Delegator
I have had 4 LD in the 45 minutes since the restart today. Prior to the restart I was also getting lag spikes every couple of minutes (two left performance dots go red, all NPCs disappear, then they come back after ~5 seconds).

PING eu.playphoenix.online (104.27.134.174): 56 data bytes
64 bytes from 104.27.134.174: icmp_seq=0 ttl=59 time=12.056 ms
64 bytes from 104.27.134.174: icmp_seq=1 ttl=59 time=13.592 ms
64 bytes from 104.27.134.174: icmp_seq=2 ttl=59 time=10.959 ms
64 bytes from 104.27.134.174: icmp_seq=3 ttl=59 time=9.594 ms
64 bytes from 104.27.134.174: icmp_seq=4 ttl=59 time=16.923 ms
64 bytes from 104.27.134.174: icmp_seq=5 ttl=59 time=11.242 ms
64 bytes from 104.27.134.174: icmp_seq=6 ttl=59 time=11.527 ms
64 bytes from 104.27.134.174: icmp_seq=7 ttl=59 time=10.221 ms
64 bytes from 104.27.134.174: icmp_seq=8 ttl=59 time=9.586 ms
^C
--- eu.playphoenix.online ping statistics ---
9 packets transmitted, 9 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 9.586/11.744/16.923/2.182 ms
Thu 30 May 2019 2:24 PM by Delegator
Here's another set of pings right during a lag spike:

PING eu.playphoenix.online (104.27.135.174): 56 data bytes
64 bytes from 104.27.135.174: icmp_seq=0 ttl=59 time=12.503 ms
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
64 bytes from 104.27.135.174: icmp_seq=3 ttl=59 time=11.286 ms
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
64 bytes from 104.27.135.174: icmp_seq=6 ttl=59 time=10.577 ms
Request timeout for icmp_seq 7
Request timeout for icmp_seq 8
64 bytes from 104.27.135.174: icmp_seq=9 ttl=59 time=10.762 ms
Request timeout for icmp_seq 10
64 bytes from 104.27.135.174: icmp_seq=11 ttl=59 time=10.928 ms
^C
--- eu.playphoenix.online ping statistics ---
13 packets transmitted, 5 packets received, 61.5% packet loss
round-trip min/avg/max/stddev = 10.577/11.211/12.503/0.687 ms
Thu 30 May 2019 4:37 PM by Boltman
Running a traceroute might show you where the packets are dropping.
Fri 31 May 2019 2:14 PM by Delegator
Yup, traceroute is the better tool, and it shows something in my ISP's domain (outside my house but before their regional gateway). Here are bad and good, in quick succession. The * in the first one are timeouts, 2 of 3 times at stage 3 and 1 of 3 times at stage 4. Then I try after pinging to see if it looks better, and no timeouts.

Time to call the cable company. Oh joy.

traceroute to playphoenix.online (104.27.134.174), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 0.740 ms 0.415 ms 0.368 ms
2 96.120.70.153 (96.120.70.153) 109.119 ms 10.065 ms 31.850 ms
3 * 68.87.180.157 (68.87.180.157) 11.830 ms *
4 * be-31-ar01.needham.ma.boston.comcast.net (68.85.106.93) 42.523 ms 53.333 ms
5 76.96.121.242 (76.96.121.242) 82.986 ms * 22.519 ms
6 104.27.134.174 (104.27.134.174) 19.908 ms 42.433 ms 13.878 ms
$ ping playphoenix.online
PING playphoenix.online (104.27.134.174): 56 data bytes
64 bytes from 104.27.134.174: icmp_seq=0 ttl=59 time=14.351 ms
64 bytes from 104.27.134.174: icmp_seq=1 ttl=59 time=12.155 ms
64 bytes from 104.27.134.174: icmp_seq=2 ttl=59 time=17.226 ms
^C
--- playphoenix.online ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 12.155/14.577/17.226/2.076 ms
$ traceroute playphoenix.online
traceroute: Warning: playphoenix.online has multiple addresses; using 104.27.134.174
traceroute to playphoenix.online (104.27.134.174), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 0.627 ms 0.303 ms 0.281 ms
2 96.120.70.153 (96.120.70.153) 12.859 ms 58.752 ms 116.993 ms
3 68.87.180.157 (68.87.180.157) 11.915 ms 56.739 ms 61.027 ms
4 be-31-ar01.needham.ma.boston.comcast.net (68.85.106.93) 20.920 ms 14.591 ms 14.964 ms
5 76.96.121.242 (76.96.121.242) 25.017 ms 13.532 ms 15.096 ms
6 104.27.134.174 (104.27.134.174) 15.894 ms 11.498 ms 12.159 ms
This topic is locked and you can't reply.

Return to Support Center or the latest topics