Error 90000 and 2002 Why are you deleting my posts without reslutions?

I sent in a ticket and what you suggest will not help as I'm tethering from my phone. There are no settings to adjust.. so your auto email reply did not solve my problem.

And you go ahead and delete my issue with no feedback or resolution.

I am still unable to play.

This all happened after patch 2.4

Nothing has changed on my side. I called my ISP and they informed me that the only changes that took place was on your end.

So stop deleting my post and have someone inform me of when you will reverse what you did to prevent me from playing.

Are you sure they weren't moved to Separate Support Required or Resolved Issues (happens sometimes after a thread becomes inactive long enough--especially when there are duplicate threads). If they were straight deleted, it may have been because duplicate threads were already up and active...could have been done by policy or because enough people reported it as such.

As for the ISP's potential culpability with your connection woes... they may have actually told you more than you realize by saying nothing has changed on their end. That may in fact be part of your problem---something may need to be changed in your route because it is getting impacted by bad latency/packet loss. May want to trace the route to see if anything sets off any red flags.

I might be experiencing a problem with my route actually. Is there a way to change the way my connection is routed, either through something I can do or on my ISP end?

Before the patch I had no problems. After patch I cannot stay longer then 2 sec in the game. For them to admit they made changes that affect me means they are obligated to fix it. By saying nothing they know they do not have to do anything other then let this fade away.

I'm tethering from my rogers wireless phone.

Changed trace and ping to the ip server I play off...

C:\Users\USER>ping 199.91.189.33

Pinging 199.91.189.33 with 32 bytes of data:
Reply from 199.91.189.33: bytes=32 time=78ms TTL=235
Reply from 199.91.189.33: bytes=32 time=196ms TTL=235
Reply from 199.91.189.33: bytes=32 time=236ms TTL=235
Reply from 199.91.189.33: bytes=32 time=86ms TTL=235

Ping statistics for 199.91.189.33:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 78ms, Maximum = 236ms, Average = 149ms

C:\Users\USER>tracert 199.91.189.33

Tracing route to 199.91.189.33 over a maximum of 30 hops

1 17 ms 4 ms 2 ms 192.168.43.1
2 * * * Request timed out.
3 279 ms 194 ms 237 ms 192.168.126.66
4 180 ms 26 ms 30 ms 10.118.22.229
5 349 ms 26 ms 37 ms 10.118.20.149
6 75 ms 28 ms 37 ms 10.118.23.22
7 81 ms 30 ms 41 ms 10.118.20.77
8 70 ms 28 ms 27 ms 192.168.1.75
9 55 ms 37 ms 32 ms 192.168.1.21
10 52 ms 30 ms 27 ms 24.156.157.153
11 185 ms 94 ms 36 ms gw03.strfrd.phub.net.cable.rogers.com [66.185.82.38]
12 43 ms 38 ms 30 ms 24.156.146.42
13 43 ms 35 ms 39 ms 24.156.157.133
14 232 ms 217 ms 43 ms 69.63.249.169
15 88 ms 47 ms 65 ms 209.148.224.254
16 * * * Request timed out.
17 217 ms 38 ms 41 ms be2373.ccr21.yyz02.atlas.cogentco.com [154.54.46.33]
18 60 ms 48 ms 49 ms be2090.ccr21.ymq02.atlas.cogentco.com [154.54.30.206]
19 211 ms 52 ms 38 ms 38.122.42.34
20 * * * Request timed out.
21 105 ms 43 ms 37 ms 192.34.76.2
22 446 ms 53 ms 46 ms 199.91.189.234
23 191 ms 51 ms 48 ms 199.91.189.33

Trace complete.



Checked the game and am still getting the 90000 error.. still not able to stay in game for more then 2 sec. So improving my connection did not resolve my issue. Again I remind you that this all happened after the patch where I am unable to play by tethering from my phone.

/sigh

You're not even looking at an IP used for the game. All the servers in Canada start with 199. That IP you are hitting hosts websites for the Squenix/EIDOS libraries, but has nothing to do with playing FFXIV. Ping www.justcause2.com, www.sleepingdogs.net, and www.deusex.com if you don't believe me. There's more than a dozen website URL's that point to that IP.

All of this has been covered over and over and over again in thread after thread on these forums. Beginning to wonder if people even bother to research them anymore before creating duplicate threads over and over again.

If you are going to run tests, ideally you want to use the IP your client actually uses (netstat from DOS or resmon from the run/search box to get the IP when you are fully logged into the game). At the very least, you could use the lobbyserver addresses:

