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

[Vitrophyre]

I've been having serious issues the past couple days with freezing during zone loading/extremely long loading time, crashes during loading, and at least a 10min multiple failure to reconnect to server/login. Anyone else having these issues? Will be reinstalling tonight.

[Nilstoniakrath]

Yes, been having these issues the last three days now. Sometimes hangs on log in, sometimes server screen blank, sometimes says no internet connection (even though I have no problems surfing the net), sometimes times out, sometimes freezes on char select screen, sometimes it tells me my patch files are out of date (so I re-load), etc.

I also crash when zoning, a lot.

[Abner]

Me too. I locked up zoning and have been trying to get back in for like a half hour.

Another thread in the wrong forum stated that everyone with the issue seems to be an ATT customer. I am as well.

[Vitrophyre]

What the hell!? I'm AT&T too!

Anyone know what's going on here?

[Vitrophyre]

Update: Reinstalled game, acted fine for ~5 zone loads, then crashed again. Switched to my iPad wifi with Verizon and it's been great ever since.

If you're having this issue, please post here so the admins can see and escalate.

Thanks,

[MiRo2]

Ensure that you aren't streaming anything, or using anything that takes up bandwidth. I get the same locking up when zoning or loading log in screen, when my youtube loads the next video, or I am watching netflix.

[Nilstoniakrath]

Not doing anything else online, such as YouTube, still crash randomly and often, over the last three days... even before the xp bonus kicked in

[Merekai]

I'm also having terrible problems with this issue, even when the client is the only thing I have open.

[Vitrophyre]

Ensure that you aren't streaming anything, or using anything that takes up bandwidth. I get the same locking up when zoning or loading log in screen, when my youtube loads the next video, or I am watching netflix.

No changes in game play operations over the past 6 months. I run a solid rig with nothing in the background. This is either a virus, internet, or server issue. My McAfee provided by AT&T comes up clean.

I find it very interesting one user says AT&T customers are having this problem. I've had AT&T for years, 140gb of 600gb usage for month, and have never had problems like this.

If you're in the field and might have some insight, please speak up.

[LexPD1145]

This has just started for me last couple days. I have all the same issues and using Att home internet as well. During some parts of the day its ok, other times its really unplayable. I have played for ages before with no issues, if I switch to my Verizon mobile data, which is limited, all the issues go away.

[Kickin Snake]

Same here, play for hours and zone fine, then freeze on zone and can't connect to server. When I do, there's no servers on the list. AT&T also.

[Crede]

Confirmed as well, this is definitely an ATT issue.

Guess it gives me an excuse to be productive IRL today...

[Vitrophyre]

This has just started for me last couple days. I have all the same issues and using Att home internet as well. During some parts of the day its ok, other times its really unplayable. I have played for ages before with no issues, if I switch to my Verizon mobile data, which is limited, all the issues go away.

Those of you experiencing this issue with AT&T, where are you located?

I'm on the north side of Houston in Texas.

[Crede]

Those of you experiencing this issue with AT&T, where are you located?

Northern IL

[LexPD1145]

South Carolina, also if its of any note sometimes when I'm trying to log back in, the server selection screen is blank. I have also had on a couple of occasions now my char. fail to load and get an error that my spell list is not current. This is not the case but I did download them again anyway.

[danceparty]

yep, same issues. to be exact...lots of zone crashes where i had not had zone crashes before; server screen blank and cannot log in. I am an AT&T Uverse customer.

[Abner]

Atlanta Metro - ATT UVerse - It just started a few days ago.

[Abner]

I wish someone that understands all this stuff could help us know what to do or who to complain to. And what to say to the person we complain to. I have been trying to log in for like 45 minutes now.

[Thugnuts]

I'm having this issue as well. Frequently either fails trying to login, or I make it to server select screen and there's nothing there.

Also, I crash 100% of the time when camping.

ATT Uverse customer.

[Abner]

Over an hour of random failures. I give up for a bit. /sigh

[razzulx]

Been having connection issues for about 1 month now, it happens when I zone or try to login. It seems like the server is trying to return packets that are failing causing the connection to be lost, making it so you cant login or never finish zoning.

Example of problem.

I try to sign into the login server and no servers will show. If i continue to try to log in they eventualy show up. When they do show up, and I click login to P99, sometimes it will give me a connection error or timeout, If I persist and keep trying in about 5-20 trys it will let me connect to the server.

At this point it still has a chance to not load when selecting your character, It will start loading the world and then never load the zone, making you have to try all over again after closing the program.

