Jump to content
TrinityCore

Stuck at connected / infinite loop / login issues / battle.net


CFGhost
 Share

Recommended Posts

@Maibenrai : I will see that ..

@Gacko Yes, I scored, I did everything correctly, and it was working fine before entering 6.2.3. I know perfectly handling to do.

Result :

11/25 12:22:39.977  Login program=WoW platform=Wn64 locale=enUS
11/25 12:22:40.051  Component WoW.Wn64.20726
11/25 12:22:40.110  Component WoW.base.20726
11/25 12:22:40.193  Battle.net is Component Bnet.Wn64.37165
11/25 12:22:40.243  LOGIN: state: LOGIN_STATE_CONNECTING result: LOGIN_OK
11/25 12:22:40.299  Connecting to xx.xxx.xxx.xxx:1119
11/25 12:22:41.187  LOGIN: state: LOGIN_STATE_FAILED result: LOGIN_FAILED
11/25 12:22:41.252  Disconnected from xx.xxx.xxx.xxx
11/25 12:22:41.340  Client initiated Disconnect from xx.xxx.xxx.xxx
11/25 12:22:41.402  Client initiated Disconnect from xx.xxx.xxx.xxx
11/25 12:22:41.463  LOGIN: state: LOGIN_STATE_FAILED result: LOGIN_FAILED
11/25 12:22:41.518  Login program=WoW platform=Wn64 locale=enUS
11/25 12:22:41.574  Component WoW.Wn64.20726
11/25 12:22:41.644  Component WoW.base.20726
11/25 12:22:41.714  Battle.net is Component Bnet.Wn64.37165

 

LOGIN: state: LOGIN_STATE_FAILED result: LOGIN_FAILED

My account and password is good " test[at]test.tld " / " test " very light ^^..

Port is open 1118 1119 8085 8086 (UDP / TCP)

Alwais #114 error ; i dont understand :s

Link to comment
Share on other sites

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.

 

  • Upvote 1
Link to comment
Share on other sites

All PCs are running Windows 7.

In the last few days, I downloaded the most recent 6.x (6.2.3, 20726), compiled it and started up the server. On a separate PC, I patched to live and ran connection_patcher and ended up with my WoW_patched.exe etc.

I have gone through all the other setup functions for running a server on my LAN (port forwarding, accounts, ....).

The server in running on one small Windows 7 PC. The client is running on another Windows 7 PC. I am able to log in, create characters and play the game.

My problem is this;

  I want to run the client on a third Windows 7 PC as well. However, when I just copy the client files over to it and try to run, I get Battle.net error #114 when trying to log in.

Does this mean that on every client PC, I have to install and patch to live the WoW client and then create a WoW_patched.exe using the connection_patcher? I am only trying to get a couple friends and I to play in the same room from time to time. If the only solution is to go through the live patching over and over, I will probably not do it and keep it as one client and one server for myself.

Can someone please confirm if there is a way to port a functioning client over to a new machine without having to go through the patching to live again.

Thank You

 

Link to comment
Share on other sites

Since several weeks I try to setup a 6.x server and client but failed several times at client connection.

Setting up the database and compiling the source seems to work fine. I'm running everything local on 127.0.0.1.

However I'm stucking to understand even the wiki at Running and Connecting to Your Server. That's why I changed today the step by step guide in the wiki a little bit in the way I understand it. I would like to write a little bit more precise about this patching stuff but at the moment I can't because it's not working on my side. And as you can see today the wiki is not anymore readable (see this post).

THIS IS THE NEW EDITED TEXT:

After completing all the steps listed above you can now start your server.

  • Run the bnetserver and worldserver to run your server. Both must stay running for your server to accept connections to it.
    Tip: The bnetserver allows you to enter your username/password to connect to the Realm Selection screen, and the worldserver allows you to connect to the realm itself.
    Once you are in-game, the bnetserver can be safely closed if you wish.
  • Open the Config.wtf file inside your World of Warcraft\WTF folder.
    If it is not already set than change the first line to: SET portal "EU" or SET portal "US"
  • Login into the character selection screen of live/retail blizzard to download modules. (Without this you will get error 114 on login screen.)
  • Get latest connection_patcher (from your build/release folder) and apply wow.exe and/or wow64.exe on it by using the command console or drag&drop the exe files over the connection_patcher.
    WoW_Patched.exe or Wow-64_Patched.exe have been created, use this from now on.
  • Change Config.wtf: SET portal "<IP address used in realmlist table>"
    The IP in the Config.wtf file should be exactly the same as the IP address you entered in the realmlist table above. (Example: SET portal "localhost")

 

But I don't understand what exactly I have to do with login into a live Blizz server.

Do I have to login into my Blizz account with wow.exe, stay there with open wow.exe and apply the patcher exactly in this moment ?

Or was the idea to login to Blizz account, wait till everything is downloaded (how can I see that), than close wow.exe, patch the wow.exe and/or wow64.exe and use the patched executables later ?

I found some forum posts with different explanations, some also contradictory. May it's also a good idea to write some more sentences to the wiki about what the connection_patcher is for for a better understanding. Some of the patches you can see in the source code.

 

At the moment I have f.ex. an error 112. Unable to validate game version.

That's may because my client version is 6.2.3 (20779) and it seems that's newer than TC is supporting. Can I do something besides waiting for a TC update ?

