FFXI / ISP Incompatibility Shuts Users Out
falcon5768 writes "Since Tuesday 9/28, an incompatibility between how Final Fantasy XI addresses a network connection with it's Playonline Viewer and Optimum Online's broadband service has blocked well over 1000 players out of the game. The only thing both companies do agree on is that the problem is a minor one. Numerous players have been told by Optimum Online that it is not a priority. Likewise Square Enix has no notice of the problem on their website, but an option on their call menu tells players they are aware of the problem and it is being worked on before hanging up.
I mean, it's not like these folks are actually paying to use a service or anything like that. Besides, it's only 1000 people. Given that they've sold several hundred thousand units, with nice monthly subscriptions attached, they don't have to worry about a few hundred people.
After all, it's not like it'll affect anything important. You know, like the bottom line.
--AC
..It sounds the heads at Squeenix are at least aware of the situation, though they seem to be passing the buck, which is kinda messed up. Last I heard, PlayOnline uses Port 25 to connect to a network (the same one that mail clients use), and that Optimum closed it off, for some reason. In any case, I wish you luck, and I wish there was something I could do besides this.
There is no chance that I could care less about this story. But it seems like a lot of people are clueless.
1. PlayOnline is thoroughly stupid for using port 25 to connect to the network. Though shalt not retain ports under 1000, and well-known ones at that.
2. Optimum Online is doing something mostly responsible, which is blocking port 25 to help stop the spread of spam using its broadband lines.
3. Choo choo, it's the clue train, making stops at the following common sense conclusions.
- Playonline, fix your stupid-ass software.
- Optimum, do what you do.
- FFXI players, use this time to reintroduce yourself to the great outdoors.
I've noticed all Sony articles lately are critical. Did One Slashdot Way just get a big shipment of Xboxen perhaps?
BC
See, this is what you get when you don't standardize your online network. Ports getting opened all over the damn place. I'm not surprised at all that they've got these problems, given the total lack of structure in Sony's online service (or lack thereof). In comparison, Xbox Live uses three ports: UDP 88, UDP 3074, and TCP 3074. What happens, I wonder, to people playing Final Fantasy online through a router that are also running a webserver? If your standard port 80 is being forwarded to the webserver, then it'll be totally screwed up, and some people wouldn't know why without sniffing it out.
Here was my post on 2003-11-03 to my local LUG on how to fix ffxi's buggy networking problems when playing behind a linux firewall:
l es -I PREROUTING -t nat -p tcp -s $intnet -d $extip --dport 51220 -j DNAT --to 61.195.48.234:51220
I started playing Final Fantasy XI online for PC this weekend.
(Yep, had to boot into windows for first time in long time
and had a couple crashes to remind me why I stopped using it)
Anyway, I have a linux box as my firewall doing NAT and the game
would not work with the error:
FFXI:3100 Could not connect to lobby server
Tech support just told me it's my fault for using a linux firewall
and implied their system has no bugs and claimed it works with NAT.
After some packet sniffing, I discovered that some bug in the game's
network code was causing it to send packets to the external ip of
my firewall(port 54001) instead of to square enix's lobby server.
A web search of port 54001 came up with a japanese language page
which had some iptables rules to use to let FF online work from
a playstation through a firewall. Those did not work, but the page
also had a list of Square's servers and which ports they use so
I made some quick rules to forward any misdirected packets to those
listed servers and voila it all worked.
So, in case anyone happens to have problems with this bug in
PlayOnline and Final Fantasy XI not working through NAT on
an adsl connection, here is the solution.
Here are the relevant parts of my firewall script:
extint="eth0"
extip=`ifconfig eth0|grep 'inet addr'|cut -f2 -d:|cut -f1 -d" "`
intint="eth1"
intnet="192.168.1.0/24"
iptab
iptables -I PREROUTING -t nat -p tcp -s $intnet -d $extip --dport 51240 -j DNAT --to 61.195.48.236:51240
iptables -I PREROUTING -t nat -p tcp -s $intnet -d $extip --dport 51300 -j DNAT --to 61.195.48.238:51300
iptables -I PREROUTING -t nat -p tcp -s $intnet -d $extip --dport 51301 -j DNAT --to 61.195.48.239:51301
iptables -I PREROUTING -t nat -p tcp -s $intnet -d $extip --dport 54000 -j DNAT --to 61.195.48.239:54000
iptables -I PREROUTING -t nat -p tcp -s $intnet -d $extip --dport 54001 -j DNAT --to 61.195.48.209:54001
iptables -I PREROUTING -t nat -p tcp -s $intnet -d $extip --dport 54002 -j DNAT --to 61.195.62.141:54002
iptables -I PREROUTING -t nat -p udp -s $intnet -d $extip --dport 54120 -j DNAT --to 61.195.62.144:54120
iptables -I PREROUTING -t nat -p udp -s $intnet -d $extip --dport 54246 -j DNAT --to 61.195.62.158:54246
There is some idea floating around it could be modem related, specifically there is a running trend going that its older motorola and non-motorola modems not able to connect, surfboard modems after a certain model number (or people who used the buisness connect option which is 100 dollars a month) havent had a problem and can get and stay in
as for some other facts, Optimum online is not completely a ISP provider, they send some of their stuff out to other ISP's, They are also a small cable provider, providing for the NE tri-state Area, but only parts of it (Comcast is the other provider and no one has had problems with them or any others and conectivity) There where no software updates to FFXI recently to have changed anything square was using, but I dont know on the OO end if they did any server/firmware updating between monday and tuesday night.
and yes I know its quite funny how much people are bugging out. I dont use OO but my girlfriend does and shes more pissed that shes paying 30 dollars a month of ISP and 13 dollars a month on the game +2 characters and no one is giving her info,
Still the question must be asked, when companies get into a fight like this, what options do customers really have?
"Slashdot, where telling the truth is overrated but lying is insightful."
The main problem with this, or rather, one of the major problems (as I found out trying to cancel my subscription)....you can't pay unless you've got their crap installed. I tried telling the idiot on the phone that I was cancelling *because* their crap game screwed up my computer, and they basically said, "Well, too bad, now you can't play our games EVER AGAIN." Big loss......*rolls eyes*
I hate it for the folks who are paying two bills to be unable to play a game, and the very least that should happen is getting credit on their FFXI accounts for the days they're locked out.
;)
On the other hand, I'm forced to consider that the spin on this particular "feature" might be that it's not an outage, it's a one-step recovery program for MMORPG addicts. Were I on their tech support staff, I'd be tempted to try it at least once.
I monitored my network this morning (working Comcast connection) to see what ports and servers POL is using when it first loads up (this is captured Ethereal data from startup of POL to about thirty seconds after I successfully logged in): TCP 34707 to 51240 TCP 443 (https) to 4072 TCP 51220 to 4068 TCP 51220 to 4067 TCP 51220 to 4065 TCP 51220 to 4064 TCP 51220 to 4063 TCP 51240 to 34707 TCP 51304 to 4071 UDP 1036 to 53 (dns query, pt008.pol.com) TCP 4060 to 54000 UDP 1036 to 53 (dns query, ci000.pol.com) TCP 36022 to 51240 TCP 4060 to 54000 TCP 34707 to 51240 TCP 36022 to 51240 UDP 1036 to 53 (dns query, pp000.pol.com) TCP 4061 to 51220 UDP 1036 to 53 (dns query, ma000.pol.com) UDP 1036 to 53 (dns query, pp000.pol.com) TCP 4062 to 51260 UDP 1036 to 53 (dns query, po000.pol.com) TCP 4062 to 51220 TCP 4063 to 51220 TCP 4064 to 51220 TCP 4065 to 51220 UDP 1036 to 53 (dns query, wh000.pol.com) As you can see, other than the high-range nonspecific ports (4000-52000), POL is using 53 for DNS queries and 443 for SSL. The suggestion was made that it could be that OO's network is confusing the TCP 443 to 4072 connection for a web server, but it could also be DNS problems, since some people can get far into the login process while others cannot (and there are a lot of DNS queries made).
Did I miss when they changed their name after the merger? I had a quick scout on google but couldn't see anything official to that note.
I only really want to know because 'Squenix' sounds bloody stupid if you ask me.
Sony didn't make FF:XI. Besides, the article doesn't mention if this is a PC/PS2 only issue.
X
4 days later, the problem was finally solved... seems it was a routing issue with how Optimum Online routed the Playonline signal the entire time.... Bonus to the fix, they now fixed the download speed for the network as well which was a crawl for most people before
"Slashdot, where telling the truth is overrated but lying is insightful."