neolobby01.ffxiv.com
neolobby02.ffxiv.com
neolobby03.ffxiv.com
neolobby04.ffxiv.com
neolobby05.ffxiv.com
neolobby06.ffxiv.com
(odd numbers are Japan, even are Canada. Note this may change once they get actually EU servers up and running)


Regardless though, you have some problems in your more localized segments that need to be addressed first. No matter how good things might be at the other end of the route, seeing 100, 200, 300, and 400+ms response times so close to home is going to be a BIG problem. You may find things get considerable better if you can get away from those bad latency spots within your first 5 hops.

And how do I change the first 5 hops? Do I ask my ISP to do something?

Changed the ip trace to the server I play on and these are the results...

C:\Users\USER>ping 199.91.189.33

Pinging 199.91.189.33 with 32 bytes of data:
Reply from 199.91.189.33: bytes=32 time=78ms TTL=235
Reply from 199.91.189.33: bytes=32 time=196ms TTL=235
Reply from 199.91.189.33: bytes=32 time=236ms TTL=235
Reply from 199.91.189.33: bytes=32 time=86ms TTL=235

Ping statistics for 199.91.189.33:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 78ms, Maximum = 236ms, Average = 149ms

C:\Users\USER>tracert 199.91.189.33

Tracing route to 199.91.189.33 over a maximum of 30 hops

1 17 ms 4 ms 2 ms 192.168.43.1
2 * * * Request timed out.
3 279 ms 194 ms 237 ms 192.168.126.66
4 180 ms 26 ms 30 ms 10.118.22.229
5 349 ms 26 ms 37 ms 10.118.20.149
6 75 ms 28 ms 37 ms 10.118.23.22
7 81 ms 30 ms 41 ms 10.118.20.77
8 70 ms 28 ms 27 ms 192.168.1.75
9 55 ms 37 ms 32 ms 192.168.1.21
10 52 ms 30 ms 27 ms 24.156.157.153
11 185 ms 94 ms 36 ms gw03.strfrd.phub.net.cable.rogers.com [66.185.82.38]
12 43 ms 38 ms 30 ms 24.156.146.42
13 43 ms 35 ms 39 ms 24.156.157.133
14 232 ms 217 ms 43 ms 69.63.249.169
15 88 ms 47 ms 65 ms 209.148.224.254
16 * * * Request timed out.
17 217 ms 38 ms 41 ms be2373.ccr21.yyz02.atlas.cogentco.com [154.54.46.33]
18 60 ms 48 ms 49 ms be2090.ccr21.ymq02.atlas.cogentco.com [154.54.30.206]
19 211 ms 52 ms 38 ms 38.122.42.34
20 * * * Request timed out.
21 105 ms 43 ms 37 ms 192.34.76.2
22 446 ms 53 ms 46 ms 199.91.189.234
23 191 ms 51 ms 48 ms 199.91.189.33

Trace complete.

Quote:

---

Originally Posted by Wilbert

And how do I change the first 5 hops? Do I ask my ISP to do something?

---

Them or whoever is in control of all those private IP addresses prior to that Rogers IP address at hop #10 (24.156.157.153). If it is your ISP using all those IP's, then you need to be in touch with their Tier3 techs about this. They can conduct a more proper investigation and hopefully get things escalated towards a proper resolution.

I did try to escalate it due to the tech at the original call saying it was beyond his understanding.. pay grade. So he transfers me to a department called Tech Experts... an off shot to Rogers.. they wanted $34 more for them to assist me??? Not that it would mean they would solve my latency issues..

I'm still leaning on FFXIV did something in that new patch that's preventing me from playing.. because prior to that I've had no issues what so ever.

My readings when in game before I get booted...

Sending 60 Receiving 72

When in Lobby server I get 3102 saying I need to wait until my character is out of the game..

Then the lobby server window freezes and crashes after a few attempts.

Then I get an error 2002...

This is not a latency issue... its a game issue.

You stopped sending and/or or receiving data frequently enough and your connection dropped. Those S/R numbers in the upper right corner are bytes/second--not your response time in milliseconds. Unless you were sitting idle for a while in an area with no active players around you, those numbers should be considerably higher... even sitting in the inn they would likely a bit higher just from keep alive and positional update streams.

And you have a latency problem that needs to be addressed. It will cause issues with this game. If not periodic session time outs that result in 2002/90k errors, it may cause extreme rubberbanding, skips, or out right pauses in gameplay.

You are getting the error about still being logged in because your client has dropped connection without logging you out of the service. A good while back, SE implemented a work around to capture these exceptions, but it sometimes takes a while to catch it and sign you out. It should clear up after a while. If not, you need to submit a more formal ticket either through the support portal or in the bug reports section, not here in the user-to-user forums.