The lobby server connection has encountered an error (2002).

[grimremember]

Hello, I've had this problem now for over a month every time i try to log in my start button is grayed out and after about 30 seconds the game says error (2002). Now I have tried at all times of the day/night so its not the servers being too full or anything and nothing with my router/internet setting has been changed, I just can't log into the game.

Does anyone have any fixes to this error? I'm so sick of not being able to play

[Raist]

sounds like something is blocking your connection to the lobby server. Are you running any kind of local firewall? One of the more common suspects.

Check your security logs to see if any attempted connections to IP's starting with 124 or 199 are getting blocked--if you see them, whitelist them (allow them full access).

Can also try testing these addresses by pinging them from a command prompt:

124.150.157.158
199.91.189.74
199.91.189.31
124.150.158.117
124.150.157.190
124.150.157.126

Those are all IP's I've seen the client use since I was back in Beta.

Can also try pinging this server name too:
frontier.ffxiv.com

It SHOULD resolve to the 124.150.157.190 IP listed above.

[grimremember]

For the first part I've tried with the firewall off and nothing changes.

For the second i don't understand how to do any of what your talking about lol


EDIT: I tried what you said with some help from google and for the website and the IPs when i pinged them the response i got from all of them was


request timed out
request timed out
request timed out
request timed out
Packets: sent = 4, Received = 0, Lost = 4 (100% loss)

[Raist]

Then something is blocking your traffic to SE's network, in most cases it is something either locally on your system or on your local network. The trick will be tracking down just what it is. If you were pinging the IP's in a CMD prompt (black window, with a white text command line), try running a tracert to one of them in the same fashion. You would type it in just like with the ping command, but using the tracert command instead, like this:

tracert 124.150.157.190


This should spit out a list of each hop your connection is making trying to get to the server. If it stalls immediately, there is something going on locally, most likely local security or an issue with your protocol stack or something. After that, you can follow each device past your system in turn. Basically, in a typical network, if it stalls after the first hop, it may be your router, after the second hop, your modem, and beyond that it is something beyond your local network--as in it may be your ISP or one of their partners having issues.

[Furlamseere]

It seems that there have not been any further posts about this concern being an ongoing issue. Because of this, we are considering it to be resolved. If this does continue to be a concern, please create another thread to further discuss resolutions or contact the Support Center at support.na.square-enix.com for assistance.

- Furlamseere