SE is against the U.S.Military

[Siros]

1st of all,im in the Army and im stationed on Kadena airbase,Okinawa Japan.This issue is not only me but every player on Kadena airbase to include Air force,Marine,and Navy personnel aswel.

We are armed forces personnel,thats all thats here so i feel extremely offended by SE for this one.

There has got ta be a way ta fix this,im losing my mind.... Can a GM plz read an respond ta this thread?,i would hate ta stay up past 2am so i can call Playonline when they open just ta be told that its on my end an theres nothing they can do....

This is not on my end,SE is filtering Mediatti Broadband Communications so now everyone on Okinawa stuck under Mediatti cant play FFXI...

We cant switch ta another isp because Mediatti is the only isp on base an they wont allow other isp's ta provide service on base so they monopolize the market,hence forth we are stuck not able ta play FFXI.

SE please remove the filter!!! How much clearer do i need ta make the issue ta you? and if you wont remove the filter atleast explain why you are filtering us in the 1st place.This is rediculous.....

[RAIST]

it may in fact me Mediatti causing your problem. They have been hammered for years for poor quality of service. They also do that traffic shaping crap to combat P2P sharing (torrents and such). FFXI relies heavily on UDP traffic--lots of small packets streaming full time. It is possible that Mediatti's anti-piracy crap is blocking FFXI traffic.


Try pinging or tracert one of the servers to see if you get through. This is one that is registered in DNS:

ffxi00.pol.com

***I would rather have sent this info to you via PM, but we don't have the option. Please, people don't start spamming this IP for testing.****

If you get a response from it, then I doubt SE is blocking your IP.

[Siros]

This is in regards ta the FFXI-3113 Protocol Timeout error....

[Siros]

it may in fact me Mediatti causing your problem. They have been hammered for years for poor quality of service. They also do that traffic shaping crap to combat P2P sharing (torrents and such). FFXI relies heavily on UDP traffic--lots of small packets streaming full time. It is possible that Mediatti's anti-piracy crap is blocking FFXI traffic.


Try pinging or tracert one of the servers to see if you get through. This is one that is registered in DNS:

ffxi00.pol.com

***I would rather have sent this info to you via PM, but we don't have the option. Please, people don't start spamming this IP for testing.****

If you get a response from it, then I doubt SE is blocking your IP.

I'm not sure on that,but i have spoke with Mediatti an they say its SE filtering them.As for ffxi00.pol.com i'm lost,im not that tech savy,how do i use that? If its a web address it doesn't work for me......

[RAIST]

open a DOS command prompt. I forget exactly where it is in Vista/Win7--but there is a link to it in the programs menu. In XP, you just go to start/run and type cmd <enter>. the cmd command might work in Vista/Win7 in the little search box too, I guess.

Youll get a little black sort of terminal window where you can type commnads to run programs. You just type the command and hit the enter key. Those are two zeros after the ffxi btw, sometimes it's hard to tell the difference with some fonts.

ping ffxi00.pol.com

Should look something like this:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Administrator>ping ffxi00.pol.com

Pinging ffxi00.pol.com [124.150.154.122] with 32 bytes of data:

Reply from 124.150.154.122: bytes=32 time=202ms TTL=42
Reply from 124.150.154.122: bytes=32 time=194ms TTL=42
Reply from 124.150.154.122: bytes=32 time=192ms TTL=42
Reply from 124.150.154.122: bytes=32 time=193ms TTL=42

Ping statistics for 124.150.154.122:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 192ms, Maximum = 202ms, Average = 195ms

C:\Documents and Settings\Administrator>

If it is showing something like a timeout error, then something is blocking the traffic. You might be able to track down some info to forward to your ISP to help them trouble shoot by running this command:

tracert ffxi00.pol.com

and get something like this:

C:\Documents and Settings\Administrator>tracert ffxi00.pol.com

Tracing route to ffxi00.pol.com [124.150.154.122]
over a maximum of 30 hops:

1 2 ms <1 ms <1 ms 10.10.100.1
2 10 ms 8 ms 7 ms cpe-098-025-064-001.sc.res.rr.com [98.25.64.1]
3 14 ms 15 ms 17 ms cpe-024-031-201-109.sc.res.rr.com [24.31.201.109
]
4 17 ms 17 ms 17 ms 24.93.64.70
5 23 ms 22 ms 22 ms ae-3-0.cr0.atl20.tbone.rr.com [66.109.6.82]
6 36 ms 56 ms 35 ms ae-3-0.cr0.hou30.tbone.rr.com [66.109.6.36]
7 43 ms 41 ms 42 ms ae-0-0.cr0.dfw10.tbone.rr.com [66.109.6.39]
8 76 ms 75 ms 78 ms ae-3-0.cr0.lax30.tbone.rr.com [66.109.6.0]
9 81 ms 102 ms 78 ms ae-1-0.pr0.lax00.tbone.rr.com [66.109.6.129]
10 79 ms 79 ms 79 ms pacnet.com.any2ix.coresite.com [206.223.143.138]

