Port Bastok struck again. For the record, I have ports opened, so it's not that. Checking my router's log, I found it was trying to communicate with 124.150.154.122 and one of the ports in the 50000-63534 range. Little google fu revealed the IP to be in Tokyo, and seemingly the address is in ownership of SE.
Since I have everything set and I'm finding it hard to believe it's suddenly a router issue for everyone, I decided to tracert the above IP with and without my router.
The following is performed through my router.
The following is directly connected to my modem.Code:Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\<omitted>>tracert 124.150.154.122
Tracing route to 124.150.154.122 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 <omitted>
4 15 ms 15 ms 15 ms te-0-11-0-2-ar03.mckeesport.pa.pitt.comcast.net [68.85.75.53]
5 14 ms 11 ms 12 ms te-8-3-ar01.mckeesport.pa.pitt.comcast.net [69.139.195.193]
6 19 ms 21 ms 18 ms te-3-0-0-0-cr01.ashburn.va.ibone.comcast.net [68.86.91.129]
7 18 ms 18 ms 17 ms xe-10-1-0.edge2.Washington12.Level3.net [4.26.6.5]
8 17 ms 17 ms 17 ms vlan52.ebr2.Washington12.Level3.net [4.69.146.222]
9 19 ms 20 ms 18 ms ae-5-5.ebr2.Washington1.Level3.net [4.69.143.221]
10 18 ms 20 ms 18 ms ae-82-82.csw3.Washington1.Level3.net [4.69.134.154]
11 19 ms 19 ms 19 ms ae-84-84.ebr4.Washington1.Level3.net [4.69.134.185]
12 30 ms 21 ms 31 ms ae-4-4.ebr3.LosAngeles1.Level3.net [4.69.132.81]
13 85 ms 85 ms 85 ms ae-63-63.csw1.LosAngeles1.Level3.net [4.69.137.34]
14 85 ms 85 ms 84 ms ae-1-60.edge2.LosAngeles9.Level3.net [4.69.144.15]
15 293 ms 204 ms 211 ms KDDI-AMERIC.edge2.LosAngeles9.Level3.net [4.53.228.14]
16 174 ms 173 ms 172 ms lacbb001.kddnet.ad.jp [59.128.2.101]
17 294 ms 290 ms 290 ms otejbb203.kddnet.ad.jp [203.181.100.153]
18 290 ms 291 ms 288 ms cm-ote221.kddnet.ad.jp [118.155.197.161]
19 289 ms 282 ms 278 ms 203.181.98.10
20 298 ms 298 ms 297 ms 61.195.56.133
21 287 ms 292 ms 287 ms 219.117.144.6
22 295 ms 298 ms 299 ms 219.117.146.153
23 287 ms 290 ms 286 ms 219.117.146.141
24 293 ms 290 ms 286 ms 219.117.146.186
25 298 ms 299 ms 310 ms 124.150.154.122
Trace complete.
What worries me is the latency spike around the KDDI hops. Now, I know signals jumping across the Pacific can warrant a bit of increased ping, but numbers like that have me worried things are possibly getting jumbled along the way. Without my router, things go a bit faster, and surprisingly I'm able to log in to Port Bastok. If this ~50ms difference is enough to be timing people out with the 3001 error, then I dare say the servers have been configured to be a bit too sensitive.Code:Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\<omitted>>tracert 124.150.154.122
Tracing route to 124.150.154.122 over a maximum of 30 hops
1 * * * Request timed out.
2 13 ms 12 ms 13 ms <omitted>
3 15 ms 16 ms 14 ms te-0-11-0-2-ar03.mckeesport.pa.pitt.comcast.net [68.85.75.53]
4 11 ms 11 ms 12 ms te-8-3-ar01.mckeesport.pa.pitt.comcast.net [69.139.195.193]
5 18 ms 17 ms 18 ms te-3-0-0-0-cr01.ashburn.va.ibone.comcast.net [68.86.91.129]
6 18 ms 82 ms 16 ms xe-10-1-0.edge2.Washington12.Level3.net [4.26.6.5]
7 18 ms 17 ms 18 ms vlan52.ebr2.Washington12.Level3.net [4.69.146.222]
8 19 ms 20 ms 18 ms ae-5-5.ebr2.Washington1.Level3.net [4.69.143.221]
9 17 ms 19 ms 18 ms ae-82-82.csw3.Washington1.Level3.net [4.69.134.154]
10 25 ms 21 ms 19 ms ae-84-84.ebr4.Washington1.Level3.net [4.69.134.185]
11 85 ms 84 ms 85 ms ae-4-4.ebr3.LosAngeles1.Level3.net [4.69.132.81]
12 84 ms 83 ms 87 ms ae-63-63.csw1.LosAngeles1.Level3.net [4.69.137.34]
13 98 ms 86 ms 84 ms ae-1-60.edge2.LosAngeles9.Level3.net [4.69.144.15]
14 143 ms 141 ms 142 ms KDDI-AMERIC.edge2.LosAngeles9.Level3.net [4.53.228.14]
15 137 ms 136 ms 139 ms lacbb001.kddnet.ad.jp [59.128.2.101]
16 303 ms 269 ms 249 ms otejbb203.kddnet.ad.jp [203.181.100.153]
17 246 ms 246 ms 247 ms cm-ote221.kddnet.ad.jp [118.155.197.161]
18 226 ms 225 ms 226 ms 203.181.98.10
19 241 ms 243 ms 243 ms 61.195.56.133
20 236 ms 239 ms 240 ms 219.117.144.6
21 247 ms 247 ms 246 ms 219.117.146.153
22 252 ms 250 ms 250 ms 219.117.146.141
23 246 ms 248 ms 258 ms 219.117.146.186
24 247 ms 242 ms 223 ms 124.150.154.122
Trace complete.
And, well, I'm still of the stance it is something that had been tweaked along with the update.
Cannot log in on one character only after crash (POL-3001)
Printable View
-
05-28-2011, 11:23 PMSeriha
-
05-29-2011, 11:39 AMLadyRagefist
Finally, proof.
-
05-30-2011, 10:39 PMSheKicksHighSquare realy is clueless, please fix your translation error, it should read "make sure the following ports are not BLOCKED". Xi needs NO ports forwarded or mapped or any such thing.Quote:
Originally Posted by SE_James
-
05-31-2011, 12:20 PMpurehateSE Comcast Problem
This is definitely an issue between SE and Comcast. I got frozen after switching nations and starting Windurst 1-1. I entered Inner Horo Ruins then dead at downloading data. I tried all the normal reboots/ports/modems/files but I got same response from PC, Xbox, and PS3. My wife plays and is on same network but works fine. My resolution was to tether my cell to PC version and walk out of ruins. I was then able to go back to home router and Xbox version working fine. Will post a fix after speaking to SE tomorrow if I get someone that knows what they are doing (crosses fingers), but that is not likely. You may be able to have a friend off Comcast or login at wi-fi hotspot off Comcast to get out of area you are in till this is resolved.
PS From searches online this has happened before in 08 so hopefully they know how to resolve it by now. -
06-03-2011, 08:02 PMGarudaEban
I'm not sure if I should make this a separate post, but I think I have concrete proof that at least part of the 3001 error is on SE's side.
As I described above, my character was stuck zoning into the Sacrarium on May 22. At that time, my job was level 90 Corsair / 45 Black Mage. This is still confirmed when I bring up the character selection page (which I have been doing regularly, hoping the problem would resolve itself.)
However, on the LS Community site, my job is still displayed as Summoner/Black Mage, the job combination I had before logging in that morning. It has been 12 days since I became trapped, and in that time LS Community has failed to update my character properly. Others have confirmed that LS Community is working properly since that time, and I am not currently equipped with any gear from the latest update, in case there was any difficulty there.
If LS Community cannot tell what job I am currently on, then it is not just me who is experiencing an error with my character. I would greatly appreciate a response from SE on this matter, even if it is just a "That's interesting, we'll look into it." I posted a separate request in this thread back on the 25th, and while I knew I was asking for a lot, I expected at least a reply of some sort from SE. -
06-04-2011, 09:15 AMNakir
Tried to enter Qufim again and stuck, but i am able to walk thru fine on my laptop using the same router and same settings. I have set a static ip, forwarded ports to that ip, still on the one PC i can not enter Qufim.... meaning i can not finish abyssea.... wtf? I am getting a new HD and new copy of windows and reloading everything fresh with a new copy of FFXI ultimate and trying that.... i am convinced at this point there has to be some sort of corrupted file on my pc that the file check isn't picking up. we'll see what happens tomorrow.
-
06-05-2011, 12:20 PMLadyRagefist
So here is an interesting addition to my problem.
At a LAN party at my friends house at the moment (Comcast provider) and we are all logged in.
All ports open, router and modem are working fine, and have been forever. I go to leave my mog house, exiting to Port Jeuno, and get stuck at the same downloading data screen.
Here's the retarded part - my friend leaves his mog house to port jeuno and can get in fine without any problems.
So I go to log in my character on his laptop to move mine out of Jeuno just to get me unstuck...still sat at the downloading data screen which resulted in the same FFXI-3001 error.
So even on a different computer, I can't login to move my character out of jeuno. Instead, I had to ask my friend in GEORGIA to log me in and move me. End result = it worked.
This thread has grown to 7 pages of people all complaining about similar issues. Something is clearly wrong, SE.
I believe its time for some answers. -
06-06-2011, 12:52 PMCurejaa
I had the same problem on two occurences:
1) Zoning into Castle Oztroja... same description as everyone else downloading data screen appears and then the FFXI-3001 error
This happened a while ago and I was able to move my character by logging into my character on my other PC on the same router/modem.
2) Zoning into Abyssea-Altep at first I was able to do what is stated above (use my other PC) but now I can't log into that zone from either PC and a friend must log me in if I go into those zones.
I tried everything from modem/router reset, port forwarding, called ISP, checked files and reinstalled the whole game. Nothing worked.
So now I avoid both these zones... but its frustrating if you have a quest involving one of these zones :( -
06-07-2011, 06:51 AMpurehate
Update: After router changes and calls to the robot tech's "all I can do is tell you what ports you need open", I have got nowhere and refuse to pay for a service I cannot use. Account cancelled.
-
06-08-2011, 04:30 AMUltima
This happened to me 2 days ago. We just switched to comcast last Friday so I may be going back to Verizon since I did not have this problem before. I have been stuck in Abyssea-Altepa for 2 days now. I cannot log in and get the error 3001 as well. I have probably read every single post on any forum that I could find through google and the solutions that people actually say worked are sooooo varied it leaves me nowhere. Tried port forwarding , checked files. Im thinking its something with my IP address but its not really my responsibility to be going to earths end to figure this out by myself. Either its SE's fault or its my ISP. Im leaning towards it being Comcast. They are coming wed. to remove this Gateway/Hybrid modem and give me a seperate phone / internet router. If this does not fix it the only other thing I can think of is to switch ISP's. Also it is sad to see SOOOO many posts from past to present on this SAME issue and they were either not resolved or the problem somehow "fixed" itself. It would be nice to see updates at the bottom of threads. :(