SE is against the U.S.Military

[RAIST]

yeah...in your correspondence, also let them know that the game streams UDP traffic constantly. This is something that often triggers the packet shaping traps. Basically what you will be hinting at is they need to let the traffic flow freely to/from those network segments because it ISN'T BitTorrent traffic. SE owns at least 3 segments--3 blocks of 256 IP addresses (they can figure the subnet details our from those addresses)--so it throws out a LOT of UDP packets, which is what I suspect may be the problem as Mediatti has a history of clamping down on streaming traffic in the past.

I feel your frustration. My brother was in the desert last year and I was trying to work with him remotely from here--remote desktop all the way to Afghanistan trying to fix laptops that were freaking out like this, only to find it was something off-base causing issues. It wasn't much fun. It's one thing to not have access to a game for stress relief, but when you are trying to keep a video stream going so troops can get in touch with loved ones at home and it keeps going down because someone thinks it's porn traffic--that's a crock.

Best of luck over there, and keep up the good work.

[Siros]

Will do,thanx again^^

[Rdelavega]

So next time they block your ISP just launch a missile at them.

[Alhanelem]

SE is not "against the US Military." You're not being singled out, though your requests for help would be more effective by behaving in a civil manner becoming of an Armed Forces member.

It seems your issue has been resolved, but in the future you might want to try a different tone for your post.

[Karbuncle]

SE is not "against the US Military." You're not being singled out, though your requests for help would be more effective by behaving in a civil manner becoming of an Armed Forces member.

It seems your issue has been resolved, but in the future you might want to try a different tone for your post.

^This!

Civility can go a long way~

[Siros]

SE is not "against the US Military." You're not being singled out, though your requests for help would be more effective by behaving in a civil manner becoming of an Armed Forces member.

It seems your issue has been resolved, but in the future you might want to try a different tone for your post.

The issue isnt resolved i still cant get past the accept or decline screen.It hangs at 65% at setting up connection then after 2 mins tells me Error code:FFXI-3113 Protocol Timeout error.I still cant play.

[RAIST]

This error has a long and nasty history--a lot of times it was due to routing issues either locally, or in between SE and the client. Everytime it rears it's ugly head, it is always a bugger--have to exhaust all efforts on fixes locally first, then move towards SE by checking with the local IT Admin's and then your ISP.

SE sends out pings and such from some servers that are not initiated by the client (so some firewalls will block it, as it was not communication started locally), those could be getting blocked and tripping the error. They may be blocking DNS pings or something to guard against DOS attacks, so there may not be a way around it if you are having to go through base security protocol.

looking at the tracert--is that a local router that you can make changes too? If so, could test putting the system with FFXI in the DMZ, or at least making sure port forwarding is set up to point to that system--TCP/UDP traffic for these ports:
25,80,110,443,50000-65535

Another thing some people did in the past in their home setups was clone the MAC address of the system on to the router--old post on a forum with a short how-to on doing it:
http://killingifrit.com/forums/topic...outers-only-3/

But I doubt that is a solution in this one particular case.

Ultimately, someone is going to need to check traffic logs to see if inbound traffic (from SE) is getting blocked by firewalls and such, then whitelist that traffic to the routers of the players. This will be a pain in the butt to do probably, especially if you are having to go through the ISP. I'm going to list the IP info I am aware of from SE, based on what I have detected in my firewall over the years--it isn't all, but is a starting point that I used to find certain subnets. It may be easier for the non-tech saavy people to just forward the rest of this post to the IT people (local dept. or ISP) to research the problem:

**SE's own support will advise to forward these ports to the system: TCP/UDP 25,80,110,443,50000-65535 **

**The following IP's have been detected as in use by the game, both through netstat and by catching them as being blocked by a firewall. They may use both TCP and UDP protocols, and some may just show up as generic DNS/Ping traffic as well. I have done reverse lookups, tracerts, and pulled up info through WHOIS to diagnose connectivity issues and verify who is leasing the IP's--only two IP's did not show a DNS entry, but they ARE in the subnet leased to SE**

dns1.square-enix.com through dns4.square-enix.com, in order:
202.67.53.31, 202.67.53.95, 202.67.53.32, 202.67.53.96

pt008.pol.com: 202.67.62.103 and also 202.67.62.70

wh000.pol.com: 202.67.54.55
ci000.pol.com: 202.67.54.52

ffxi00.pol.com: 124.150.154.122

Pings blocked by my firewall when having issues connecting to zones, did not resolve DNS names, but ARE in a subnet leased to SE. White-listing these IP's resolved my connectivity issues IMMEDIATELY without contacting anyone:

124.150.152.96
124.150.152.99

At the very least, they could try to enable/allow traffic from these sites to your router/system to see if it gets things moving forward. These are the specific IP's working for me though in the US--might need other IP's within the same subnets. SE leases the entire /24 subnet (xxx.xxx.xxx.1 - 255) around these IP addresses, so they could also try to enable and allow:

202.67.53.0 /24 (202.67.53.1 to 202.67.53.255)
202.67.54.0 /24 (202.67.54.1 to 202.67.54.255)
202.67.62.0 /24 (202.67.62.1 to 202.67.62.255)
124.150.152.0 /24 (124.150.152.0 to 124.150.152.255)

[Siros]

Raist you are always helpful buddy,thank you^^ i have had my isp company come by an check this out for themselves and they figured out its not my router,but yet it is something between them and SE.But i will give them this info so maybe it will help them figure it out.Thank you again.




P.S. Yes i did go off the deep end with this post title,but i was extremely frustrated so hope people understand.Yea i should have though before naming it...

