toekutter1134 Posted April 17, 2016 Report Share Posted April 17, 2016 I read all the faq's and unable to figure this out. I have pulled down the latest off of git | Compiled and have a working Bnet and worldserver |I have patched the client on the machine. |created accounts via TC shell prompt| changed the config.wtf for my local lan ip (all config and setup use local lan IP not 127... but I have tried both) I get this in the client BattleNnet.log (windows 10) 4/16 21:00:13.262 [IBN_Login] OnRealmJoin | code= (225) 4/16 21:00:13.262 [GlueLogin] Fatal error while logging in | result=( | code= (225) | localizedMessage= | debugMessage=Error joining realm) 4/16 21:00:13.262 [IBN_Login] Front disconnecting | connectionId=1 Can anyone point me in the right direction? Link to comment Share on other sites More sharing options...
toekutter1134 Posted April 17, 2016 Author Report Share Posted April 17, 2016 Here is what I am seeing: My Patched 64 - 21463 should be currently supported. My Trinity Core TC>TrinityCore rev. d82a2cf47118 2016-04-16 19:05:32 +0100 (master branch) (Win6 4, Release) (worldserver-daemon) ready... My bnetserver.conf LoginREST.Port = 8081 LoginREST.ExternalAddress=10.1.1.8 LoginREST.LocalAddress=10.1.1.8 Any Ideas or Thoughts? Link to comment Share on other sites More sharing options...
Nay Posted April 18, 2016 Report Share Posted April 18, 2016 Make sure that you have applied the SQL updates. There's one in /sql/updates/auth/6.x that changes the realm versions. Link to comment Share on other sites More sharing options...
Aokromes Posted April 18, 2016 Report Share Posted April 18, 2016 Updated https://community.trinitycore.org/topic/12451-updating-or-starting-with-trinitycore-issues/ Link to comment Share on other sites More sharing options...
Recommended Posts