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.

[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.

[Babydoll]

This is called a coincidence.

Nah, my bf and whole fc did it and it worked. Have to make sure toy ping the correct IP though!

[Liv_Traisharan]

Nah, my bf and whole fc did it and it worked. Have to make sure toy ping the correct IP though!

That's... screwed up. Totally not discounting you trying to find a workaround for 3102, but that doesn't make any sense. Any network engineer or sysadmin in the room will tell you that's bonkers.

[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.

[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.

[BlazeChronic]

I just powercycled my router in P4, relogged and it worked.

Haven't had 3102 since P4, but idk that's what I did and it worked while my buddy was stuck on 3102 for over 24 hours.

[roflcaust]

...

I don't want to rain on your parade OP, but this is not a fix. This has absolutely nothing to do with you getting past or "fixing" Error 3102. That just pure coincidence.

When you ping an IP address, you are sending 32 bytes packets of information (very tiny bits of data) to see what is the response time between your request to send data and receive data from the FFXIV servers.

It doesn't do anything server/client side. It's a very simple command that enables you to check the latency between your computer and SE's servers.

[ashikenshin]

...

I don't want to rain on your parade OP, but this is not a fix. This has absolutely nothing to do with you getting past or "fixing" Error 3102. That just pure coincidence.

When you ping an IP address, you are sending 32 bytes packets of information (very tiny bits of data) to see what is the response time between your request to send data and receive data from the FFXIV servers.

It doesn't do anything server/client side. It's a very simple command that enables you to check the latency between your computer and SE's servers.

have you tried it?