Moved into new apartment. New wifi connection. Gettting 90ked constantly.

*EDIT* DISREGARD IRRELEVANT INFO RE: MOVING, ETC. ISSUE IS THAT TIME WARNER "ULTIMATE" PACKAGE ROUTES TO NA SERVERS FROM NYC IN SUCH A WAY THAT CONNECTION DROPS AT CERTAIN HOPS. RESULT: CONSTANT 2002 AND 90000 ERRORS


As the title states I recently moved from my old place (which had time warner cable & where I connected with no problems for the past 6 months via wifi) to a new place (also with time warner cable / wifi). I was able to start and update the launcher without issue, but was not able to get into character select (error 2002). After some searching I forwarded all the ports outlined in this post: http://na.finalfantasyxiv.com/lodest...06/blog/77559/

after forwarding all of those ports I was able to get into the game without getting error 2002. However every ~5 minutes I am receiving a 90k error. Any suggestions?

Note that I can NOT connect via hardwire connection, so please leave that out of any troubleshooting suggestions. This is really frustrating and I've already missed two raid dates because of it. I am willing to follow any diagnostic instructions & post trace route logs, etc; just tell me how to do it and I will post the info. Thanks in advance.

I don't know if this will help, but if you didn't have this problem before, then most likely the problem is with the new router configuration in some way.

One possible suggestion I can think off offhand is, If your router has the ability, see if there is an issue with the channel it is using, for example if you have 10 other wifi routers in range using channel 6, it might be a good idea to use a different channel. Interference due to multiple other networks/devices could degrade the performance, causing issues.

For better support you might also post the actual model of the router.

Try disprove that it is the WIFI connection by connecting through the ethernet port for testing purpose. If you still get 90000 error while on ethernet, it could most like be the actual internet connection.

Why can't you hardline? Is this a shared router/switch? You're going to want to post your tracert logs for sure.

Questions:

Who's your ISP?
What's your OS? Make/Model of computer?
Make/Model of wifi card?
What's your network path (client > router > modem > WAN etc.)?
City/State?
Was your old residence on the same ISP/City/State?
Are you using a VPN (I had this happen with WTFast a couple days ago. Tunnel to Tunnel SLC to Montreal was failing all over the place. Turned it off checked later they had reconfigured one of their nodes)?
If you Alt-Tab out and check your wifi symbol while you have the 2002, do you see a warning sign?

TS steps (until more data is provided):

Hardline to see if the issue dissipates (sorry, but this is going to need to happen)
Perform a ipconfig /release followed by a ipconfig /renew
Make sure firewalls aren't blocking anything (Norton)
Pull tracert logs and post them. Anything with high latency asterisks are points of interest.
Factory reset the router

Odd questions, but... do you have a microwave near the router or being used when you're playing?
Some microwave can kill wifi frequency, not sure if this will happen if your neighbors got microwave nearby as well. I would suggest try moving the modem/router to another location in your house to see if that will fix the issue.

I'm at work so I can't do a tracert right this second but I can say that I can't hardline because the account isn't under my name, but rather the landlord's. Hardwiring would require drilling holes and somehow fishing the ethernet cable into my apartment, which my landlord doesn't want; on top of this I can't simply use the modem downstairs and have her use wifi because she's used to having the hardwired connection herself.

Re: previous connection, same state, same ISP (Time Warner), same package, same wifi adapter, same computer. What has changed is the physical location (obviously) and the router. I can't tell you what the router number is either, other than that it's an arris. I was able to access the router settings via web (which is how I forwarded the ports) but didn't figure out the make or model. I may be able to post that info later.

You said that WTFast is having a problem specifically with the montreal server? because that is the server that I typically connect to.

*edit* also I am no longer receiving the 2002 since forwarding my ports. I am able to log into the game and play just fine until I disconnect. The only thing I'm experiencing are 90ks every 3-5 minutes.

check to see what frequency most of your neighbors are running on using something like meraki stumbler (you can find it on android store, there are variety of similar web apps if you look).

After which, set your frequence to 1, 6, or 11, depending on which block of bands is least used.

Quote:

---

Originally Posted by jumpypuppet

I'm at work so I can't do a tracert right this second but I can say that I can't hardline because the account isn't under my name, but rather the landlord's. Hardwiring would require drilling holes and somehow fishing the ethernet cable into my apartment, which my landlord doesn't want; on top of this I can't simply use the modem downstairs and have her use wifi because she's used to having the hardwired connection herself.

Re: previous connection, same state, same ISP (Time Warner), same package, same wifi adapter, same computer. What has changed is the physical location (obviously) and the router. I can't tell you what the router number is either, other than that it's an arris. I was able to access the router settings via web (which is how I forwarded the ports) but didn't figure out the make or model. I may be able to post that info later.

You said that WTFast is having a problem specifically with the montreal server? because that is the server that I typically connect to.

*edit* also I am no longer receiving the 2002 since forwarding my ports. I am able to log into the game and play just fine until I disconnect. The only thing I'm experiencing are 90ks every 3-5 minutes.

---

