how to get past 3102

[Aver]

As a network admin this makes absolutely 0 sense. But if it works it works. Also try this: http://forum.square-enix.com/ffxiv/t...o-Fix-for-3102

Right. Though, SE does get all crazy when you log in from a different IP without a token, so there could be a tie in to your specific IP somewhere in their DB.

Pulling at straws here though, it really makes no sense from a networking standpoint. That's not how ping works.

[SarynFireborn]

As a network admin this makes absolutely 0 sense. But if it works it works. Also try this: http://forum.square-enix.com/ffxiv/t...o-Fix-for-3102

There's some logic to this but I still find it unlikely.

What may be happening if this works is that the Na and JP servers are in different clusters. Because the NA servers are aware that the account actively has a character signed in it gives you an error and rejects the login. The difference being the JP servers likely share the same authentication servers but are not aware of the other server cluster, hence it does not see an active login and only sends a signal to the global authentication server that you've opened an active connection, so in response the NA account gets forcibly disconnected from the server.

[Gawan]

As a network admin this makes absolutely 0 sense. But if it works it works. Also try this: http://forum.square-enix.com/ffxiv/t...o-Fix-for-3102

And it doesnt make any sense at all. Cause I have a traceroute running most of the times Im running the game, to see if the lagg ingame could be cause by latency. Since Im a EU player connecting to the servers in Montreal.

[Alhanelem]

What worked for me was wait paitently for SE to fix the problem without complaining.

[Gucci_Charms]

What worked for me was wait paitently for SE to fix the problem without complaining.

I don't know why your statement made me laugh lol. But ya I have 0 issues logging in. I feel for those still experiencing the 3102 and 1017 issues.

[Abriael]

Doesn't make too much sense lol.

[Alhanelem]

I don't know why your statement made me laugh lol. But ya I have 0 issues logging in. I feel for those still experiencing the 3102 and 1017 issues.

I got the error, but it went away after about 5 minutes or so.

It's just hte duty finder server glitching out.

[DAMNLAMA]

What worked for me was wait paitently for SE to fix the problem without complaining.

I don't think anyone was complaining, sounds to me like the community is coming together and trying to help each other out by posting potential solutions to a persisting problems. But, if you prefer....

FUCK YOU SE! GET YOUR SHIT TOGETHER, HOW LONG DO I HAVE TO PUT UP WITH THIS CRAP?????? WTF, BITCH MOFO!

LOL, JK.

[Liv_Traisharan]

You know what could be legit is releasing and renewing your IP... I mean, long shot but you could try opening CMD and doing:

ipconfig /release
ipconfig /renew
ipconfig /flushdns

It's worth a try. It won't hurt anything either.

[Tiggy]

It may work because the fresh ping to the server directly may knock the server into realizing you aren't actually connected anymore. Probably not a sensible fix from a networking standpoint, but the server software might get a good nudge from it. Who knows. Took notes just in case I hit the 3102 error myself.