FFXIV 90002 error

[Garg27]

I am getting the all too famous 90002 error randomly pop up when playing Final Fantasy XIV.  This is a known issue that has been raised and resolved multiple times on these forums and I'm looking for a bit of that same magic.

[Garg27]

So, it's definitely not a problem in the area as this has been going on since at least May, if not earlier.  It's still continuing to be incredibly bad and kicking me repeatedly.  Nothing has so far improved, from the engineer visit, resetting my router, rebooting it.  It's getting quite frustrating now.

[Travis_M]

Hi @Garg27

Thanks for posting on our community forum!

How has your service been since posting?

Regards

[hortonj88]

What I'm about to suggest is a shot in the dark but might be worth checking.

Have you allowed FFXIV through any firewalls you have, including Windows Defender Firewall?

90002 happens when you have a unstable connection to the game server but can also be caused by firewall's interfering with the game connection.

[hortonj88]

What I'm about to suggest is a shot in the dark but might be worth checking.

Have you allowed FFXIV through any firewalls you have, including Windows Defender Firewall?

90002 happens when you have a unstable connection to the game server but can also be caused by firewall's interfering with the game connection.

Try allowing ffxiv.exe and ffxiv_dx11.exe through any firewalls you have and re-login to the game.

If it still persists after you've allowed the game through any firewalls then the problem 100% is with Virgin Media's side of things and good luck with getting that fixed.

[Garg27]

Thanks for the option, only firewall I have is basic windows defender firewall.  It seems the boot and launcher were open but not the actual game executibles.  I've added them both and set all four enabled for private and public and will see if it treats me any better.

[Garg27]

Nope, sadly it has made no difference at all 😞

[Garg27]

Current state of things since the last 10 minute reboot a few weeks ago

Downstream bonded channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors

1	Locked	40.3	1486	1820
2	Locked	40.9	64549	5670
3	Locked	40.3	9303	5212
4	Locked	40.9	8021	5950
5	Locked	40.3	5781	4751
6	Locked	40.9	4947	3968
7	Locked	40.3	3373	3882
8	Locked	40.9	2077	3427
9	Locked	40.3	1854	3003
10	Locked	40.3	1359	3055
11	Locked	40.3	1184	2409
12	Locked	40.9	1145	2343
13	Locked	40.3	1068	2220
14	Locked	40.9	1355	1816
15	Locked	40.3	1343	1706
16	Locked	40.3	1286	1426
17	Locked	40.3	1440	1234
18	Locked	40.3	1399	1189
19	Locked	40.3	1152	1114
20	Locked	40.3	1175	930
21	Locked	40.3	1306	834
22	Locked	40.9	1064	812
23	Locked	40.3	1245	588
24	Locked	40.9	1134	602

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1	ATDMA	0	0	3	0
2	ATDMA	0	0	2	0
3	ATDMA	0	0	3	0
4	ATDMA	0	0	3	0

Network Log

Time Priority Description

05/02/2022 14:53:28	notice	LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
31/01/2022 11:10:42	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/01/2022 11:20:58	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/01/2022 05:08:19	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/01/2022 23:10:42	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/01/2022 16:18:35	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/01/2022 11:10:42	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/01/2022 11:58:37	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/01/2022 04:11:22	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/01/2022 23:10:42	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/01/2022 11:32:14	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/01/2022 11:32:26	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/01/2022 11:10:42	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/01/2022 23:46:27	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/01/2022 04:46:49	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/01/2022 22:40:42	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/01/2022 12:54:4	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/01/2022 10:37:52	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/01/2022 16:41:23	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/01/2022 07:45:40	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

[Molly_T]

Hi @Garg27, 

Sorry to hear you are still experiencing issues with your service. I just wanted to check - the intermittent connection issues you are having, are they happening on devices connected via WIFI or ethernet? 
I know you previously spoke about the technician advising you to split your WIFI networks - are the disconnections happening across both of these networks, or just one? (Eg, the 5ghz network)

I can also see some upstream power level signal issues that will need a technician to resolve. I will send you a PM to confirm a few details and get this booked in for you. 

All the best. 

[Garg27]

We only have one or two devices connected by Ethernet and they seem fine, though it's difficult to tell.  Regarding the wifi, we only really use 5ghz devices in this household, so most things connect through that.  But again, it's not the entire internet that gets cut off during these downs, but specific services such as my game connection, twitch streams and works' VPN.  But they do seem to happen at the same time across different devices when they do happen

[hortonj88]

The issue's most definitely on the Virgin side of things then.

I'm with BT and I haven't seen any 90002 or similar errors since Endwalker early access.