Leaderboard

You could try setting logging to debug(2) or trace(1) in bnetserver.conf and check from there? Default is just info (3).

I "think" I had "LOGIN: state: LOGIN_STATE_FAILED result: LOGIN_FAILED" problem and I had to rerun connection_patcher. Then it started to work. Have you applied https://github.com/TrinityCore/TrinityCore/commit/035a2b122e57c7b7406f830d471bc284b0101238 ? I had that problem too, because I moved sources from D to C and my config files still pointed to D, so auto patching didn't work.

Please check Logs\connection.log. Successful connection looks like : 11/25 08:24:11.514 Login program=WoW platform=Wn64 locale=enUS 11/25 08:24:11.544 Component WoW.Wn64.20726 11/25 08:24:11.569 Component WoW.base.20726 11/25 08:24:11.608 Battle.net is Component Bnet.Wn64.37165 11/25 08:24:11.635 LOGIN: state: LOGIN_STATE_CONNECTING result: LOGIN_OK 11/25 08:24:11.743 Connecting to xx.xxx.xxx.xxx:1119 11/25 08:24:11.918 LOGIN: state: LOGIN_STATE_AUTHENTICATED result: LOGIN_OK 11/25 08:24:11.947 ClientConnection Initiating: COP_CONNECT code=CSTATUS_CONNECTING 11/25 08:24:11.978 LOGIN: state: RESPONSE_CONNECTED result: LOGIN_OK 11/25 08:24:12.105 ClientConnection Completed: COP_CONNECT code=RESPONSE_CONNECTED result=TRUE 11/25 08:24:12.129 ClientConnection Initiating: COP_AUTHENTICATE code=CSTATUS_AUTHENTICATING 11/25 08:24:12.251 ClientConnection Completed: COP_AUTHENTICATE code=AUTH_OK result=TRUE 11/25 08:24:13.203 ClientConnection Initiating: COP_GET_CHARACTERS code=43 11/25 08:24:13.320 ClientConnection Completed: COP_GET_CHARACTERS code=44 result=TRUE 11/25 08:24:18.066 ClientConnection Initiating: COP_LOGIN_CHARACTER code=81 11/25 08:24:19.939 ClientConnection Completed: COP_LOGIN_CHARACTER code=82 result=TRUE 11/25 08:24:23.935 ClientConnection Completed: COP_LOGIN_CHARACTER code=82 result=TRUE 11/25 08:24:24.511 ClientConnection Initiating: COP_GET_CHARACTERS code=43

https://community.trinitycore.org/topic/10582-6x-is-now-the-supported-branch-623-20726/#comment-69555