I encountered a problem where WideClient.exe wouldn't connect to the server. After some troubleshooting, I discovered the cause:
If you start WideClient.exe using a shortcut that was dragged out of the WideClient folder, it won't connect.
It must be launched from within the WideClient folder itself.
I seem to remember dealing with this issue once before (a long time ago) and it may even be documented - I just didn't see it this time around. This may be due to dependencies or configuration files (like WideClient.ini) that are path-dependent. Running it from outside the folder likely prevents it from accessing the necessary resources.
Hopefully, this helps others who run into the same issue.