I'm not sure where the break was in the data center. It was last night. When it kicked me I closed the proxy and loaded the old fashioned way. After a couple hours reloaded the proxy and was fine. I wasn't wiresharked at the time and I didn't think to load loggers.

So it's a shared network and you don't have direct LoS to the router. You're using a wifi adapter? No integrated 802.11 on the machine (a desktop I take it).

Your setup allows for multiple points of failure. Can you use PLC Bridges (Asoka, Tenda make what's called PoE or powerline over ethernet adapters)? The hardline connection will always take priority on the network over any wifi device. If the hardline machine is eating tons of bandwidth or the router is bad/crappy/out dated firmware it could also exhibit the issues you're seeing.

Quote:

---

Originally Posted by cearka

check to see what frequency most of your neighbors are running on using something like meraki stumbler (you can find it on android store, there are variety of similar web apps if you look).

After which, set your frequence to 1, 6, or 11, depending on which block of bands is least used.

---

Use caution when playing around in the advanced functions of the NIC as changing some values (not this one specifically) will burn out the modem.

was on the phone for 2 hours with Company Tech Support Guy who helped me rule out several things. ultimately we came to the conclusion that since my own connection wasn't dropping, and the tracert was consistently showing failures at specific hops in the middle (going from my computer --> [insert NA server]), the problem is completely out of my hands.

here is a tracerts i just ran, to lamia (my server):

1 2 ms 1 ms 2 ms 192.168.0.1
2 29 ms 28 ms 29 ms 24.92.40.1
3 13 ms 20 ms 21 ms 24.29.42.233
4 16 ms 19 ms 30 ms 74.76.241.40
5 25 ms 35 ms 26 ms 74.76.241.193
6 30 ms 25 ms 28 ms 66.109.6.74
7 31 ms 28 ms 24 ms 107.14.17.169
8 36 ms 46 ms 37 ms 4.68.63.21
9 42 ms 45 ms 51 ms 4.69.156.30
10 45 ms 44 ms 43 ms 4.69.132.97
11 45 ms 50 ms 44 ms 4.69.141.5
12 32 ms 44 ms * 4.69.141.1
13 50 ms 44 ms 51 ms 4.59.178.74
14 51 ms 50 ms 57 ms 192.34.76.10
15 47 ms 52 ms 53 ms 199.91.189.242
16 54 ms 51 ms 56 ms 199.91.189.40

as you can see, at the 12 hop, the connection drops. sometimes the tracert will connect without issue; sometimes it has several more drops, all in the middle of the route to the final destination. we determined that this is because my old time warner service was the "turbo" package, servers for which originate in albany, and my new package is the "ultimate," for which the servers come out of NYC, meaning my connection takes a new route on the way to the server.

I resubscribed to my VPN at a cost of 10$ and wasn't able fix anything.

I am pretty sure this is on SE's end. I have already missed my raid for this week and will likely miss it the week after that, and after that, unless I can figure something else. Thoughts?

I am subbed for the next 200+ days so I would REALLY hate to just have wasted that money.

Quote:

---

Originally Posted by jumpypuppet

was on the phone for 2 hours with Company Tech Support Guy who helped me rule out several things. ultimately we came to the conclusion that since my own connection wasn't dropping, and the tracert was consistently showing failures at specific hops in the middle (going from my computer --> [insert NA server]), the problem is completely out of my hands.

here is a tracerts i just ran, to lamia (my server):

1 2 ms 1 ms 2 ms 192.168.0.1
2 29 ms 28 ms 29 ms 24.92.40.1
3 13 ms 20 ms 21 ms 24.29.42.233
4 16 ms 19 ms 30 ms 74.76.241.40
5 25 ms 35 ms 26 ms 74.76.241.193
6 30 ms 25 ms 28 ms 66.109.6.74
7 31 ms 28 ms 24 ms 107.14.17.169
8 36 ms 46 ms 37 ms 4.68.63.21
9 42 ms 45 ms 51 ms 4.69.156.30
10 45 ms 44 ms 43 ms 4.69.132.97
11 45 ms 50 ms 44 ms 4.69.141.5
12 32 ms 44 ms * 4.69.141.1
13 50 ms 44 ms 51 ms 4.59.178.74
14 51 ms 50 ms 57 ms 192.34.76.10
15 47 ms 52 ms 53 ms 199.91.189.242
16 54 ms 51 ms 56 ms 199.91.189.40

as you can see, at the 12 hop, the connection drops. sometimes the tracert will connect without issue; sometimes it has several more drops, all in the middle of the route to the final destination. we determined that this is because my old time warner service was the "turbo" package, servers for which originate in albany, and my new package is the "ultimate," for which the servers come out of NYC, meaning my connection takes a new route on the way to the server.

I resubscribed to my VPN at a cost of 10$ and wasn't able fix anything.

I am pretty sure this is on SE's end. I have already missed my raid for this week and will likely miss it the week after that, and after that, unless I can figure something else. Thoughts?

I am subbed for the next 200+ days so I would REALLY hate to just have wasted that money.

---

Okay, you are dealing with the same issue as a lot of other people then. Specifically, 4.69.141.1 is level3, not SE. It is a internet backbone company. That hop (and 2 others I know of), are causing everyone routed through them problems. Nothing you can do unless you can convince ISP to reroute the way your old plan did.

That said, that doesn't usually cause a lot of 90K issues, but rubber-banding in game. Perhaps the combination of WIFI issue and the dropped packet is what is leading to the constant disconnects.

I am unable to get into the game at all because of error 2002.

Quote:

---

Originally Posted by jumpypuppet

was on the phone for 2 hours with Company Tech Support Guy who helped me rule out several things. ultimately we came to the conclusion that since my own connection wasn't dropping, and the tracert was consistently showing failures at specific hops in the middle (going from my computer --> [insert NA server]), the problem is completely out of my hands.

here is a tracerts i just ran, to lamia (my server):

1 2 ms 1 ms 2 ms 192.168.0.1
2 29 ms 28 ms 29 ms 24.92.40.1
3 13 ms 20 ms 21 ms 24.29.42.233
4 16 ms 19 ms 30 ms 74.76.241.40
5 25 ms 35 ms 26 ms 74.76.241.193
6 30 ms 25 ms 28 ms 66.109.6.74
7 31 ms 28 ms 24 ms 107.14.17.169
8 36 ms 46 ms 37 ms 4.68.63.21
9 42 ms 45 ms 51 ms 4.69.156.30
10 45 ms 44 ms 43 ms 4.69.132.97
11 45 ms 50 ms 44 ms 4.69.141.5
12 32 ms 44 ms * 4.69.141.1
13 50 ms 44 ms 51 ms 4.59.178.74
14 51 ms 50 ms 57 ms 192.34.76.10
15 47 ms 52 ms 53 ms 199.91.189.242
16 54 ms 51 ms 56 ms 199.91.189.40

as you can see, at the 12 hop, the connection drops. sometimes the tracert will connect without issue; sometimes it has several more drops, all in the middle of the route to the final destination. we determined that this is because my old time warner service was the "turbo" package, servers for which originate in albany, and my new package is the "ultimate," for which the servers come out of NYC, meaning my connection takes a new route on the way to the server.

I resubscribed to my VPN at a cost of 10$ and wasn't able fix anything.

I am pretty sure this is on SE's end. I have already missed my raid for this week and will likely miss it the week after that, and after that, unless I can figure something else. Thoughts?

I am subbed for the next 200+ days so I would REALLY hate to just have wasted that money.

---

Yeah, looks like a BB issue. I can't tell (your log doesn't show the hop names) for sure, but looking it over it appears that to be the issue.

