You're seriously going to cherry pick a single example from SEVEN YEARS AGO as if it has any relevance whatsoever to the problem at hand?Yes, I did.
It is a theory, not a proof.
I also said it is suggestions because whatever Japanese is suggest is also a theory
No IT tech is able to recreate same environment for each player's system
I only can tell you SE is not intend to lie about 2002 because their IT is truly believed it is client side issue.
This is a blog from a Japanese player in regard to 2002 at year 2014 (not provide name due to privacy:
2014/02/06 09:49 3
ロビーサーバー接続でエラー2002の対処法
[エラー2002]
公開
昨日からエラーで入れなかった件ですが
GAME START
をクリックしましてデータセンターに接続表示後
ロビーサーバー接続でエラーが発生しました(2002)
と出て入れなかったわけですが
問い合わせメールの返信が来ました。内容は最後にコピペしときます。
自分の原因はですがセキュリティーソフトのバグ?でした。
普通でない状態だったらしく立ち上げて更新とかクイックスキャンとかできることを片っ端からやって閉じたら
FF14に入れるようになってました。このエラーは向こうに原因はなくPCか回線の問題みたいですね。
ともかく入れてよかった。
ではコピペ
Basically, SE IT tech inform him 2002 is player's PC connection issue and this JP player fixed it by turn off the antivirus program: there is a bug with security soft (セキュリティーソフトのバグ)
After the patch, I on average only encounter 2002 twice and my system environment is cleaner than most of FF14 players because this system is dedicate to gaming only. No other 3rd party software including discord. I bought the new wifi6 router, i will update if i am still getting same 2002 frequency
The question is, as a game producer, who should Yoship believe? His own IT tech team who able to provide steady service before WoW exodus or some google document and no idea who the author is?
No?
Just showing that is really what their IT believed in?
Is Yoship an IT or a game producer?
Better question is, are you a person believe in professional IT or something you googled?
I've had 2002 on a direct connection (from router, not modem ;P). I've had it with just FFXIV going and I've had with other sites working at the same time. Noting that when it has happened no device, no site, nothing in the house has recognized an internet issue (meaning if it was a local hiccup it was extremely small). I don't play FFXIV on wifi.I don't really think OP has any concrete proof.
Basically Japanese side agreed this is client side issue (player) and suggested the following 3 methods (copy word to word)
対策方法1:WiFiの接続方法をIEEE802.11nに変える
もし11acで無線接続している場合は通信品質が悪いことが多いので、速度が気になるところですが11nで接続しなおしましょう。
11acは通信速度が速い特性がありますが、障害物に弱い
11nは11acよりも通信速度は遅いが、障害物に強い
障害物を超えるごとに電波はどんどん弱くなっていきます。
This is to suggest to change type of WIFI connection from 11ac to 11n and basically concluded:
11a provides higher speed but signal will be weaker if there are obstacle (like metallic/concrete object)
11n is slower but stronger if there are obstacles
対策方法2:次世代通信方式11axが使えるルーターに変える
11axは超高速通信規格でWi-Fi 6と呼ばれるものです。
11axは「11acと11nの良いとこどり&通信速度が速い性質の電波」で通信品質も格別です。
This method is to suggest to switch to WiFi - 6
対策方法3:LANケーブルで接続する
まあ、確実ですね…。
ルーターが近くにあってパソコンやPS4と接続可能であれば検討してみてください。
なお、LANケーブルは見た目は全く同じでも規格があり、古すぎると通信速度・品質に影響が出る場合があります。
Last method is to suggest is to just abandon wifi and use direct cable connection.
Simple and straight foward.
They also suggest to not have anti-virus program to be running at back ground.
After SE patch, I am experiencing only 2 x 2002 from previous 8 x 2002.
This is my computer environment:
This new i7 CPU with 3080 GPU is connect via direct cable, no wifi
As the system is for gaming only (no surfing, no youtube), there is no anti virus program since i am not installing anything beside steam games.
My router is pretty old that bought 6 years ago and i assume that is why i am still encounter 2002 occasionally
I bought the new wifi6 router and will see if i am still having 2002 after installation
Though I do appreciate the translation attempt (serious), I just want to say I don't think it's simply just a client thing.
2021/12/14 11:55; Shougun が最後に編集
I'd wager the majority of the people getting 2002'd aren't using WiFi and even if they were, the game shouldn't error them out in the first place for a minor connection hiccup that's not an issue in literally any other game
Yeah I've been on Wifi since Stormblood and no issues ever. The 2002s have to be a lobby server fault or it's just randomly stops communicating with the user.
More proof that this company is full of it.
Sometimes it's not your equipment nor the data center equipment, but the nodes connecting you in between.
For those who aren't PC savvy, here is how you can see the router your computer is using:
Go to the website ARR Server Status: https://arrstatus.com/
Click on your data center. At the bottom of the list of servers is an IP address for the lobby server. The current ping time from their website to the lobby of Primal, my DC, is 155 ms, which is..... not great. There's a traffic jam on the internet between this website and the lobby server.
Take that IP address, and on Windows, open up a command prompt. Click on Start and type in the letters CMD to open it up.
In the command prompt, type in tracert "server IP address" (without the quotes) and let 'er rip.
This is what mine just spit out:
As you can see, there's two spots between me and the lobby server that have dropped packets. One is just outside the data center, which I imagine is slammed with traffic - and granted, trace route packet pings are lowest priority and many nodes will just reject them, but the node "snjsca04" also dropped a packet and it's not anywhere near the data center yet. (San Jose, I think? Sacramento nodes are cool.)Code:Tracing route to 204.2.229.10 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 192.168.1.1 2 * * * Request timed out. 3 8 ms 7 ms 7 ms 096-034-004-140.biz.spectrum.com [96.34.4.140] 4 10 ms 10 ms 10 ms 096-034-072-047.biz.spectrum.com [96.34.72.47] 5 16 ms 15 ms 15 ms bbr02atlnga-bue-3.atln.ga.charter.com [96.34.2.72] 6 14 ms 12 ms 11 ms bbr02atlnga-tge-0-2-0-0.atln.ga.charter.com [96.34.3.111] 7 10 ms 12 ms 10 ms atl-b24-link.ip.twelve99.net [62.115.179.146] 8 12 ms 11 ms 13 ms ae-2.r04.atlnga05.us.bb.gin.ntt.net [129.250.9.21] 9 12 ms 10 ms 11 ms ae-14.r22.atlnga05.us.bb.gin.ntt.net [129.250.5.202] 10 30 ms 32 ms 30 ms ae-6.r21.dllstx14.us.bb.gin.ntt.net [129.250.4.116] 11 75 ms 72 ms 71 ms ae-2.r25.snjsca04.us.bb.gin.ntt.net [129.250.4.154] 12 69 ms * 70 ms ae-5.r24.snjsca04.us.bb.gin.ntt.net [129.250.3.146] 13 76 ms 78 ms 75 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57] 14 79 ms 75 ms 76 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2] 15 74 ms * * 204.2.229.230 16 73 ms 74 ms 75 ms 204.2.229.10 Trace complete.
From what we understand, all it takes is one of those heartbeat communications from the local client to the data center lobby failing too many times to generate 2002. That's a lot of potential points of failure.
2021/12/15 00:29; Catwho が最後に編集 理由: Adding content
![]() |
![]() |
![]() |