Jump to content
TrinityCore

Dormammu

Members
  • Posts

    26
  • Joined

  • Last visited

Posts posted by Dormammu

  1. @Aokromes It was entirely my fault, I missed one setting. RealmServer port as you stated was supposed to be set to the default of 3724, however - my config was showing the default to be 8085.

    Additionally, earlier in the thread, I failed in showing the proper screen capture in the AuthServer.config document. As CDawg caught, for *WHATEVER* reason, my config was showing an odd default. Cant explain it as I followed directions and downloaded and compiled only TC material.

    RBb9F4F.png

  2. Attn: Community..... With the help of @CDawg, I was able to fire up my server and connect to it. To resolve said issues, I went to AuthServer.config and changed my port to 3724. The **EDIT** default I had in front of me was something completely different. Furthermore, I renamed my WTF folder to WTF_OLD and had the client build me a new one. I entered the IP Information as well as vital config info and attempted log in with success! Someone give @CDawg mad props! :Salute

  3. 8 minutes ago, CDawg said:

    Ok.

    So let's start from scratch. config.wtf reads from what's in realmlist.wtf (unless it doesn't exist). If realmlist.wtf exists with your server info, then config.wtf needs to be updated.

    If I want to switch servers (domains), I blow away the config.wtf, then I update realmlist.wtf to point to my friend's server for debugging purposes, etc... The client builds a new client.wtf from what realmlist.wtf has in it.

    That make sense? ;)

    Clear as crystal. :) (Mostly) If I create a new realmlist.wtf then it should be stuck *WHERE*? Yet, if I decide to do away with the realmlist.wtf entirely, what needs to be entered into config.wtf in order for my server to be detected by the authserver?

  4. @CDawg Thanks. I'll give the 10.x address a shot as well. You're right when it *SHOULD* work using localhost address, but it continues to baffle me. Last night, with the help of a friend here on TC, he remoted into my server and took a look. He couldn't find anything out of the ordinary either. He has a Master server but not 3.3.5. If theres such a subtle change that we are missing, we have yet to find it. :(

     

  5. Im basically still trying to figure out why my 335 server will not allow any localhost connections. Im trying to pick someone's brain that if I copy the configuration from my Master server (which works just fine) to my 335 server - will it completely muck it up? (Both servers are on completely different boxes by the way.)

    So.....theoretically, if  I change my RealmServerPort to 3724, should that allow  my 335 AuthServer to grant access, particularly if it's giving me that error (2316) on login attempt?

  6. I am working on creating my 3.3.5 server on a different box from my Master server. I don't know why I am having so many issues considering I have followed directions as I did Master flawlessly. By comparison, 3.3.5 has been one phenomenal headache. Onwards I march though. Perhaps you lot can help me with what ails me.

    After installing everything as directed to in the Requirements | Core Installation and Configuring / Compiling, etc...... I successfully opened WorldServer / AuthServer but got this on client boot.....

    soG7yPN.jpg

    Going back and forth to my setup directions, I thought I followed it all fine.

    My config.wtf.....for your reference....

    http://i.imgur.com/2rjqf7a.png

    Realmlist within Data/enUS for reference.....

    http://i.imgur.com/lQto7K8.png

    AuthServer Config......

    http://i.imgur.com/NQN9e5p.png

    WorldServer Config......

    http://i.imgur.com/g69wU3R.png

    Test account was successfully created using test:test, which is what was failing on login attempt with client. Running Windows 10.

    Can anyone glance over these please and advise me? Maybe I missed something, but I thought I followed it all to the letter.

    Thanks!

     

     

×
×
  • Create New...