bump
bump bump bump bump
bump
bump bump bump bump
SolArisa:
Thanks for your input. I ran a wireshark capture tonight and posted my findings in a spreadsheet.
I have a spreadsheet I've uploaded online for review that hopefully will give some insight into what this problem is. Here's a summary of what's going on:
* 22 frames had a duplicate acknowledgement to a frame before it due to the a segment in the frame before it being lost.
* 62 frames had a tag of [TCP Previous segment lost].
* EVERY packet sent FROM the server with the exception of those listed above (items 1 and 2) was received with no errors.
Wireshark link: https://www.filesanywhere.com/fs/v.a...8a5e626ebd73ab
I can upload the actual wireshark log file if network support needs it. It's just a proprietary format and won't really work without wireshark I don't think.
Now the question is, what causes this problem? I got back on the phone with Cox level 2 support but he wasn't really able to help with something this technical so he gave me an e-mail address to send my data to. I'm hoping they can decipher something out of it that makes sense.
Last edited by Orophin; 10-21-2011 at 02:27 PM.
Uploaded a new file tonight:
http://www.filesanywhere.com/fs/v.as...8c5c676da76e9e
The packets in question have the following tags:
[TCP Dup ACK]
[TCP Retransmission]
[TCP Previous segment lost]
The first tag I've read can be a problem due to a duplex mismatch between network devices. By default, duplex is set to auto, which my NIC is. I've e-mailed my ISP just to ensure that nothing changed on their end, but it seems highly unlikely something changed on their end the day after patch 1.19a hit. Perhaps if someone from SE would actually take the time to read these threads, they can check either:
a) their coding for the latest patch to make sure packets aren't being sent in something other than Auto Duplex
b) their hardware for any duplex changes.
Support for this game is absolutely terrible. This is where we get directed to when we need an issue fixed. And the only thing that ever gets posted is them asking for your PC specs. If they start charging for this game next month I will not be playing it that is for certain.. Its sad when you have people that want to play the game and can't....
I completely agree. This is a typical Square Enix response. If they would only acknowledge that they recognize that there is even a problem, then that would be something.Support for this game is absolutely terrible. This is where we get directed to when we need an issue fixed. And the only thing that ever gets posted is them asking for your PC specs. If they start charging for this game next month I will not be playing it that is for certain.. Its sad when you have people that want to play the game and can't....
The basic problem is that this ONLY STARTED HAPPENNING after patch 1.19a. It is being reported by many people in differtne locations with different ISPs. Therefore, it is NOT an ISP issue. It is an issue with SE hardware.
For any of them to even slightly imply that it could be our hardware is ridiculous. They developed the benchmark program. We passed the benchmark. Many of us built PCs just in order to play FFXIV.
They need to address this issue and get in-game GMs that you can personally complain to about RMT and botting activity and have the authority to take immediate action. (I'm not attempting to derail, but it is typical of their customer support)
I have posted on other 30002 threads, but i can 100% say its not any problem on our (players) end, i can log in an alternate character on same account, with no issues, but my main character, gets 30002 at now loading screen when i attempt to log in, if customer service does not fix this TODAY, I will be cancelling my FFXI subscription, and will not be playing either game anymore, pretty ridiculous imo...
I definitely think you should blood I wouldn't give them any money right now. When as many people have connection issues as they do that should be first priority.. I even completely reinstalled and downloaded the patch thinking it would help and it wouldnt... And they don't even post on here or make an announcement acknowledging they are aware of our issues.
|
![]() |
![]() |
![]() |
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.