Jump to content
TrinityCore

CDawg

Members
  • Posts

    1477
  • Joined

  • Last visited

  • Days Won

    85

Posts posted by CDawg

  1. Here is a checklist that I created on another post: Your friendly neighbor that lives across the street is connecting to your machine.

     

    Your neighbor has the wtf modified with the public IP (DNS)... (check)

    Your neighbor is using the exact version to connect to your machine... (check)

    Your machine has the DB, the authserver, and worldserver all running on it... (check)

    Everything from the .conf has localhost or 127.0.0.1... (check)

    Your router has 8085 and 3724 forwarded... (check)

    The firewalls are enabled to communicate through 8085 and 3724... (check)

    Your neighbor can ping the public IP (DNS) that you obtained from, lets say whatismyip.com ... (check)

    You verified that public IP matches the DNS that you are hosting... (check)

    Last but, not least. You put the public IP in the DB.realmist, and relaunched authserver... (check)

     

    Your neighbor is able to connect... (fail)

     

    1 of the above steps is either missing, or needs to be reconfigured.

     

    I forgot to mention. If you modify your own .wtf file with your public IP (as if you are outside) and able to connect,.. than so can your neighbor ;)

  2. Ok, let's break this down. Your friendly neighbor that lives across the street is connecting to your machine.

     

    Your neighbor has the wtf modified with the public DNS... (check)

    Your neighbor is using the exact version to connect to your machine... (check)

    Your machine has the DB, the authserver, and worldserver all running on it... (check)

    Everything from the .conf has localhost or 127.0.0.1... (check)

    Your router has 8085 and 3724 forwarded... (check)

    The firewalls are enabled to communicate through 8085 and 3724... (check)

    Your neighbor can ping the public IP (DNS) that you obtained from, lets say whatismyip.com ... (check)

    You verified that public IP matches the DNS that you are hosting... (check)

    Last but, not least. You put the public IP in the DB.realmist, and relaunched authserver... (check)

    Your neighbor is able to connect... (fail)

     

    1 of those above steps is either missing, or needs to be reconfigured.

  3. If the map doesn't exist, then several things may have happened.

    1. The client (possibly) could be incomplete, when you used the mapextractor it skipped it, since it is missing.

    2. Wrong version of the mapextractor, did you use an older one?

    3. You placed them in the wrong directory.

     

    Did you get any error when you using all the tools?

    Are using the tools used that "you" compiled that was located in the /bin directory?

     

    I'm guessing number 1. (I could be wrong) but, there was an error extracting one of the oldest maps.

    or possible corrupted. Since it is extracting, then error's out.

  4. If the map doesn't exist, then several things may have happened.

    1. The client (possibly) could be incomplete, when you used the mapextractor it skipped it, since it is missing.

    2. Wrong version of the mapextractor, did you use an older one?

    3. You placed them in the wrong directory.

     

    Did you get any error when you using all the tools?

    Are using the tools used that "you" compiled that was located in the /bin directory?

  5. http://en.wikipedia.org/wiki/Point-to-Point_Protocol_over_ATM

    http://en.wikipedia.org/wiki/Point-to-point_protocol_over_Ethernet

    Almost the same thing.

    Still, this issue should probably be brought up with your ISP. Most ISP's block certain or an amount of incoming. I don't know how your DSL is setup, and I'm not a big fan of it.

    Also try turning off your 3rd party apps to test it.

    Temporarily:

    Turn off the anti-virus, firewall, any other network 3rd party apps. then ping your box. If you get a ping, then turn each app back on 1 by 1 as a process of elimination.

    If all that still fails... call your ISP.

  6. The DNS configuration is fine, but I can't ping my own ext IP (or my Dad's IP from my PC). Funny thing is I can ping my DNS from my PC (getting my ext IP back), but no response when I try it at my Dad's PC. But I can ping my Dad's IP from his PC, so there must be something wrong with either my PC or my router.. :(

     

    The External IP is resolved from your ISP. You can also try to reset your router it so that it changes the MAC address. The external IP should not change unless you have an agreement from your ISP and you have a static external IP. But, if you can't ping your own external IP and you are able to get on the internet, you configured something wrong. You may also have a special setting in your router to not allow pings, either way, you may have to call your ISP or the support line for your router.

    • Upvote 1
  7. @Matter94

    Ports opened = allow from firewall

    Ports forwarded = router/proxy settings

     

    Iv'e said this , time and time again.

     

    Everything is pointing to internal. Like baric mentioned above. The only external is the realmlist.DB. (Tell your friends to use the external in thier realmist.wtf file)

     

    Depending on the ports you have forwarded and opened. You only need 3724 for the authserver and 808* for your world.

     

    That's it!

  8. Please don't take this offensively, but I don't think you know what you are doing. You need the exact game client of 4.3.4 to extract the vmaps.maps,etc.. You get those tools after you finished compiling from the source you get here., there is a doc to install and update the DB to 434 (Looks like you already accomplished that)

    There is really nothing else more informative I can give you.

     

    The database and the core are alpha, early development, and are only meant to be used for development purposes.
     

  9. What on earth are you doing?

    From your original post, you grabbed the source from master (3.3.5a).

    All you need t do is load TDB_Full_3.3.5a, then apply the updates.

    TDB_Full_434 is for another version, and from what it looks like, you are extracting from a wrong client version.

     

    So the question now is: what version are you trying to load?

    You started to follow the instructions correctly, until you got to updates, than you loaded 434 on top of that. Than you started to extract on a wrong client version, probably with the wrong.

    What a fucking mess!

     

    First, Figure out what version you want to experiment with. 335a or 443.

    • Upvote 1
×
×
  • Create New...