Recent zone loading freezes, crashes, & failure to connect to server

[phiren]

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]

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]

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.