Recent zone loading freezes, crashes, & failure to connect to server - Page 5

Slideonby · #1 09-05-2016, 11:03 AM

Ditto to Anowin

Abner · #2 09-05-2016, 11:53 AM

Back to not being able to even get to server select. I am thinking perhaps volume has an effect. Interested to find out what happens with Anowin with his tech visit.

rugerx · #3 09-05-2016, 01:58 PM

Exact same issues, ATT, could log in 1 out 5 attempts 5 AM CST, has become worse as population increased. Traceroutes show drops etc.

Cannot get back on now, sometimes cannot get to server select, no servers in select screen, once I made it to character select and it told me I was out of date on my patch, which I am not, as I patched this morning with new patch and logged in.

One thing to note, this morning when I downloaded the patch it took 2 seconds, I downloaded again to make sure it had not been updated and it was crawling, took 3 minutes to download.

phiren · #4 09-05-2016, 02:05 PM

I also noticed that it took about 5 minutes to download a 4.9MB package this morning. That would be from project1999.com though. I'm not entirely sure on the game's back-end architecture though and what servers are needed.

eqemulator.org obviously handles the log in stuff... but is there ANY reason for problems with project1999.com to be linked? In other words .. do we as players need successful traffic to both eqemulator.org and project1999.com at the point where we are having problems?

Tracing route to login.eqemulator.net [66.55.145.2]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms dsldevice.attlocal.net
2 23 ms 3 ms 8 ms lightspeed.rcsntx.sbcglobal.net [104.185.156.1]
3 5 ms 4 ms 4 ms 71.155.29.24
4 * * * Request timed out.
5 6 ms 7 ms 7 ms 12.83.80.233
6 7 ms 8 ms 7 ms gar25.dlstx.ip.att.net [12.122.85.233]
7 5 ms 5 ms 6 ms ae-9.r01.dllstx04.us.bb.gin.ntt.net [129.250.8.237]
8 5 ms 6 ms 6 ms ae-2.r23.dllstx09.us.bb.gin.ntt.net [129.250.6.128]
9 33 ms 33 ms 32 ms ae-3.r20.chcgil09.us.bb.gin.ntt.net [129.250.4.153]
10 48 ms 48 ms 49 ms ae-0.r25.nycmny01.us.bb.gin.ntt.net [129.250.2.167]
11 48 ms 48 ms 50 ms ae-2.r07.nycmny01.us.bb.gin.ntt.net [129.250.3.98]
12 * * * Request timed out.
13 53 ms 60 ms 53 ms vl23-br2.pnj1.choopa.net [66.55.130.53]
14 * * 52 ms ethernet1-2-2-c8-12-b2-1.pnj1.choopa.net [108.61.80.218]
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

phiren · #5 09-05-2016, 02:24 PM

Just to try to catch some of the hops that weren't showing .. I staggered it and ran a few more. The 4th hop only showed up once out of 4 traces.

Traceroute #2:

Tracing route to login.eqemulator.net [66.55.145.2]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms dsldevice.attlocal.net
2 5 ms 2 ms 2 ms 104-185-156-1.lightspeed.rcsntx.sbcglobal.net [104.185.156.1]
3 5 ms 4 ms 4 ms 71.155.29.24
4 * 7 ms 7 ms 70.143.193.158
5 9 ms 7 ms 7 ms 12.83.80.233
6 8 ms 9 ms 7 ms gar25.dlstx.ip.att.net [12.122.85.233]
7 6 ms 6 ms 5 ms ae-9.r01.dllstx04.us.bb.gin.ntt.net [129.250.8.237]
8 6 ms 6 ms 6 ms ae-2.r23.dllstx09.us.bb.gin.ntt.net [129.250.6.128]
9 32 ms 33 ms 37 ms ae-3.r20.chcgil09.us.bb.gin.ntt.net [129.250.4.153]
10 48 ms 48 ms 48 ms ae-0.r25.nycmny01.us.bb.gin.ntt.net [129.250.2.167]
11 48 ms 48 ms 47 ms ae-2.r08.nycmny01.us.bb.gin.ntt.net [129.250.6.209]
12 54 ms * 53 ms ae-1.choopa.nycmny01.us.bb.gin.ntt.net [128.241.2.250]
13 54 ms * * vl23-br2.pnj1.choopa.net [66.55.130.53]
14 * 51 ms * ethernet1-2-2-c8-12-b2-1.pnj1.choopa.net [108.61.80.218]
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Traceroute #3

