H0zen

Edit mangosd.conf and change the console log level to 0. For files change it to 1. Restart mangosd after editing.

Your client does nothing because you didn't handle the connection step right.
When the client is successfuly authenticated by the realm daemon, it is redirected to mangosd daemon and the first step, of course , is to establish a connection via TCP socket. When the connection is established, the server will send SMSG_AUTH_CHALLENGE packet. THIS IS THE FIRST PACKET YOU HAVE TO SEND AND IS MANDATORY!!!
The client will respond to this packet with a CMSG_AUTH_SESSION packet, and this is where the miracle happens.  The server has to handle this packet and has to create the so called session. If it succeeds, the server will send SMSG_AUTH_RESPONSE like yours.  Because the intialization of Warden module is part of making the session, the server can send (but is not enforced to) various SMSG_WARDEN* packets, and this is what you already noticed.
Hope this helps! 

All these issues comes from a wrong advice given in the mentioned install tutorial. All versions of MaNGOS have their own ACE integrated in the source code, so you don't need to mess with downloading and installing ACE separately. The guide says "Use External ACE libraries. Allows you to use the ACE libraries coming from your system. Untoggle this option only if you know what you are doing. " But this should read "Untoggle this option UNLESS you know what you're doing".

So, the solution is to clear everything, and repeat the install and build process, BUT WITHOUT EXTERNAL ACE. You'll be amazed how smooth it'll compile and install.

Please go to Player.cpp file and change lines 1920-1926 into

if (m_regenTimer != 0)
    return;

Rebuild and send us the feedback