Server Issues?

[colomis]

If you're nervous about giving out your login information and you have a BLM buddy, there's another way to get rescued from zones like the Hall of Transference.

Have your BLM buddy unpartied in the zone.
When you log in, /sea Buddy name.
Invite buddy to party.
They will join party. You will be oblivious to this, but they can D2 you (or someone could just teleport you to a safe zone).

Note: /pcmd add buddyname will not work. I don't know why. But /sea will. Go figure. I guess my ISP filters /pcmd but not /sea.

Tried to do this with a WHM buddy of mine and teleport out, but to no avail. I sent a GM call while I was in the zone and it went through, but said that there was only 1 call to them. The other wierd thing was that I was there as NIN/WAR and was going to mijin gakure to try to get out, but when I pulled up my ability list, it listed all my THF abilities.

I hope that SE.........errrr my ISP figures out what the problem is, because this update is pretty sweet and I'd like to fully experience it, but until then, I guess I'll just stick to trying to get my flickering lantern. 0/70

[Drace]

I've tried everything suggested, still have certain dead zones when connected through my router, and other dead zones when I connect straight from my modem. (Literally had to use both types yesterday to make it to Dynamis, as B-Markets was a deadzone on the modem, and B-Mines was a deadzone on the router...)

Kept a mule logged in overnight for Bazaar and now there was apparently an emergency maintenance on certain zones with an update, and of course it won't let me connect to start the update.

Good times.

[Khamsin]

If they actually plan on fixing the issue, it'll require an Emergency Maintenance on all worlds, which means that FFXI will be shut down. Oh, and they'd also have to get a fucking clue. Not happening.

why don't you just tell us your view on what's going on instead of intentionally keeping us in the dark?

Don't turn into Map, Taj. Your knowledge of FFXI hacking has become your Ninurta's Sash, and the ego boost and popularity you've received from it is slowly twisting your soul. You gain pleasure from teasing people with it, always reminding others of this thing you possess so that they may fear and respect you. The dark tendrils of Arrogance and Pride have begun to sink in, slowly spreading through you.

There is still time!

It is too late for Map, someone already dropped him down a conveniently located bottomless shaft somewhere and everyone's forgotten about him; you still have a choice. You are supposed to bring balance to FFXI, not leave it in darkness! Join the Dark Side, you must not... or photoshop a Taj's Sash, I may.

The above post only contains 15% truth, and 85% artificial flavoring and preservatives.
Ok, maybe 25% truth.

[Taj]

I'm working on a fix right now, just be patient.

[Aaros]

I seriously think that this is a backbone peering/routing issue. It might be a router just before traffic his SE's network. I've been doing some packet sniffing with Ethereal, and whenever I enter my dead zone (lower jueno) from Rolanberry I see data being sent to a different IP. When I do a trace route to that IP it times out on a router that is upstream of SE. lolbadpackets

[Similli]

If they actually plan on fixing the issue, it'll require an Emergency Maintenance on all worlds, which means that FFXI will be shut down. Oh, and they'd also have to get a fucking clue. Not happening.

why don't you just tell us your view on what's going on instead of intentionally keeping us in the dark?

Don't turn into Map, Taj. Your knowledge of FFXI hacking has become your Ninurta's Sash, and the ego boost and popularity you've received from it is slowly twisting your soul. You gain pleasure from teasing people with it, always reminding others of this thing you possess so that they may fear and respect you. The dark tendrils of Arrogance and Pride have begun to sink in, slowly spreading through you.

There is still time!

It is too late for Map, someone already dropped him down a conveniently located bottomless shaft somewhere and everyone's forgotten about him; you still have a choice. You are supposed to bring balance to FFXI, not leave it in darkness! Join the Dark Side, you must not... or photoshop a Taj's Sash, I may.

The above post only contains 15% truth, and 85% artificial flavoring and preservatives.
Ok, maybe 25% truth.

rofl, quality there...

I'm fucking stuck in sea because I r0ed on the way to limbus as soon as I zoned in from a crag. I really don't want to have someone else log in for me and move me... is there any other way out? I haven't tried that d2 trick but I can't /sea so I doubt that will work. GM said he was unable to move my character too which is just bs...

Also if your working on a fix Taj would it work for Xbox? otherwise I'm still fucked ><

[Sine]

I'm working on a fix right now, just be patient.

Sweet!

[Taj]

I seriously think that this is a backbone peering/routing issue. It might be a router just before traffic his SE's network. I've been doing some packet sniffing with Ethereal, and whenever I enter my dead zone (lower jueno) from Rolanberry I see data being sent to a different IP. When I do a trace route to that IP it times out on a router that is upstream of SE. lolbadpackets

Incorrect, the problem is the opposite way. There's two things to consider. First, the server is receiving packets sent by the client. The fact that you can zone out is proof of this. Second, the client is receiving packets from the server, just discarding them because the header is mangled. Good fucking game Square-Enix.

[Aaros]

Ah so they f'ed up part of their networking code? Why they would have to change anything pertaining to their network protocols is beyond me. Same for making the plural of gil to gils.

Its not affecting me too much, I just have to zone around lower jueno. I haven't found another dead zone yet, but I'm not exactly actively trying to search for one either.

I seriously think that this is a backbone peering/routing issue. It might be a router just before traffic his SE's network. I've been doing some packet sniffing with Ethereal, and whenever I enter my dead zone (lower jueno) from Rolanberry I see data being sent to a different IP. When I do a trace route to that IP it times out on a router that is upstream of SE. lolbadpackets