Tracing route to login.eqemulator.net [66.55.145.2]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms dsldevice.attlocal.net
2 3 ms 2 ms 2 ms 104-185-156-1.lightspeed.rcsntx.sbcglobal.net [104.185.156.1]
3 5 ms 4 ms 4 ms 71.155.29.24
4 * * * Request timed out.
5 9 ms 7 ms 7 ms 12.83.80.233
6 9 ms 7 ms 7 ms gar25.dlstx.ip.att.net [12.122.85.233]
7 5 ms 5 ms 5 ms ae-9.r01.dllstx04.us.bb.gin.ntt.net [129.250.8.237]
8 6 ms 6 ms 5 ms ae-2.r23.dllstx09.us.bb.gin.ntt.net [129.250.6.128]
9 33 ms 33 ms 32 ms ae-3.r20.chcgil09.us.bb.gin.ntt.net [129.250.4.153]
10 48 ms 49 ms 49 ms ae-0.r25.nycmny01.us.bb.gin.ntt.net [129.250.2.167]
11 50 ms 50 ms 48 ms ae-2.r08.nycmny01.us.bb.gin.ntt.net [129.250.6.209]
12 56 ms 54 ms * ae-1.choopa.nycmny01.us.bb.gin.ntt.net [128.241.2.250]
13 53 ms 53 ms 53 ms vl23-br2.pnj1.choopa.net [66.55.130.53]
14 51 ms * * ethernet1-2-2-c8-12-b2-1.pnj1.choopa.net [108.61.80.218]
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.
~~~~~~~~~~~~~~~

Traceroute #4

Tracing route to login.eqemulator.net [66.55.145.2]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms dsldevice.attlocal.net
2 8 ms 10 ms 14 ms 104-185-156-1.lightspeed.rcsntx.sbcglobal.net [104.185.156.1]
3 5 ms 4 ms 4 ms 71.155.29.24
4 * * * Request timed out.
5 8 ms 7 ms 7 ms 12.83.80.233
6 7 ms 7 ms 7 ms gar25.dlstx.ip.att.net [12.122.85.233]
7 5 ms 5 ms 6 ms ae-9.r01.dllstx04.us.bb.gin.ntt.net [129.250.8.237]
8 6 ms 5 ms 10 ms ae-2.r23.dllstx09.us.bb.gin.ntt.net [129.250.6.128]
9 56 ms 36 ms 32 ms ae-3.r20.chcgil09.us.bb.gin.ntt.net [129.250.4.153]
10 48 ms 48 ms 48 ms ae-0.r25.nycmny01.us.bb.gin.ntt.net [129.250.2.167]
11 48 ms 51 ms 50 ms ae-2.r07.nycmny01.us.bb.gin.ntt.net [129.250.3.98]
12 55 ms 101 ms 156 ms ae-0.choopa.nycmny01.us.bb.gin.ntt.net [128.241.2.202]
13 * * 55 ms vl23-br2.pnj1.choopa.net [66.55.130.53]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

xrabbitv · #6 09-05-2016, 03:27 PM

Hey ATT...Fix whatever you all caused !!!

Nilstoniakrath · #7 09-05-2016, 03:37 PM

The problems I have logging in are the same on both project99 and the vanilla EQEMU server list.

But if I do anything else on the internet, no problem.

So the issue is accessing EQEMU (not just project99) via AT&T.