11 183 ms 182 ms 182 ms gi6-0-0.cr1.nrt1.asianetcom.net [202.147.61.166]

12 183 ms 182 ms 183 ms gi1-0-0.gw1.nrt5.asianetcom.net [202.147.0.178]

13 251 ms 206 ms 183 ms squareco.asianetcom.net [203.192.149.210]
14 184 ms 182 ms 182 ms 61.195.56.121
15 212 ms 184 ms 183 ms 219.117.144.21
16 185 ms 182 ms 182 ms 219.117.144.2
17 182 ms 182 ms 182 ms 219.117.144.14
18 183 ms 186 ms 182 ms 219.117.146.149
19 193 ms 195 ms 193 ms 219.117.146.129
20 190 ms 190 ms 192 ms 219.117.146.182
21 194 ms 192 ms 194 ms 124.150.154.122

Trace complete.

C:\Documents and Settings\Administrator>

If it is a routing issue, you will see the laste point that it passed through. That is the point of failure that the ISP will need to look into.

You can copy/past all of this into an email to forward to your ISP so they can try to find just where the routing error is happening and take action if it is on their end. In the upper left corner of the window there will be a little icon the looks like C:\ on a black button. Click that for drop down menu and seleck Edit/select all, then click it again and select Edit/Copy. Then you can open an email, word, notepad, whatever and hit <Control> and V keys to paste it all.

[RAIST]

This is in regards ta the FFXI-3113 Protocol Timeout error....

That is a screwy error...and very misleading. At one time, it was actually an internal error with SE or their local ISP. Lots of people were simply unable to login, regardless of which ISP they were on. People would get into POL, launch the game, and get to loading character selection screen and then timeout.

It could be that something is being blocked from you to SE, SE to you, or across one of SE's 3 subnets used to run the game. For some people it was a DNS routing issue.

That is another thing you could try. It's a lot to try to detail out here, and would be a lot easier if I could copy paste some screen shots. You may want to get a friend familiar with setting up IP settings in Windows to tinker with it. Basically, you want to try changing some of your DNS options--toggling NetBIOS settings, name registration, etc. to see if it resolves it. You could even go so far as setting a different DNS server to use (many cable ISP's will have it set to Automatic, but you can manually set IP's to use and point them to an OpenDNS server on this list: http://www.dnsserverlist.org ) to see if it alters your pathing to bypass a stalling route.

[Siros]

Dude,your awesome,Ty^^ I figured out what it was for after a few seconds an did a ping -n 50 an let it go,the time is jumping between 42ms an 56ms.Idk if that makes a difference.Anyways thanx for the help Raist,i appreciate it greatly.

Did a trace aslo,this is what i got:

C:\Users\Siros>tracert ffxi00.pol.com

Tracing route to ffxi00.pol.com [124.150.154.122]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms SIROS44 [192.168.1.1]
2 9 ms 9 ms 10 ms 10.104.128.1
3 12 ms 11 ms 9 ms sr1.spearpt.com [180.131.208.2]
4 10 ms 10 ms 11 ms 211.120.234.41
5 11 ms 10 ms 13 ms 211.120.224.49
6 205 ms 46 ms 43 ms tkgw-mlx-2-tko.ii-okinawa.ad.jp [211.120.225.74]

7 44 ms 43 ms 44 ms tkwrt2x-dix.sakura.ad.jp [61.211.233.1]
8 44 ms 41 ms 50 ms tkwrt1s-wrt2x.bb.sakura.ad.jp [59.106.249.197]
9 44 ms 43 ms 44 ms tkort3-wrt1s.bb.sakura.ad.jp [59.106.251.137]
10 43 ms 44 ms 46 ms AS17685.ix.jpix.ad.jp [210.171.224.200]
11 47 ms 46 ms 46 ms 61.195.56.121
12 45 ms 82 ms 44 ms 219.117.144.21
13 46 ms 45 ms 54 ms 219.117.144.2
14 46 ms 50 ms 44 ms 219.117.144.14
15 47 ms 49 ms 45 ms 219.117.146.149
16 44 ms 43 ms 47 ms 219.117.146.129
17 44 ms 42 ms 43 ms 219.117.146.182
18 44 ms 42 ms 44 ms 124.150.154.122

