If you check your login server log, you see that you are indeed connecting, and login server closes the connection and passes you over to char server. Now that you can't connect further means that it passes you either wrong, or unaccessible IP for char server. That is configured in conf/char-server.conf:
// Character Server IP// The IP address which clients will use to connect.// Set this to what your server's public IP address is.char_ip: IP address or DNS hereAlso, why I adviced to configure conf/subnet.conf is because sometimes (like in my case) you may have no access to server if you use outer IP/DNS, thus it helps to use local IPs for same subnet. So in short, your client seems aight, but you missed a turn during configuring the server itself. Also, be sure that char_ip is NOT assigned to 127.0.0.1/localhost, or the PC will try to connect to itself looking for char server after getting login accepted.
I've changed that value around multiple times; I changed it to my external IP to check (Loopback adapter is running therefore I can afford to do that) and I've used localhost/127.0.0.1. Neither seem to be changing the results.
Okay so it seems to work if I place the client into the same VM as my server...I can't connect to it from my main desktop however, which proves to be a problem. From what I can see, the PIN authentication won't drop even if I enter in one. Weird stuff so far.
Fixed PIN by restarting client. Everthing is working (In korean, but working). I just need to get it to work for my desktop...problem persists on laptop too as it can connect to the login and char server but it cannot connect to map server.