[Siros]

Hey Raist,
these are the last tracert's ive done.I figure the Astrix's mean there a problem...


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

Tracing route to wh000.pol.com [202.67.54.55]
over a maximum of 30 hops:

1 2 ms <1 ms <1 ms SIROS44 [192.168.1.1]
2 14 ms 18 ms 11 ms 10.104.128.1
3 * 20 ms 12 ms sr1.spearpt.com [180.131.208.2]
4 * 18 ms 19 ms 211.120.234.41
5 13 ms 15 ms 13 ms 211.120.224.49
6 44 ms 47 ms 44 ms tkgw-mlx-2-tko.ii-okinawa.ad.jp [211.120.225.74]

7 49 ms 49 ms 48 ms tkwrt2x-dix.sakura.ad.jp [61.211.233.1]
8 * 46 ms 45 ms tkwrt1s-wrt2x.bb.sakura.ad.jp [59.106.249.197]
9 50 ms 50 ms 49 ms tkcrt2-wrt1s.bb.sakura.ad.jp [59.106.251.141]
10 76 ms 55 ms * 210.173.176.26
11 56 ms 52 ms 56 ms 219.117.144.2
12 * 49 ms 45 ms 219.117.146.149
13 52 ms 51 ms 55 ms 219.117.146.129
14 45 ms 52 ms 54 ms 219.117.147.38
15 51 ms 63 ms 75 ms 202.67.54.11
16 52 ms 54 ms 56 ms 202.67.54.55

Trace complete.

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

Tracing route to ci000.pol.com [202.67.54.52]
over a maximum of 30 hops:

1 2 ms <1 ms <1 ms SIROS44 [192.168.1.1]
2 12 ms 9 ms 13 ms 10.104.128.1
3 13 ms 12 ms * sr1.spearpt.com [180.131.208.2]
4 13 ms 16 ms 17 ms 211.120.234.41
5 * 21 ms 18 ms 211.120.224.49
6 44 ms 43 ms 45 ms tkgw-mlx-2-tko.ii-okinawa.ad.jp [211.120.225.74]

7 43 ms 52 ms 43 ms tkwrt2x-dix.sakura.ad.jp [61.211.233.1]
8 46 ms 47 ms 46 ms tkwrt2b-wrt2x.bb.sakura.ad.jp [59.106.249.201]
9 48 ms 43 ms 52 ms tkcrt2-wrt2b.bb.sakura.ad.jp [59.106.251.61]
10 47 ms 46 ms 48 ms 210.173.176.26
11 59 ms 62 ms 55 ms 219.117.144.2
12 63 ms 46 ms 49 ms 219.117.146.149
13 45 ms 49 ms 49 ms 219.117.146.129
14 47 ms 48 ms 46 ms 219.117.147.38
15 49 ms 49 ms 46 ms 202.67.54.11
16 46 ms 52 ms 49 ms 202.67.54.52

Trace complete.

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 3 ms <1 ms SIROS44 [192.168.1.1]
2 10 ms 9 ms 12 ms 10.104.128.1
3 13 ms 18 ms 14 ms sr1.spearpt.com [180.131.208.2]
4 14 ms 14 ms 15 ms 211.120.234.41
5 17 ms 20 ms 15 ms 211.120.224.49
6 46 ms 55 ms 49 ms tkgw-mlx-2-tko.ii-okinawa.ad.jp [211.120.225.74]

7 44 ms 44 ms 49 ms tkwrt2x-dix.sakura.ad.jp [61.211.233.1]
8 50 ms 42 ms 47 ms tkwrt1s-wrt2x.bb.sakura.ad.jp [59.106.249.197]
9 46 ms 48 ms 50 ms tkcrt2-wrt1s.bb.sakura.ad.jp [59.106.251.141]
10 47 ms 45 ms 42 ms 210.173.176.26
11 49 ms 44 ms * 219.117.144.2
12 46 ms * 47 ms 219.117.146.149
13 53 ms 54 ms 60 ms 219.117.146.129
14 45 ms 49 ms 52 ms 219.117.146.182
15 45 ms 45 ms 54 ms 124.150.154.122

Trace complete.

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 17 ms 12 ms 12 ms 10.104.128.1
3 18 ms 16 ms 17 ms sr1.spearpt.com [180.131.208.2]
4 14 ms 12 ms 21 ms 211.120.234.41
5 14 ms 15 ms 16 ms 211.120.224.49
6 295 ms * 49 ms tkgw-mlx-2-tko.ii-okinawa.ad.jp [211.120.225.74]

7 51 ms 46 ms 44 ms tkwrt2x-dix.sakura.ad.jp [61.211.233.1]
8 46 ms 45 ms * tkwrt1s-wrt2x.bb.sakura.ad.jp [59.106.249.197]
9 49 ms 51 ms 50 ms tkcrt2-wrt1s.bb.sakura.ad.jp [59.106.251.141]
10 47 ms 52 ms 48 ms 210.173.176.26
11 56 ms 58 ms 57 ms 219.117.144.2
12 * 57 ms 45 ms 219.117.146.149
13 49 ms * 51 ms 219.117.146.129
14 63 ms 60 ms 59 ms 219.117.146.182
15 46 ms 44 ms 44 ms 124.150.154.122

Trace complete.


Any ideas?,I think i figured out whitelisting but i have a friend here who thinks they might know how to do that.But this loox bad with astrix's in it,an i havent whitelisted anything yet.

[Glamdring]

What they meant about the decorum was that the military wasn't the problem, it's that ISP or SE themselves, the military is not a factor in the equation.