how to get past 3102

Hi guys ,

I figured out how to bypass 3102. Just cmd and ping the SE servers(should be pinging two different IPs). Make sure you ping the correct ones. Anyway I did that and logged in instantly. Hope this helps!

What worked for me was:

Create a character on a JP server.
Log in as said character then log out.
Log in on NA server character.

Quote:

---

Originally Posted by Dann

What worked for me was:

Create a character on a JP server.
Log in as said character then log out.
Log in on NA server character.

---

I tried to create a character on a JP server but it wouldn't load the list.
I tried to create a character on a NA/EU server and guess what I got: Error 3102 :/

Quote:

---

Originally Posted by Babydoll

Hi guys ,

I figured out how to bypass 3102. Just cmd and ping the SE servers(should be pinging two different IPs). Make sure you ping the correct ones. Anyway I did that and logged in instantly. Hope this helps!

---

This is called a coincidence.

Quote:

---

Originally Posted by Babydoll

Just cmd and ping the SE servers(should be pinging two different IPs). Make sure you ping the correct ones. Anyway I did that and logged in instantly. Hope this helps!

---

How would I find out what IP my server has?

ok, so i dont know if its a coindidence as Noosed said, or if it actually worked but i pinged
NA : 199.91.189.21
JP : 124.150.157.36

and now i can log in.
so its worth a try

thx a lot. For me it worked fine and that was not a coincidence.
I pinged 199.91.189.19 for EU Shiva.

For all IT-non-experts: start-button --> enter "cmd" ---> in new cmd window enter "ping <IP>"
IPs are
NA : 199.91.189.21
JP : 124.150.157.36
EU : 199.91.189.19

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

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

Quote:

---

Originally Posted by Alhanelem

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.

Quote:

---

Originally Posted by Cedri

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.

Quote:

---

Originally Posted by Alhanelem

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.

Quote:

---

Originally Posted by Noosed

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!

Quote:

---

Originally Posted by Babydoll

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.

Quote:

---

Originally Posted by Cedri

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.

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.

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.

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.

...

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.

Quote:

---

Originally Posted by 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.

---

have you tried it?

3102 is simply an error telling you that the server has not kicked your character out yet. With the recent fixes, the amount of time it takes to time you out depends on the server load and other factors. Pinging the server does nothing to hurry this process. It is a coincidence people.

Quote:

---

Originally Posted by ashikenshin

have you tried it?

---

If it doesn't work that way it doesn't work that way. Everything involving networking is designed to work a certain way.

Quote:

---

Originally Posted by Asriah

3102 is simply an error telling you that the server has not kicked your character out yet. With the recent fixes, the amount of time it takes to time you out depends on the server load and other factors. Pinging the server does nothing to hurry this process. It is a coincidence people.



If it doesn't work that way it doesn't work that way. Everything involving networking is designed to work a certain way.

---

While I would agree with you, I just tried about 5 times to get, pinged, and was allowed log in (although got a server error, appears my instance is bad). If it is successful so many times, it is no longer a coincidence.

As someone that is in IT, this makes no sense to me why/how it would work.

Square is incredibly lucky that there wasn't another AAA MMO, or hell, anything. That released side by side with this. I'm an avid supporter. and HUGE into FFXI. And I'm to the point now where I almost don't even care anymore to play.

ping the server ...

internet voodoo

Doesn't make too much sense lol.

Quote:

---

Originally Posted by Cedri

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.

Quote:

---

Originally Posted by Gucci_Charms

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.

This was working for me earlier tonight but it just stopped working.. any other IPs to hit for NA?

EDIT: Actually, I pinged the JP server. When I got 90k and 3102'd I was in a duty finder instance. Pinging the JP server fixed it for me. Goddamn it, SE!

Also the servers are unstable because they were too liberal with raising the cap after midnight EST tonight.