comradeboris

Fixed! Here's what I had to change to get it working: 1) Opened port 3306 for SQL service 2) When I was modifying my Realm DB, from reading the guides it would seem that the "Data" table entry is all matters, I didn't realise that I also had to update the "default" table. I was making the inverse mistake that others were. D'oh! 3) When running authserver - my HOST file was forcing the server to run on localhost - which I think was wrong. My fix was to clear my HOSTS file, run the server, (now shows it running on my external IP at 8085) then put 127.0.0.1 (DDNS) back into my HOST file so that I could connect. Hope that helps anyone w/ the same issue!

I updated the core and DB's with the commit above, but the same problem persists.

Info: Operating System -Win 64x TrinityCore Revision -2013-01-22 <4f3c6b139031> TrinityDatabase Version - 335.50_2013_01_14 DB servers running on my local machine. MySQL Server -5.5.29 Been wrestling with the "Realm loop" problem for a family member trying to connect from outside my LAN. I've followed the steps necessary to setup the server for external access by doing the following: -Setup a DDNS through DynDNS. I've tested it by pinging via CMD and it successfully returns my external IP - so I'm fairly confident it is setup correctly. -Forwarded ports 3724 and 8085. I've tested ports via both my external IP and my DDNS and they show as open. -Modified realmlist DB to point to my DDNS. (The data entry, I did not make the "default entry" mistake on HeidiSQL) -Modified realmlist.WTF to point to my DDNS. -Have my family member do the same to his realmlist.WTF Now I did encounter the Realm Loop issue on my own computer. After browsing the forums I understand that there sometimes is a loopback issue when trying to connect from the host machine, I fixed this by editing my "Hosts" file with "127.0.0.1 <DDNS.net>" and I can login just fine. A family member trying to get in, however, suffers from the Realm loopback. (He sees my Trinity server ---> Connecting...... ----> Back to realm selection). I have a creeping suspicion that my hosts file will play a role in whatever issue this is, but I'm not quite savvy enough to figure it out on my own. I've searched around for this issue, I know there's more than a few topics on it, but I cannot seem to fix it with any of the suggested methods. I've tried the following: -Reset router -Changed the worldserver port from 8085 to 8086 in the worldserver.conf, realmlist DB, and the forwarded ports in case the 8085 port was hosed up. Same issue, I can login fine with the different port - but outside connections cannot. -Disabled all firewalls (including routers) Any help would be greatly appreciated.