New Trinity Core 2/ Mangos Problem when trying to go Public [No-Hamachi]

[daphtpunk]

Well, as the title says, I am having a problem with people OUTSIDE of my LAN network connecting to my server. I spent over 12 hours today troubleshooting and still have not got anything working. At the moment, I have the TrinityRealm.conf and TrinityCore.conf files unchanged in the respect that both are still using 127.0.0.1 for the connecting Hostname. I have my Windows Host file edited with a configuration like this...

# Copyright (c) 1993-2009 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
#      102.54.94.97     rhino.acme.com          # source server
#       38.25.63.10     x.acme.com              # x client host

# localhost name resolution is handled within DNS itself.
#	127.0.0.1       localhost
#	::1             localhost

127.0.0.1 MY DYNDNS.ORG HOST [ localhost ]
192.x.x.x MY DYNDNS.ORG HOST [ internal ip ]
64.x.x.x MY DYNDNS.ORG HOST [external ip ]

On top of that I have my Realmlist.wtf on other PC's outside my LAN set to my DYNDNS.org Host. They all get stuck at "Connecting..." when trying to join from outside my LAN.

Im not sure what else to do. I've tried everything I can think of, and most of the guides on here are for ArcEmu. Any input would be appreciated and +Rep

Thanks again.

[SYnical]

Sounds to me like ports are not forwarded correctly on your router, check your realmlist port, and if that isnt the case, check that the realm ports and ip's match up with what the guides tell you to do, try switching them to your external and one localhost etc and allthough usually untrue, i've found the setting localhost to react very differently to 127.0.0.1 when placed in different spots in the config (server).