12/6 14:52:57.175  Login program=WoW platform=Win locale=enUS
12/6 14:52:57.236  Component WoW.Win.20779
12/6 14:52:57.296  Component WoW.base.20726
12/6 14:52:57.369  Battle.net is Component Bnet.Win.37165
12/6 14:52:57.427  LOGIN: state: LOGIN_STATE_CONNECTING result: LOGIN_OK
12/6 14:52:57.488  Connecting to 127.0.0.1:1119
12/6 14:52:57.573  LOGIN: state: LOGIN_STATE_FAILED result: LOGIN_BADVERSION
12/6 14:52:57.636  Disconnected from 127.0.0.1
12/6 14:52:57.698  Client initiated Disconnect from 127.0.0.1
12/6 14:52:57.758  LOGIN: state: LOGIN_STATE_FAILED result: LOGIN_BADVERSION
12/6 14:52:57.821  Login program=WoW platform=Win locale=enUS
12/6 14:52:57.878  Component WoW.Win.20779
12/6 14:52:57.937  Component WoW.base.20726
12/6 14:52:57.997  Battle.net is Component Bnet.Win.37165

 

Link to comment
Share on other sites

Hello,

- If your client is 6.2.3:20779, you can't connect to TC server yet. You'll need to wait for new TC upgrade.

- To connect to your server you need to edit config.WTF to SET portal "ip of your server" and patch your WoW binary with the connection_patcher

- Login to a live account (was needed) to download bnet modules before patching the binary (the patcher patchs both binary and modules). Afaik, on Win/Linux it's not needed anymore because the patcher will download bnet modules automatically. On OS X, I still need to connect to a live account before running the patcher or I won't be able to connect to my server. Oh and another bug on OS X, you need to patch everytime you want to connect to the game.

Link to comment
Share on other sites

  1. Compile TrinityCore with tools.
  2. Check if you configured correctly realmlist IP.
  3. Copy connection_patcher on you WoW Directory.
  4. edit config.wtf from WTF/ folder
  5. set your external address to SET portal "IP/DNS ADDRESS"
  6. drag WoW.exe on connection patcher
  7. Try to connect to your server.(create bnetaccount from your worldserver console by "bnetaccount create EMAIL PASSWORD"

Port forwards : 1119,8085

Edited by svenstero
Link to comment
Share on other sites

  • 2 weeks later...

Hey everyone, I have made a server and I can connect and all that good stuff. However whenever my friend tries to connect it gives them the Battlenet error 2, I've tried as much as I can to solve this issue, even tried to use Hamachi and port forward instead but nothing has worked.I would appreciate any advice that is out there to help me here. Thank you in advance, the server is a Warlords 6.2.3 server running on the Trinity Core.

Link to comment
Share on other sites

Heloo there! Greetings from Poland.

I compiled a complete WoW server 6.2.3, I generated maps - all in all everything I've done one after the other - at least there I think.

I made the patch files wow.exe and WoW-64.exe for Windows client (server on Ubuntu MariaDB).

Config.wtf also completed the file as a link:

http://pastebin.com/7H8nkYYs

Unfortunately, I have a problem # 104 - i checked a lot of topics on Google, but unfortunately little specific information.

To registering users use the form below:
http://demo.ovh.eu/download/2a52aa75ffb5d7aa46e5b94c4c7ce4a1/www.zip

Probably it is evil (ps you better? Willingly accept)

Designed account gives the effect:

12/23 20:18:28.066  LOGIN: state: LOGIN_STATE_CONNECTING result: LOGIN_OK 
12/23 20:18:28.066  Connecting to 167.114.227.227:1119
12/23 20:18:28.314  LOGIN: state: LOGIN_STATE_FAILED result: LOGIN_UNKNOWN_ACCOUNT 
12/23 20:18:28.314  Disconnected from 167.114.227.227
12/23 20:18:28.314  Client initiated Disconnect from 167.114.227.227
12/23 20:18:28.314  LOGIN: state: LOGIN_STATE_FAILED result: LOGIN_UNKNOWN_ACCOUNT 
12/23 20:18:28.314  Login program=WoW platform=Wn64 locale=enUS
12/23 20:18:28.329  Component WoW.Wn64.20779
12/23 20:18:28.329  Component WoW.base.20726
12/23 20:18:28.329  Battle.net is Component Bnet.Wn64.37165

I have no idea where to find the problem (also tried to create a massacre CLI command: ".account create [email protected] admin")
 

 

 

 

Edited by zdzichu6969
Link to comment
Share on other sites

Hello,

First i'll tell you what i've done on my server (Debian 8.2) : 

  • downloaded sources
  • compiled sources
  • created maps, mmaps, vmaps, ...
  • Created databases, realmlist database is well configured
  • Started bnetserver and worldserver as screens
  • Created a bnet account ([email protected] / admin)
  • Changed the portal in Config.wtf on the client

Now when i'm trying to connect to my server i'm instantly disconnected... I've tried few 6.2.3.20779 WoW.exe patched but no one works... :(

Link to comment
Share on other sites

12/25 20:34:43.715  Login program=WoW platform=Wn64 locale=enUS
12/25 20:34:43.735  Component WoW.Wn64.20779
12/25 20:34:43.752  Component WoW.base.20726
12/25 20:34:43.770  Battle.net is Component Bnet.Wn64.37165
12/25 20:34:43.786  LOGIN: state: LOGIN_STATE_CONNECTING result: LOGIN_OK 
12/25 20:34:43.963  Failed to resolve poweredcore.com.logon.battle.net
12/25 20:34:43.978  LOGIN: state: LOGIN_STATE_FAILED result: DISCONNECTED 
12/25 20:34:43.993  Login program=WoW platform=Wn64 locale=enUS
12/25 20:34:44.011  Component WoW.Wn64.20779
12/25 20:34:44.026  Component WoW.base.20726
12/25 20:34:44.046  Battle.net is Component Bnet.Wn64.37165
12/25 20:34:44.066  Client Disconnect due to reason:8

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...