Once I am logged into the server, I can be on all day long with zero problems as long as I dont zone, but as soon as I zone there is a great chance going LD and getting stuck zoning, then once again have to do the login BS again.

Skype / Mumble / Other games / Web, all work fine with zero issues. I have restarted modems/routers , cleared my DNS, changed my DNS, checked my EQEMU hosts file to make sure its pointing to correct login server, tried a new install of titanium, all have the same issue. Starting to think it might not be at my end.

Been playing for over a year and a half with zero problems untill about 1 month ago.
Its making the game alot less fun to play when you go link dead all the time :(.

[Abner]

Preach it brother Razz. :(

[Mendo]

I'm having a tough time logging in as well. I freeze sometimes on zoning then can't log in.
I'm on ATT in California

[Abner]

I can't get past server select. It's either empty (mostly) or it fails logging in. What has ATT done to us?

[Slideonby]

Same problems. Been going on for a few days. ATT in Dallas Texas area.

[Slideonby]

BTW, I switch to mobile hot spot and it works fine.

[Harshmallow]

Been having connection issues for about 1 month now, it happens when I zone or try to login. It seems like the server is trying to return packets that are failing causing the connection to be lost, making it so you cant login or never finish zoning.

Example of problem.

I try to sign into the login server and no servers will show. If i continue to try to log in they eventualy show up. When they do show up, and I click login to P99, sometimes it will give me a connection error or timeout, If I persist and keep trying in about 5-20 trys it will let me connect to the server.

At this point it still has a chance to not load when selecting your character, It will start loading the world and then never load the zone, making you have to try all over again after closing the program.

Once I am logged into the server, I can be on all day long with zero problems as long as I dont zone, but as soon as I zone there is a great chance going LD and getting stuck zoning, then once again have to do the login BS again.

Skype / Mumble / Other games / Web, all work fine with zero issues. I have restarted modems/routers , cleared my DNS, changed my DNS, checked my EQEMU hosts file to make sure its pointing to correct login server, tried a new install of titanium, all have the same issue. Starting to think it might not be at my end.

Been playing for over a year and a half with zero problems untill about 1 month ago.
Its making the game alot less fun to play when you go link dead all the time :(.

:eek::eek: I am facing this same exact issue. Did not previously have issues until recently... I am NOT an ATT customer; instead a local internet provider (more regional).

[mythias]

Every problem/symptom that is being described is happening to me. AT&T Indiana.

Note* It has only started a couple of days ago

[HtotheK]

start comparing your traceroutes to 66.55.145.2.... i bet you'll find the common denominator....

Looks like server is hosted at gameservers.com which is hosted behind choopa which is having an issue their connectivity to certain providers (mainly att).... this is just a guess.


edit: looks like it might finally be fixed... it's working on every attempt now.

[LexPD1145]

Not for me anyway still getting blank server screens etc

[LexPD1145]

Still having all the same issues this morning after patch, so still not fixed.

[Slideonby]

Now I am getting spells files outdated error message....

[Abner]

OK this morning I got in. But I got in yesterday morning too. SO either it's fixed or the volume of people logged on has an effect. /ponder But I got RL stuff to do now /shrug

[Slideonby]

Patch installed. Got on and was able to zone a time or two ... then game froze when zoning. Was hoping it was fixed.

[Slideonby]

Blank server screen....

[west42074]

Also AT&T Uverse customer (which I regret). Past few days I have been having all the same issues - freezing/crashing on zone loads, sometimes getting blank server select screen, even after today's V43 patch.

[Anowin]

Exact same problems here. I have an AT&T tech coming to the house on Wednesday, as I have noticed some coincidental slowness in browsing as well. But, never had a problem until a few days ago. Whether in windowed mode or not, attempting to log in I get either:

1) After typing password, I get "logging in to server...", and then a pop up stating there was a problem and could not log in, or;

2). The password is accepted and I can log in to the server select screen, but it is blank/black with no severs to select; or

3). I get all the way to character select (after an inordinate loading time), but when I click "enter world" it freezes/never takes me into the world, and I have to end task; or

4). I get all the way in, finally, and can play (with some subtle loot lag/ghosting which never used to occur), but I get stuck zoning - it takes longer than normal for the red "LOADING, PLEASE WAIT..." to come up in the chat bar, and then it just stays on that screen. I never actually get kicked back to the log in screen; or

