Making MaNGOS Public?

[freeman725]

Before everyone starts bashing me about not reading guides and what not... I've read about 5 guides and set this up 5 times according to different people's methods to no avail. Here's what I have so far...

Keep in mind this is not being run on a repack. Repacks are against my religion. This is a fresh compile of mangos x64 with the latest revision of psdb running wow version 3.3.5. The realm and world servers start up without a hitch. After a login attempt there is no evidence of a login attempt in any of the logs.

First off I've tried running the host machine in the dmz on my router. So, port forwarding is not the issue. A question I have is, when port forwarding and not running in the dmz, is it better to select both tcp and udp forwarding on a single port or set up the table to forward the port on tcp and udp separately? It shouldn't really matter but I've heard in the past that routers are a pain when trying to port forward on both protocols at the same time rather than forwarding the same port on both protocols separately. I'm on a netgear router by the way.

I have my dyndns account set up with westpennwow.dyndns.org. Which the setup of that is pretty straight forward.

My realm database in the realmlist table is set to the dyndns adress.

My hosts file:

# 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
#	192.168.1.2	westpennwow.dyndns.org
#	192.168.1.1	westpennwow.dyndns.org
#	###.###.###.###	westpennwow.dyndns.org

Now I've tried the loopback as both localhost and with the dyndns address. The hosts file is where I get a little confused. The last address in the list is my external ip. In my mind I think the problem lies here for some reason. Also, call me noob, but why is the hosts file used when dns resolution is handled through dyndns and all ports are open?

And of course I have my wow realmlist set to the dyndns address.

No matter what I try, the wow client hangs on connecting for a few seconds and then says unable to connect. If it wont work with the host machine in the dmz or with all the proper ports forwarded, wtf is going on? Some more food for thought is I've tried it with my antivirus disabled and windows firewall disabled. Which also shouldn't matter being as I added the world and the realm server into the windows firewall exceptions. Ultimately, I'm friggin lost... So any help would be greatly appreciated.

[freeman725]

Anyone? Also one of the guides had me change the world server port from 8085 to 8050 in the config. What purpose does this serve? I've noticed that even if you change it in the config, it's still listed in the realmlist table as 8085 which caused me to not be able to connect locally. Do I need to change any of the bind ip's in the configs? None of the guides said to. idk.... HHAAAAAAAALLLLLLLPPPPPPPP!!!!!! been working on this all day lol

[Harambeqt]

List all ports you have opened in the router, submit a screenshot on the realmlist table in realms db.

[freeman725]

Not sure why the forwarded ports matters at all. I've tried it with the host machine in the dmz and it still wont work.