Incorrect, the problem is the opposite way. There's two things to consider. First, the server is receiving packets sent by the client. The fact that you can zone out is proof of this. Second, the client is receiving packets from the server, just discarding them because the header is mangled. Good fucking game Square-Enix.

[BerenTebogo]

So you're fixing the 3113 error or just the disconnects from zones?

Either way, cool, but I hope its the 3113 error

[Pawky]

I'm working on a fix right now, just be patient.

Pleaseeee tell me this is going to work for PS2 also

[Paegan]

I seriously think that this is a backbone peering/routing issue. It might be a router just before traffic his SE's network. I've been doing some packet sniffing with Ethereal, and whenever I enter my dead zone (lower jueno) from Rolanberry I see data being sent to a different IP. When I do a trace route to that IP it times out on a router that is upstream of SE. lolbadpackets

Incorrect, the problem is the opposite way. There's two things to consider. First, the server is receiving packets sent by the client. The fact that you can zone out is proof of this. Second, the client is receiving packets from the server, just discarding them because the header is mangled. Good fucking game Square-Enix.

Mmm, but are you sure that it's SE who is reponsible for the mangling?

[Taj]

I seriously think that this is a backbone peering/routing issue. It might be a router just before traffic his SE's network. I've been doing some packet sniffing with Ethereal, and whenever I enter my dead zone (lower jueno) from Rolanberry I see data being sent to a different IP. When I do a trace route to that IP it times out on a router that is upstream of SE. lolbadpackets

Incorrect, the problem is the opposite way. There's two things to consider. First, the server is receiving packets sent by the client. The fact that you can zone out is proof of this. Second, the client is receiving packets from the server, just discarding them because the header is mangled. Good fucking game Square-Enix.

Mmm, but are you sure that it's SE who is reponsible for the mangling?

I'm positive, I'm looking into it right now and it's really interesting. It's definitely not a case of "oops, the packets got lost." Basically you zone in, the client and the server handshake like normal, the server sends you information about your surroundings, and then the client stops accepting packets from the server. The client still sends the server information, and it still parses it, but when the server replies the client ignores it. Looking further into it, it's not really something I'll be able to fix, there are a number of things that could be causing it, but the time it would take me to figure out what exactly is going wrong isn't really worth it. I suspect they'll ninja fix it soon, and pretend nothing ever happened.

[Elesirdur]

My dead zones are: Ru'Lude, Yhoator Jungle, South Sandy, Hall of Transferrence <-- got stuck here for like 6 hours due to the fact that I couldn't select anything in the environment to get out. I'm scared to go anywhere you have to select something in the environment to enter/leave. My friend from across town that is on the same ISP logged onto my character and moved me so I don't get how SE can blame ISP's.

I've got the same dead zones, plus Port Jeuno. I doubt we're on the same ISP (Shaw Cable, B.C., Canada) so it's got to be something about the way FFXI's interpreting network data.

PS: Good info Taj, makes a lot of sense from what I, and many others, have been experiencing.

[Hawky]

Mmm, but are you sure that it's SE who is reponsible for the mangling?

It has been happening since the update. So several ISP apparantly mess up somehow magically after a FFXI update, I don't think so

[Jeryhn]

I've been to most everywhere on the list so far and haven't found my own personal "dead zone" yet, so dunno.

I did have to restart my version update quite a bit to get it to go a little faster on update day, but that's probably meaningless.

[Khamsin]

I haven't found any dead zones either. I never had to restart my update either, it only took like an hour anyway since I went home over lunch to start the download right after the servers came up. I didn't update on my laptop until the next day, late night PST sometime. On neither computer have I had issues, so I don't think update issues has anything to do with it.

[Elesirdur]

Mmm, but are you sure that it's SE who is reponsible for the mangling?

It has been happening since the update. So several ISP apparantly mess up somehow magically after a FFXI update, I don't think so

And that's exactly I can't abide by SE's explanation. It isn't just a Daylight Savings Time issue, as I started having problems like this on Friday and Saturday before the DST switch. Furthermore, the problems only started after the March 7 update. The fact that the affected zones are not consistent for many players means that there is some client-side connection, but I'm far more inclined to believe Taj's explanation that the servers are somehow not sending out properly formatted packets to the clients or that the packets are being malformed in some way.

It's really pissing me off as I want to get to Ifrit's Cauldron to farm some Domodeki's and complete my Haku cluster set as well as help a friend farm Thief's Knife pop items, but I can't stay connected in Yhoator Jungle >_<

[Paegan]

Mmm, but are you sure that it's SE who is reponsible for the mangling?

It has been happening since the update. So several ISP apparantly mess up somehow magically after a FFXI update, I don't think so

It would only take one backbone provider to mess up to affect a large number of ISPs.

Just seems strange that the majority of people have no issues at all if it is SE's fault.

[Gregorio]

I knoew SE knows about it, but I figured I'd call anyway. Maybe if they get enough complaints they'll get their asses working on a fix extra fast. Anyway, their phone support line is just giving me the busy signal instead of putting me on hold or something. I guess tons of other people are calling in too. And their web support gives me this message:

"As of Mar. 9, 2007 5:00 (PST), we are aware of connection related issues with an underlying backbone outside of our servers control. This is not affecting all ISPs. This is affecting NA and EU players primarily. Please try again later. "

Conclusive proof that SE does not care about black peop...NA and EU players.