Some (not all) ISP's do tiered packaging. I'll give you an example of an ISP in my area, Cable One. The highest residential plan you can get has a data cap of, I believe 50 GB (don't quote me, I have Century Link). Now, as a residential user, you COULD upgrade to a commercial plan (for more money) that would eliminate the data cap, and, MUCH MORE IMPORTANTLY, give you "priority" status for your route path.

This may be what Time Warner is doing with your connection. "Turbo" may be their priority node while "Ultimate" may be the "everybody else" node.

it's actually the opposite: "turbo" is a lower tier package than "ultimate." ironically the slower package in this case is better because it avoids the faulty hop on the way to the server.

let me ask you this: it does seem clear that the 12-14 hops are where i'm running into trouble. but why doesn't using a VPN fix the issue? would that not send me on a different path?

Quote:

---

Originally Posted by jumpypuppet

it's actually the opposite: "turbo" is a lower tier package than "ultimate." ironically the slower package in this case is better because it avoids the faulty hop on the way to the server.

let me ask you this: it does seem clear that the 12-14 hops are where i'm running into trouble. but why doesn't using a VPN fix the issue? would that not send me on a different path?

---

It depends on the VPN, and how the VPN in turn gets to the server. If the VPN still goes through the problem hop, it won't solve your problem. You can try picking different routes. For example, try a route that goes through the west/midwest, instead of New York.

Hops 11 and 12 are your problem, so try the free trials of VPN's and find a route that bypasses them.

i simply signed up for a new time warner package in my own name (hard wired) and picked up the modem from the local branch. i am again using the "turbo" servers so with any luck i will no longer have this problem. however even if that does resolve the issue i am pretty sure that other time warner ultimate customers in New York that play XIV will continue to have this problem unless something is fixed. granted the ultimate package is very expensive so it may be less noticeable but I would not consider this "resolved" by a longshot even if i can bypass the problem via a new package.

Quote:

---

Originally Posted by Rivienne

It depends on the VPN, and how the VPN in turn gets to the server. If the VPN still goes through the problem hop, it won't solve your problem. You can try picking different routes. For example, try a route that goes through the west/midwest, instead of New York.

Hops 11 and 12 are your problem, so try the free trials of VPN's and find a route that bypasses them.

---

Exactly. If the VPN uses that node to hop through after their proxy tunnel then you're in the same position you started in. My normal route path puts me around Chicago which has nothing but issues but when I SSH (SLC) > SSH (Montreal) > Host I don't have a problem