They updated the servers on the 9th or something (Pallas update) that made it so that only one connection can be established at any moment (PS2 limitations) so everyone is d/cing.
They updated the servers on the 9th or something (Pallas update) that made it so that only one connection can be established at any moment (PS2 limitations) so everyone is d/cing.
Over in the compiled data thread I see a few people using Shaw service that are experienceing R0 in a lot of the same areas. Perhaps we can find a common link there? Same with people using that Roadrunner service (I don't know the telecom co., but they're a big US one)Originally Posted by Khamsin
the update is for aura steals.Originally Posted by Gladiator
and same 3113 problem here. Has been enable uPnP, open ports, hard reset routers etc, things still not solved unless i either play at school or hook it directly to modem![]()
How can you be so sure not everyone is having this problem?Originally Posted by Khamsin
Has everyone been to every zone since the update?
I didn't have any problems with this until I zoned into a zone most people probably would never visit, Monarch Linn, and if it wasn't for that encounter I would have claimed to "not have any problems."
I've noticed that people who get error 3113 often seem to be using TELUS. I know I am.Originally Posted by Elesirdur
I've been reading over the stickied thread regarding R0 zones and I notice something different. There are three people, including myself, who have posted in that zone that say they are using Shaw Cable in BC. Two of us have some of the same zones going R0, and the other has totally different zones. ie. I and the other R0 in Ru'Lude and Port Jeuno, where as person #3 R0s in Lower Jeuno. I assume that we've all tried all four of the Jeuno zones to see what works and what doesn't.
Therefore, as we're all using the same ISP and 99% sure we're all connected to the same backbone, BUT experiencing R0 problems in dissimilar zones it leads me to believe that it's not completely related to one's ISP.
Yes, this affected me a long time ago, and it was enough to make me quit the game for a couple months. Finally one day I decided to randomly see if FFXI would work, and voila, it was working fine again.Originally Posted by SephirothYuyX
I really, really hope that kind of time frame doesn't repeat itself this time around.
I am using Shaw Cable in Nanaimo BC, and I can access all areas of jeuno, the dead zones I've noticed to date are rolanberry fields, dynamis-beaucedine, and the sanctuary of zitah. I'm sure there are more.
in 2005 i am laughingOriginally Posted by Snowknight26
in 2007 i am angry
Of those zones, I know that I can access Rolanberry - I was bazaaring there forever today. HOWEVER, I couldn't perform a search in that area even though I had a proper connection.Originally Posted by dritero
i didnt mean to start a MAC Address war. i just wanna know wtf is going on. Why does changing my MAC Address allow me to get to some zones i couldnt before. Like...i guess i'm just confused on what exactly is broke "besides the packet handling thing". How does my IP changing, change the way the client handles incoming packets?
Why did you end every comment on that youtube link with an exclamation point?Originally Posted by Izzy
I know it makes no logical sense, but honestly, changing your IP address really does change the problem. For the last 3 days now I've been travelling around by cycling through a few IP addresses that I've found that belong to my ISP (also Shaw, like many others apparently), and I've learned the dead zones for each of them.Originally Posted by SephirothYuyX
For instance, if I use xxx.xxx.xxx.195 (which is the IP I will be assigned every time if I turn the settings to automatic), Port Windurst is dead. However, if I change my TCP/IP settings and tell it to assign me xxx.xxx.xxx.206 (which is usually free), Port Windurst will work fine, but, for example, Yuhtunga Jungle is dead. If I want to do something in Yuhtunga, I can switch back to either .195 or go to my usual third option, .201. Both of those will work in Yuhtunga, however, if I'm going fishing, I shouldn't use .195 because it will be dead in Sea Serpent Grotto.
Yes, it's weird as hell, but it's really how it is. I've found other IP addresses that I can't even consider an option, because they cause that 3113 protocol error that other people are reporting.
Now, without actually knowing anything about how FFXI's servers are set up, here's my theory on what's going wrong:
SE says that their technicians have checked the servers multiple times, and they're fine. That's because they probably are. There's nothing wrong with the servers. This is pretty obvious because it IS possible to get into these zones, just not from certain IP addresses.
So then, imagine for the sake of argument that there's say... 3 servers that can handle Sea Serpent Grotto for Sylph. Some programmer at SE decides that a clever way to do load balancing would be a chunk of code like this that gets run when you zone in to any zone:
ip_address_sum = 0;
ip_address_array = client_ip_address.split('.');
for (i = 0; i < 4; i++)
ip_address_sum += ip_address_array[i];
assign_client_to_server(zone, ip_address_sum % 3);
Now, if somehow they messed up that assign_client_to_server function so that assigning it to the #0 server always fails, but assigning to #1 and #2 work, we have a situation like what seems to be happening. MOST people can connect to the zone just fine, but for some reason the same IP address always fails when zoning in.
Note that I have absolutely no clue if they're actually doing this, but I'm assuming something like this is going on, because it explains the problem perfectly.
!!!!! = new cruise control 2 coolOriginally Posted by Taj
So a linkshell mate on Leviathan was complaining about how Nyzul Isle is a dead zone for him on his laptop, but not his desktop. I asked him if his laptop and his desktop share the same broadband connection, and they do.
Mmm, I smell blatant lies on Square-Enix's part.
going to test that theory right now
edit; hmm geee my other stuff cant download the update. I guess the update server is down
Well, SE did say its not a fault of their servers or on their side of the connection, and they're probably right. They never denied it was a problem with the client software or something going wrong at the client side.Originally Posted by Taj
you know, i thought about that after i posted the replies. At the time, I think i was just obsessed with !!!!!Originally Posted by Taj
I would just like to add I'm sitting dead in West Altep because of this fucking ridiculous problem, and can't really play the game until it's fixed.
Northeast US, Comcast is my ISP. Other dead zones are Metalworks and Upper Jeuno. Releasing/renewing IP doesn't work.
-edit- Homepointing worked, much to my surprise! Stuff clearly is getting sent and being recieved.
nyzul was a dead zone for me with my router in. Connected straight from modem to my comp and i could enter nyzul. Fucked up huh :\Originally Posted by Taj