Lobby Server error 2002 only with Dx11 Client

Hi there, I made a post a few days ago about having troubles connecting. Over a few days I could not log into FFXIV normally. The only way that would work is through a VPN. It's now somehow resolved itself with my Dx9 client. Unfortunately, I'm now unable to use the Dx11 client at all. I always get a 2002 lobby server error. Has anyone else had any trouble with this or found a fix? It's quite consistent, I just switch back to the Dx9 and I can log in no problem. I've checked permissions on each client. Making sure both versions have administrator privileges and the like. I've also allowed it through windows firewall, and tried disabling it completely. Does the Dx11 client use different ports? I haven't had success finding an answer or even a why. Any help is appreciated!

Thank you

Just to clarify, you were adding the ffxiv_dx11.exe file to your firewall, right? Did you also add it to any other security as well (anti-virus, Windows Defender/Essentials, etc.)?

**should note that some Anti-Virus programs may have a separate section for network rules in addition to the local file scanning rules that may need a rule set as well. Avast made a change like this a while back in the Web Shield section for adding exclusions for running processes. Just pointing it out in case it was overlooked.

I have. I've added it to the list of approved programs. I also added it to my old anti-virus (Avira and Mal-ware bytes). I've also now removed them. Thank you for the suggestion. I'm hoping someone has run into something like this before. As it's completely strange for this to happen. When it all started I was playing in the morning. Logged off(normally), and came back a couple hours later to it not working. I'm thinking there must be something I've overlooked but I just can't find it!

May want to check for Windows Defender. Especially if you made the move to Win10. Even in the older flavors, a lot of people don't even know it is installed. It has been causing headaches specifically in the Win10 installs, so may be worth a look if you haven't tried that already.

Already have. Gone through all of windows defender and disabled it, allowed DX11, allowed the launcher. No such luck. And I'm still on Windows 7. Haven't made the move yet.

I have this same exact problem.

I have two laptops that I use to play FF14. One of them I constantly keep updated with windows updates and the other I haven't used windows updates for about 4 months.

Once Dx11 support came out, I downloaded the patch on both my laptops.

The computer than I keep updated consistently gets the 2002 error when trying to use Dx11 but works perfectly fine with Dx9.

The other computer that I rarely keep updated worked just fine in both Dx11 and Dx9... Until recently. Last night I decided to get all the updates from Windows update and suddenly Dx11 doesn't work any more.

Checked to see if I had the latest Direct X and I do have the latest version.

Our problem must lie somewhere within Windows Updates changing some settings which I can't pin point down.

bugger. Haven't done my updates in a long time myself either. The only recent change from Winupdate that I can recall is the one that reset the SSL options in the inetcpl.cpl config screen (Internet Options, Advanced tab, TLS support options)--that annoying one that broke the launcher. Could be something odd like a Media Player update that has knackered up a DLL or something. Hate to even say it... but unless someone has already posted it somewher, will probably have to roll back updates (or roll them forward) bit by bit until it fixes or breaks it.

Thanks for the replies! Hearing that someone else had the problem too gave me a little hope that a fix might be found sooner. I took a look through my recent updates and I did actually get a security update on the 11th(the day it stopped working). I uninstalled the updates but unfortunately still can't connect. It must be something else. I'm going to continue to look through and see if anything else changed. If I find anything I'll let you know!

Sorry for bumping an old thread - I just figured out the problem. Opening up Command Prompt and typing "netsh winsock reset" without quotations has solved my problem.

THANK YOU!!!

This finally fixed my problem.