phiren · #8 09-05-2016, 03:59 PM

Can you other AT&T users open up command prompt .. do a:
tracert login.eqemulator.org >eqtrace.txt

It will output the file "eqtrace.txt" in whatever directory you are in .. usually:
C:\Users\<yourname>\eqtrace.txt

I did a few different ones staggered:

tracert login.eqemulator.org >eqtrace111.txt
1 minute later
tracert login.eqemulator.org >eqtrace222.txt
1 minute later
tracert login.eqemulator.org >eqtrace333.txt
1 minute later
tracert login.eqemulator.org >eqtrace444.txt

See if you notice any similarity in the hops.

The hop in between my 3rd and 5th .. 70.143.193.158 was a 25% 'success' in traceroute. Could be a few reasons .. but 25% is about the success rate of logging in. If all you AT&T users are being routed through that IP address, and it's flaky, that could be the source.

#3 Hop: 5 ms 4 ms 4 ms 71.155.29.24
#4 Hop: 4 * 7 ms 7 ms 70.143.193.158
#5 Hop: 5 9 ms 7 ms 7 ms 12.83.80.233

In other words .. if you are AT&T and do a traceroute .. it would be interesting to see if we are ALL getting routed through:
71.155.29.24 -> 70.143.193.158 -> 12.83.80.233
Most likely it would be your 3rd / 4th / 5th hops .. but it might be different #s depending.

If you are getting a * * * * * between the 71.155.29.24 hop and the 12.83.80.233 hop , that might be telling it's the source. How to get that fixed is a different problem. Hopefully AT&T knows it's broken or having problems and fixes it soon on their own.

Or it could just be normal that 70.143.193.158 doesn't respond to traceroutes *sometimes*... although that would be weird.

phiren · #9 09-05-2016, 04:56 PM

Quote:

Originally Posted by phiren [You must be logged in to view images. Log in or Register.]

Can you other AT&T users open up command prompt .. do a:
tracert login.eqemulator.net >eqtrace.txt

It will output the file "eqtrace.txt" in whatever directory you are in .. usually:
C:\Users\<yourname>\eqtrace.txt

I did a few different ones staggered:

tracert login.eqemulator.net >eqtrace111.txt
1 minute later
tracert login.eqemulator.net >eqtrace222.txt
1 minute later
tracert login.eqemulator.net >eqtrace333.txt
1 minute later
tracert login.eqemulator.net >eqtrace444.txt

See if you notice any similarity in the hops.

The hop in between my 3rd and 5th .. 70.143.193.158 was a 25% 'success' in traceroute. Could be a few reasons .. but 25% is about the success rate of logging in. If all you AT&T users are being routed through that IP address, and it's flaky, that could be the source.

#3 Hop: 5 ms 4 ms 4 ms 71.155.29.24
#4 Hop: 4 * 7 ms 7 ms 70.143.193.158
#5 Hop: 5 9 ms 7 ms 7 ms 12.83.80.233

In other words .. if you are AT&T and do a traceroute .. it would be interesting to see if we are ALL getting routed through:
71.155.29.24 -> 70.143.193.158 -> 12.83.80.233
Most likely it would be your 3rd / 4th / 5th hops .. but it might be different #s depending.

If you are getting a * * * * * between the 71.155.29.24 hop and the 12.83.80.233 hop , that might be telling it's the source. How to get that fixed is a different problem. Hopefully AT&T knows it's broken or having problems and fixes it soon on their own.

Or it could just be normal that 70.143.193.158 doesn't respond to traceroutes *sometimes*... although that would be weird.

Crap my bad guys -- it's:
login.eqemulator.NET not .org

Anowin · #10 09-06-2016, 11:26 AM

I was able to log on last night after a few failed attempts, as before. I was also able to gate and zone into Qeynos Aqueducts and N. Qeynos three times. We will see what happens today. If it doesn't go well, I'll update you all after the AT&T tech comes to my house on Wednesday.