1
Forum Settings
       
This thread is locked

Let's sort this out.Follow

#1 Mar 11 2007 at 7:55 PM Rating: Decent
**
351 posts
Frankly I'm tired of watching the pingpong game of idiot logic going on here.

The connection argument breaks down to this: The people who can't connect or get R0 say it's SE's fault simply because it all started after the update.

The people who can connect say it's the ISP's fault simply because they can connect and someone else can't. Meanwhile there are people on the same ISP as the person who said "I can connect your ISP sucks", who have said they can't connect. I saw someone say they had Time Warner and they had no problem. While another person with Time Warner said they were getting the FFXI-3113 error and couldn't connect.

The logic on both sides is devoid of anything related to the word. What everyone seems to forget is that their connection has to pass through several other routers and servers on the way to FFXI that neither their ISP nor SE own. These connections that are beyond both companies's control are more than likely the culprits in a lot of the cases. Why do I think this? Because a few months ago I had this exact same problem and there wasn't an update for me to blame. For no apparent reason I just suddenly R0ed while playing and I couldn't get back on. My ISP had no ports or IPs blocked and SE said they had nothing to do with it as well. Yet I had access to another ISP and I had no problems at all using it to play the game. I later discovered that I could freely move around all the besieged areas on my main ISP while I R0ed in all the conquest areas. I went back and fourth on the phone between my ISP and SE for about a month until my ISP discovered the problem to be beyond their network yet not in SE's network. The only solution was to change the point of connection or POP server that I got to my ISP through. I'm not saying this is the case for everyone my point is that there are alternate reasons to the ISP vs SE argument. In this case the route your connection takes. Changing your IP works in some cases because the router out there that had you blocked in the first place now sees an IP that it doesn't have blocked.

Now if changing your IP did not work changing your POP server is probably the route you should look into taking. Tell your ISP you might need to change your POP server and make sure they don't mistake it for POP3. Your ISP will more than likely charge you for the change and if you're like me and have a static IP for a website or something you're going to lose your old one. This will give your connection a new route to take and hopefully a clear one. If this still doesn't work then the last option you have is to look for another ISP.

Edited, Mar 13th 2007 10:34pm by Pikko
#2 Mar 11 2007 at 8:00 PM Rating: Decent
heres what I think:

I think someone is running a MITM attack or traffic shaping on ffxi somehow, and they screwed it up, either intentionally or not.

Think about it.. its r0 meaning you cant get packets from SE, but you can still send stuff to them. You can chat and people can see your /tells, they just cant respond. Its only on certain zones.. meaning that some servers are being "attacked" and some are not.

The only other time I have seen an issue on the network like this was when there was MITM done on the router via arp poisoning, but the middleman computer's routing table was not set up right.


This makes sence since I can try multiple computers, internet connections, routers/no routers, and still can not connect to the same exact zones, no matter what I try.
This thread is locked
You cannot post in a locked topic!
Recent Visitors: 223 All times are in CST
Anonymous Guests (223)