5). On extremely rare occasions, I can play and actually zone once or twice after long zoning times, but eventually I freeze on zoning.

[HtotheK]

Yeah --- sorry... last night it was doing a lot better around 1 am cst... guess it's back to having issues.

[mythias]

Of two of the scenarios mentioned ... the frozen load screen and the blank server select screen

[Slideonby]

Ditto to Anowin

[Abner]

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.

[Vitrophyre]

:eek::eek: I am facing this same exact issue. Did not previously have issues until recently... I am NOT an ATT customer; instead a local internet provider (more regional).

I think this may have a different root cause since it has been been happening to you for closer to a month. My issue began out of nowhere about 3 days ago.

Have not tried the new patch from this morning but reading this thread it sounds like it did not resolve the issue for some people.

[Splade]

Having the same issues as everyone itt. And I use att as well, started 3 days ago. Sometimes the game works fine (like 1\10) times but the rest it crashes or freezes or there's a blank server select screen

[phiren]

+1

Am also AT&T U-verse, North Texas area, and began experiencing the problems few days ago. Exact same everything.

Blank server select screen IF i can even get past the username/password screen .. and then IF I get past the username/password screen, and see a server select screen .. there's still a 50% chance I'm going to get a "server error", or my character select screen is blank and I gotta start all over again.

Very interesting problem that this would be just for AT&T Internet users across the country though. If the problem was isolated to a specific region of AT&T customers, that would make more sense.

If I do a traceroute from my computer to eqemulator.org or project1999.com or google.com ... like 10 of my 15 hops are ****'d out. So it's tough to say.

EVERYTHING else about my Internet works fine. EQ doesn't need much bandwidth at all. Streaming things doesn't make a difference.

Very very weird problem and hard to diagnose/troubleshoot/resolve. It would make more sense if you couldn't get in at all.

Any thoughts from the GMs / Server Admins?

Would gladly set up a TeamViewer session or something if any *GM* wants to poke around. Or some of us are probably pretty tech savvy .. let us know what we should be doing?

What ports are needed open to where?
What should we be tracerouting?
etc / etc

~Phiren

[rugerx]

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]

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]

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]

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

[Nilstoniakrath]

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.

[Vitrophyre]

Any thoughts from the GMs / Server Admins?

~Phiren

Wanted to let you guys know I spoke with Sr. Guide Braknar last night, and followed his request to PM him a link to this thread. Hopefully we'll have some feedback from the team soon.

As an aside, if you've never thought about donating and can afford to, please help support the server by donating through their paypal account.

Thanks