Trace complete.


I have no idea what exactly ta look for or how ta tell which one is the problem source if there is one...

[RAIST]

I'm not sure on that,but i have spoke with Mediatti an they say its SE filtering them.As for ffxi00.pol.com i'm lost,im not that tech savy,how do i use that? If its a web address it doesn't work for me......

lol... this happens all the time... ISP points at SE, SE points at the ISP. More often than not, it is actually a routing problem out in the cloud of hardware bbetween you and the server. the trick is finding just who is at fault.

I got caught in that loop once. I did the pinging/tracert testing and found the stall. Reversed the lookup on the last IP and found out it was in Nova Scotia--I'm in South Carolina. Called ISP, got to their Tier3 support in Atlanta and gave them the last IP before the stalled connection. About 30 minutes later, it was resolved and I didn't have to change anything on my end.

I know it's a lot to take in, but if you have someone that tinkers with this stuff as a hobby (or their job), might want to pull them in and help you out when you contact the ISP. This may be Mediatti's snafu, or it could be the ISP SE is using. The trick is getting some useful information to point someone in the right direction so SOMETHING gets done.

[RAIST]

Dude,your awesome,Ty^^ I figured out what it was for after a few seconds an did a ping -n 50 an let it go,the time is jumping between 42ms an 56ms.Idk if that makes a difference.Anyways thanx for the help Raist,i appreciate it greatly.

Did a trace aslo,this is what i got:

C:\Users\Siros>tracert ffxi00.pol.com

Tracing route to ffxi00.pol.com [124.150.154.122]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms SIROS44 [192.168.1.1]
2 9 ms 9 ms 10 ms 10.104.128.1
3 12 ms 11 ms 9 ms sr1.spearpt.com [180.131.208.2]
4 10 ms 10 ms 11 ms 211.120.234.41
5 11 ms 10 ms 13 ms 211.120.224.49
6 205 ms 46 ms 43 ms tkgw-mlx-2-tko.ii-okinawa.ad.jp [211.120.225.74]

7 44 ms 43 ms 44 ms tkwrt2x-dix.sakura.ad.jp [61.211.233.1]
8 44 ms 41 ms 50 ms tkwrt1s-wrt2x.bb.sakura.ad.jp [59.106.249.197]
9 44 ms 43 ms 44 ms tkort3-wrt1s.bb.sakura.ad.jp [59.106.251.137]
10 43 ms 44 ms 46 ms AS17685.ix.jpix.ad.jp [210.171.224.200]
11 47 ms 46 ms 46 ms 61.195.56.121
12 45 ms 82 ms 44 ms 219.117.144.21
13 46 ms 45 ms 54 ms 219.117.144.2
14 46 ms 50 ms 44 ms 219.117.144.14
15 47 ms 49 ms 45 ms 219.117.146.149
16 44 ms 43 ms 47 ms 219.117.146.129
17 44 ms 42 ms 43 ms 219.117.146.182
18 44 ms 42 ms 44 ms 124.150.154.122

Trace complete.


I have no idea what exactly ta look for or how ta tell which one is the problem source if there is one...

Cool, that means your generic traffic is passing to that server. So it doesn't look like your IP is geting blocked by SE to that subnet. Gonna give you two more to try, eadch one hits different sections of their networks. If these pass OK, then it's not likely someone blocking you guys deliberately--but possibly filtered traffic. THAT would be most likely on Mediatti, or someone else in the loop that is trying to crack down on BitTorrent users. Or it could be the internal problem again that SE had once before. Here are the server names:

pt008.pol.com
ci000.pol.com

Again , those are two letters, then 3 numbers in the first part of those addresses. If you don't get a good ping test --ie if one drops out or has a big jump in response time--then it might be an IP to trace for problems enroute. Just to simplify things on your end, I would maybe forward that to Mediatti for them to check the situaion out. Just tell them, "ey.. this is one of the servers that my connection is freaking out on when I try to play the game, the connection keeps dropping" Once they have that specific endpoint they should be able to try some diagnostics on thier end.

heck..it might even be worth it to just forward all three of those names to them and say these are the networks the game is trying to reach and can't--you guys figure it out. That is what you pay them $75 USD a month for anyway... lol

Edit: Oh, forgot to tell you earlier. to exit those command boxes, just type the word exit and press enter to shut them down.

[Siros]

Good point,i think i will have ta inform them since the $75-80 a month is going ta waste on my end if i cant play.Those other 2 passed ok aslo so now i have no clue but ill let Mediatti know of them an hope maybe something will get done.I still blame SE in a way too though for letting this happen,lol.