[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.

[Abner]

I tried the tracert to the eqemulator as well and got the same timeouts after the choopa.net stuff:


13 * 49 ms 49 ms vl23-br2.pnj1.choopa.net [66.55.130.53]
14 * 51 ms 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.

[PerroDeAqua]

This started happening to me a few days ago

[Erica]

10 91 ms 91 ms 91 ms vultr-ic-318452-nyk-b2.c.telia.net [62.115.149.39]
11 * * * Request timed out.
12 91 ms * * ethernet1-2-2-c8-12-b2-1.pnj1.choopa.net [108.61.80.218]
13-30 * * * Request timed out.

This might have happened a couple times in the past, but never this bad. I've been experiencing it since Friday I believe. Today it is even worse than previous days.

If I finally get on I'm fine unless I zone, then I need to cross my fingers.

[EQBallzz]

How are you guys getting that to work? I get "unable to resolve target system name login.eqemulator.org". It works when I just do eqemulator.org but that login prefex isn't working.

That being said I'm seeing the same timeout using just eqemulator.org when it hits ae-0.choopa.nycmny01.us.bb.gin.ntt.net and v1203-cr1.ewr3.choopa.net. I'm also using ATT Giggapower service. I been having this issue all weekend and can't log in today either.

[herb_gotti]

Same thing is going on with me. It seemed to get worse today after I did the file update for the patch. It was working decent until an hr into the game. Now I can't even get back into the game. I too am an AT&T user.

[EQBallzz]

BTW, I called the "choopa" hosting service tech support and they said their servers don't respond to pings or tracert commands so would probably show as a timeout or question mark but he also said if I didn't have an account with them they couldn't provide me technical support so who knows.

[Sactar]

Having same issues here as well with server screen and zone crashes. Is worse today then last couple of days. I also have Att in TX

[phiren]

The "Choopas" are going to be fine in my opinion. Those aren't AT&T.. and if the "Choopas" were the problem ... EVERYONE would probably have problems right now. But since this seems to be an AT&T U-verse problem ... it's most likely a problem with the hops that are AT&T related... "before the Choopas" :D

In other words your internet traffic goes from:
Your router -> AT&T stuff -> Choopas (Probably where eqemulator is hosted)

Everyone else who plays P99 would go:
Their Router -> Their internet company's stuff -> Choopas (Probably where eqemulator is hosted)

So the problem is going to be somewhere in the "AT&T stuff" hops

[phiren]

You AT&T guys -- I'm moreso curious about your first 10 hops -- because that's all AT&T related stuff.

I'm particularly curious if you are seeing these 3 in your first 10-15 hops:
71.155.29.24 <-- seems fine
70.143.193.158 <-- this is the one I think is the problem .. but could really only confirm if other people see it too, might have to run a few iterations of a staggered tracert like i suggested
12.83.80.233 <-- seems fine

[phiren]

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

[dirtynumbangel333]

AT&T customer here as well.
Having issues with the no internet connection error, or the Server list not populating, or not allowing me to log in, or characters being gone / the patch update message.

I have updated after today's patch, and have managed to log in once, but when I camped to try to change toons, it crashed and has been right back to the previously stated issues.

[phiren]

Well actually weird new troubleshooting problem discovered by accident.

Sometimes when I ping:
login.eqemulator.net

it says ping request could not find host

I tried changing up my eqhost.txt from:
[LoginServer]
Host=login.eqemulator.net:5998

to:
[LoginServer]
Host=66.55.145.2:5998

Thinking that might be it -- but still no dice. Definitely still seems like some kind of routing server @ AT&T is broken

[qualia]

Well actually weird new troubleshooting problem discovered by accident.

Sometimes when I ping:
login.eqemulator.net

it says ping request could not find host

I tried changing up my eqhost.txt from:
[LoginServer]
Host=login.eqemulator.net:5998

to:
[LoginServer]
Host=66.55.145.2:5998

Thinking that might be it -- but still no dice. Definitely still seems like some kind of routing server @ AT&T is broken

im on att. been super slow all day

[phiren]

im on att. been super slow all day

Well once you are in, you are pretty much in. I just sat in the same zone for like 2 hours straight. The problem is GETTING IN... and then surviving zoning.

I'm assuming when you zone, your computer connection tries to talk to the login.eqemulator.net server again .. and since AT&T isn't routing properly.. the communication breaks, and you get a lockup. But if you are in the same zone, it never really bothers to check with login.eqemulator.net .. no reason .. or it does occasionally but doesn't care.


~Phiren

[phiren]

Bottom line is -- some server at AT&T is broke. Knowing how these companies are set up .. I'm almost positive they KNOW there's a problem through automated ticketing.

Also knowing AT&T , I'm guessing they will get it fixed this week.

My internet went down for 5 days a few months back .. and learned they don't like to do the technical stuff on the weekends.

I wouldn't be surprised if this is magically resolved by the end of next week.

All we can do is run tracert's and try to find the broken server FOR THEM.. and then find someone at AT&T who cares/knows what we are talking about.

~Phiren

[qualia]

Well once you are in, you are pretty much in. I just sat in the same zone for like 2 hours straight. The problem is GETTING IN... and then surviving zoning.

I'm assuming when you zone, your computer connection tries to talk to the login.eqemulator.net server again .. and since AT&T isn't routing properly.. the communication breaks, and you get a lockup. But if you are in the same zone, it never really bothers to check with login.eqemulator.net .. no reason .. or it does occasionally but doesn't care.


~Phiren

i have been phone tethering in the mean time... better than 250ms

[Thugnuts]

Surely we have at least one techbeard on P99 who works for AT&T?

Hopefully he's on the trail!

[Abner]

I got in last night. I stayed on the same character (Wiz) most of the night scared to switch toons. I zoned and ported probably 20+ times and never crashed /hooray although one time it took like 4 minutes.

Near the end I tried switching toons and that worked too. We'll see what tomorrow brings!

[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.

[mythias]

It seems like all the symptoms that I have been having disappeared (knock on wood) after yesterday afternoon ... haven't had trouble yet

[EQBallzz]

I thought it was fixed for me also yesterday afternoon after applying the patch. Thing were working fine and I was zoning np until late in the evening..zoned into Sol A and locked up. Had to force close the game and the login issues started up again. Took about 10 minutes of the same errors and such trying to log back in before getting back in again.

[phiren]

no one wants to jinx it and say it eh?

[Vitrophyre]

no one wants to jinx it and say it eh?


Haha okay fine, IT'S FIXED!! ;D

We did it P99.

Safe travels everyone!

[Nilstoniakrath]

<Knocking on wood>

Played all night tonight, switched chars a lot and zoned a lot, no problems at all, so I would say that something got fixed, very happy, thank you devs and/or whoever got this solved

[getoffmylawn]

I crashed to login screen 3 times tonight. same as before. I crashed in my last grp tonight as our ivu wore off and had to CR. its bad when your group wipes. Extra bad when you wipe and then crash to login screen waaahhh.

edit

Make that back to back crashes soo as I logged back in from first crash

edit

make that 6 times in under 1 hr during CR

[Jhaerik]

I crashed to login screen 3 times tonight. same as before. I crashed in my last grp tonight as our ivu wore off and had to CR. its bad when your group wipes. Extra bad when you wipe and then crash to login screen waaahhh.

edit

Make that back to back crashes soo as I logged back in from first crash

edit

make that 6 times in under 1 hr during CR

Crashing during zoning? Having any other weirdness? 100% sure all of the files from the new patch went into the correct folder? (Sometimes depending on the program subfolders can not extract correctly.) I mean it's probably the AT&T issue again.. but never hurts to double check. I believe the pathing node changes effected a lot of zones and it might be that you are having issues loading into those zones if those files didn't get overridden properly. (Hell it could be server side for all I know.)

[Rygar]

I have had this issue repeatedly and made a thread about it, here it is:
http://www.project1999.com/forums/showthread.php?t=249614

Rogean made a post a while ago about this same issue and requested trace routes, I found it searching for answers to this. I PM'd him if there was anything I could do to help pin down the problem but I haven't heard back. Here is his thread:
http://www.project1999.com/forums/showthread.php?t=201530&highlight=trace+routes

Edit: He does mention in his post that around 8:30PM or 9:30PM central a lot of issues tend to occur with server select and zone crashing, I have definitely found this to be the case as that is my usual play time. If i play off hours on the weekend or log in super late at night I typically can log in first try and zone fine.

Edit #2: Here is Rogean's post from same thread, had said they thought they had the problem identified and could stop posting trace routes, but had given this potential solution instead. Unsure if this is still accurate as I'm not in the NYC region, but unsure if I route through there:

We got an update from GTT saying they've increased their peering in the NYC region. I'm not sure if this affects all providers or not though. So keep an eye on things tonight. IF you start having issues, please run WinMRT for several minutes (Get it here: http://sourceforge.net/projects/winmtr/files/Latest/) and post the results here. When using WinMRT please direct it at project1999.com, and when making the forum post, post it using the same internet connection you ran WinMRT from so I can pull your ip address from the post (The data center needs this information).

[Abner]

Played last night with no issues. Well other than crashing when I camp most of the time but I have always had that problem and just live with it. HooRay!

[phiren]

Crashing while zoning occasionally = classic EQ experience

Crashing while zoning 90% of the time, not being able to see servers on server select screen, = problem

This thread was specifically for AT&T users who were all having massive problems.

I had great success last night, zoned a lot, swapped a few toons. 100% normal (and by 100% normal, of course it crashed 1 time the whole night).

But the MAJOR issue seems to be resolved

[EQBallzz]

I had no issues last night thankfully. Not 100% confident the issue is resolved but hoping it is.

[Anowin]

AT&T Tech replaced some old line at the house, increased the MPS to 18. Found no other issues. I played with no problems last night, before the tech came this morning. Crossing my fingers this remains fixed.

[Culkasi]

This happened to me quite a lot today, in Europe so no AT&T, not happened a lot prior to today (that I have noticed)

[Nilstoniakrath]

It's baaaack.... good grief

Had a couple of good days at least

[Hunky]

I've been having these same issues for the last couple of days. Timed perfectly with my druid getting 29 and trying to doing some porting.

[Numia]

Started to have all of these problems today as well.

Occasional black screen on server select
Crashing on my zone loads
Long zone loads if I do make it through

Had no issues prior to these starting, I am on google fiber in Austin, Tx. No other streaming stuff going on in the background.

[Bittersauce]

I've been having these problems starting today.

So far, I've noticed the following behaviour:

LD on zoning (on my end, I'm stuck on the loading screen forever - waited 25 minutes in one case before closing the window. Group mates confirmed I went LD within a few minutes on their end)
LD on logging in (same as LD on zoning, stuck on the loading screen indefinitely)
On some recovery from LD, server select screen is empty
On some recovery from LD, I'm told my spell files are out of date

Every once in a while I just have an extremely long zonetime (10+ mins)

Interestingly, once I'm IN the zone, I have no issues at all.

No other internet issues experienced outside of this. I'm Canadian, and on Bell, so it isn't the infamous AT&T issue. Tracert while experiencing the issue below:

Tracing route to 66.55.145.2 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms mynetwork [192.168.2.1]
2 8 ms 7 ms 3 ms 10.11.2.241
3 * 3 ms 2 ms 10.178.206.72
4 3 ms 3 ms 2 ms 10.178.206.73
5 20 ms 23 ms 23 ms tcore4-toronto12_2-4-0-0_.net.bell.ca [64.230.10
4.164]
6 16 ms 19 ms 19 ms tcore4-montreal01_hundredgige0-9-0-0.net.bell.ca
[64.230.79.195]
7 17 ms 18 ms 16 ms newcore1-newyork83_so6-0-0_0 [64.230.187.234]
8 17 ms 19 ms 16 ms bx6-newyork83_xe3-0-0.net.bell.ca [64.230.187.15
8]
9 23 ms 43 ms 23 ms nyiix.gi3-6.cr1.nyc1.choopa.net [198.32.160.157]

10 * 22 ms 22 ms vl23-br2.pnj1.choopa.net [66.55.130.53]
11 22 ms 21 ms 21 ms vl20-br1.pnj1.choopa.net [108.61.244.41]
12 * 20 ms * ethernet1-2-1-c8-12-b2-1.pnj1.choopa.net [108.61
.244.50]
13 * * * Request timed out.
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.

[thedonkdonk]

LD on zoning (on my end, I'm stuck on the loading screen forever - waited 25 minutes in one case before closing the window. Group mates confirmed I went LD within a few minutes on their end)
LD on logging in (same as LD on zoning, stuck on the loading screen indefinitely)
On some recovery from LD, server select screen is empty
On some recovery from LD, I'm told my spell files are out of date

Every once in a while I just have an extremely long zonetime (10+ mins)

Interestingly, once I'm IN the zone, I have no issues at all.

I've been having the exact same issues today. I'm on Google Fiber. Did a fresh reinstall today also just to make sure.

[melandis]

I've been having these problems starting today.


Your long description matches what I've started getting from a few hours ago, trace in case it's of use to anyone:

6 11 ms 11 ms 12 ms peer6-hu0-1-0-1.telehouse.ukcore.bt.net [195.99.127.25]
7 14 ms 12 ms 16 ms 166-49-211-230.eu.bt.net [166.49.211.230]
8 78 ms 77 ms 77 ms ixp1-xe-11-0-1-0.us-nyc.eu.bt.net [166.49.208.144]
9 * * * Request timed out.
10 * 81 ms 82 ms vl23-br2.pnj1.choopa.net [66.55.130.53]
11 81 ms * * ethernet1-2-2-c8-12-b2-1.pnj1.choopa.net [108.61.80.218]
12 * * * Request timed out.
13 80 ms 86 ms 89 ms 170.rogean.com [108.61.129.170]

[Erati]

tonight has been awful - cant zone one time successfully

its 50-50 whether my character actually enters world from character select ( if I make it there )

[Nute0711]

Same exact problems from KC on Google Fiber. Seems that Google Fiber and AT&T are the primary offenders. This all started 3 days ago. I never had any problems prior.

[ajdes]

I've been having these problems starting today.

So far, I've noticed the following behaviour:

LD on zoning (on my end, I'm stuck on the loading screen forever - waited 25 minutes in one case before closing the window. Group mates confirmed I went LD within a few minutes on their end)
LD on logging in (same as LD on zoning, stuck on the loading screen indefinitely)
On some recovery from LD, server select screen is empty
On some recovery from LD, I'm told my spell files are out of date

Every once in a while I just have an extremely long zonetime (10+ mins)

Interestingly, once I'm IN the zone, I have no issues at all.

No other internet issues experienced outside of this. I'm Canadian, and on Bell, so it isn't the infamous AT&T issue. Tracert while experiencing the issue below:


Very similar behavior on RCN in the mid atlantic. Just started happening today.

[lland]

Same issue and I'm with Orange in Europe. I never had zoning time issues and only the odd LD/crash here and there. Since two days ago it's massive, almost every time I zone I crash and have to manually close EQ etc..

[feanan]

RCN in chicago, started up for me a few days ago also.
Quite annoying.

Well, looks like its not just an at&t issue. So maybe its a server issue

[daskullicious]

Same issues
ISP : Bell
not internet connection confirmed
it's this server internet i beleive

[stingman]

I've always had issues w/ zoning and crashing. I nearly almost always crash when camping out too. It's a Windows 10 issue.

But today, 4.5 hours ago I crashed while zoning and could not log in to server select screen again. It would let me in but show a blank screen with no servers. I've tried everything imaginable and nothing is working.

I live in California and my ISP is Comcast, so definitely not an ATT only thing.

[phiren]

if you guys really want to join forces and get assistance with it from techsperts looking at it -- you really need to post your traceroutes. You can skip the first couple hops when you post if you want (that's usually your own stuff, for security reason!)

Open up command prompt (Start -> Run -> Type "cmd" without the quotes).. 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
(You will see what directory you are in)

That's the data you will want to post. Someone good at this stuff might be able to pinpoint the source of the problem (one of the choopa switches or something).

It is definitely a network related issue .. and the only way ANYONE can help troubleshoot is to look over the traceroute data everyone supplies.

~Phiren

[greena03]

Same deal for me with Google Fiber, Windows 10.

Hang/freeze/crash when zoning. Also encountering login server timeouts and weird Spell File outdated errors when logging into the game again.

[Rathlok Wu]

I'm on Google fiber... same issue as everyone else and it started yesterday after weeks of very stable and solid gaming.

[Raev]

I agree with Phiren that it's likely to be a network issue. Somehow the loginserver is very sensitive to packet loss. Traceroute is extremely unhelpful for me, though:

11 vl203-cr1.ewr3.choopa.net (216.155.128.2) 67.220 ms 67.269 ms 67.301 ms
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

Edit: on second thought, maybe not. It looks like Choopa is Rogean's ISP, and something bad is happening internally since I can get to their gateway with 65ms ping.

Anyway, I think we should all celebrate this new, more classic, environment.

[Hunky]

I tried, got the text file and inside was just 'Unable to resolve target system name login.eqemulator.org.' :(

edit: Tried same thing with google.com and it worked.

[hamirez]

I am crashing as well. 80% of times I zone. Sometime blackscreen others the game freezes. Reve to reestart my computer because I was playing on fullscreen. Now I just play windowed to ctrl+alt+del the game when needed.

[thedonkdonk]

'Unable to resolve target system name login.eqemulator.org.'

It's login.eqemulator.net

[Hunky]

Thanks. With that now fixed I did two tests, having to stop them as they were timing out:

5 61 ms 59 ms 57 ms rc3fs-hge0-15-0-0.mt.shawcable.net [66.163.73.177]
6 68 ms 72 ms 74 ms rc1hu-pos0-1-0-0.ny.shawcable.net [66.163.76.14]
7 * 75 ms 91 ms nyiix.gi3-6.cr1.nyc1.choopa.net [198.32.160.157]
8 78 ms 68 ms 68 ms vl23-br2.pnj1.choopa.net [66.55.130.53]
9 86 ms 75 ms 74 ms vl20-br1.pnj1.choopa.net [108.61.244.41]
10 76 ms 78 ms 74 ms ethernet1-2-1-c8-12-b2-1.pnj1.choopa.net [108.61.244.50]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
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 * *

And:

7 78 ms 75 ms 76 ms nyiix.gi3-6.cr1.nyc1.choopa.net [198.32.160.157]
8 71 ms 69 ms 70 ms vl23-br2.pnj1.choopa.net [66.55.130.53]
9 72 ms 70 ms 69 ms ethernet1-2-2-c8-12-b2-1.pnj1.choopa.net [108.61.80.218]
10 * 82 ms 71 ms ethernet1-2-1-c8-12-b2-1.pnj1.choopa.net [108.61.244.50]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * *

[thedonkdonk]

MTR to port 9000 (same port the game runs on) on login.eqemulator.net. Via a Raspberry Pi on the same network as my Windows 7 PC I game on. Same public IP as this post. On Google Fiber in Kansas City.

http://i.imgur.com/AHM2VnF.png

You can see the packet loss happens once we hit choopa.net. The hosting provider. 2.7% packet loss is normal enough on a traceroute for an edge router. It can be busy enough that it will drop these kind of diagnostic packets but still do regular traffic just fine.

The 54.5% packet loss on the last hop is at least a symptom of what ever issue.

It's not an AT&T issue or a Google Fiber issue.

Here is one from a colocation datacenter I use in Kansas City. It uses Hurricane Electric. Same packet losses.

http://i.imgur.com/1Mq0pty.png

Another from a Chicago Rackspace Cloud Server. It uses Comcast.

http://i.imgur.com/KcrDiBb.png

[greena03]

Whole lot of kansas city people playing that old ass EQ in here.

[TacoSmasher]

East coast canada here. just got Bell Fiber op installed today and been having this issue. Didnt have the problem at the other place before i moved, same ISP.

Seems like something changed on the server side recently. There have been multiple server reboots over the last few days correct?

[Fleetwood]

As of the last couple days I've been having the same problems.
Crashing on zone, Crashing on /camp, freeze on login, and sometimes very delayed spell casts and mouse clicking issues.

Nothing on my end has changed and I don't stream/download stuff while I'm playing so I'm assuming this is server side.

East coast Canada here as well with a good connection.

[Grimjaw]

looks like its failing after that specific Choopa hop for everyone however u'll need to go thru ur ISP for resolution

[feanan]

Tech support, may I help you?

Umm, yes, hi, I play this 17 year old emulated game called everquest, and 40% of the time I can't log in, it appears that its the Choopa hop, can you help me?

I can imagine the laughter from here...

[Hunky]

I've had success using PIA VPN out of Seattle, no issues since. Hopefully I dont have to use it for very long.

[TacoSmasher]

issue seems to be resolved for me as of yesterday

[delfi]

This has just begun happening to me. I crash when zoning, logging in, even the minute i loot my corpse I'll crash.

Not just me, friends on different internets/computers have been experiencing same issue.

[Obeast44]

I am having the same issue on my home connection. Everything else works perfectly, youtube, Netflix, Kodi. As soon as I try and login to P99. I have no servers showing. If I do manage to get in after 20 tries I cannot zone or it will crash. The very second I disable my home network and enable a wireless 4g tether, everything immediately works perfectly. I have noticed this really only happens on the weekends or during peek hours. Is there something I can do to solve this?

[Obeast44]

I am still having this issue. It only happens on weekends and evening (primetime). Any suggestions?

[WDavidson]

I have not been able to get a server list since the servers went down this morning, 9/20/2016. I've been scrolling the forums for fixes for hours and I'm stumped. There was no hardware or software changes to the PC before the server crashes (when it worked).

I have now re-installed titanium twice, opened port 5998 in my firewall, turned off my firewall, shut down/restarted both my PC and Modem, hard reset my modem so hard I had to call my ISP, installed and setup both Wineq2 and EQemu, set eq to run in compatibility mode and admin, and updated every driver I could find.

I've also run a tracert, which came up decent, even going through choopa.

5 18 ms 17 ms 16 ms xe-3-2-0.mpr4.bos2.us.above.net [208.184.223.233
]
6 17 ms 16 ms 16 ms ae2.mpr3.bos2.us.zip.zayo.com [64.125.25.41]
7 25 ms 26 ms 25 ms bost-b1-link.telia.net [62.115.35.233]
8 34 ms 24 ms 24 ms nyk-bb1-link.telia.net [62.115.122.202]
9 34 ms 25 ms 25 ms nyk-b2-link.telia.net [62.115.112.107]
10 25 ms 25 ms 25 ms vultr-ic-318460-nyk-b2.c.telia.net [62.115.149.4
1]
11 25 ms 26 ms 32 ms vl50-br1.pnj1.choopa.net [66.55.144.146]
12 26 ms 29 ms 25 ms ethernet1-2-1-c8-12-b2-1.pnj1.choopa.net [108.61
.244.50]
13 29 ms 27 ms 30 ms vl203-cr1.ewr3.choopa.net [216.155.128.2]
14 26 ms 26 ms 27 ms 170.rogean.com [108.61.129.170]

Trace complete.

I'm just a little lost, as less than 24 hours ago, everything worked fine. Any advice is welcome.

Laptop
Intel I7 core
Nvidia GTX card

[Strana]

Been having this issue for past 3 days. I'm on Frontier's network. Only thing in common with these issues is the hosting side. P1999 guys or who ever owns the login server need to open a support ticket with their ISP.

[Blizzax]

I will say, I was having this same exact issue, found that disabling loading screen when zoning helped, not a single crash since.