Open Home server hosting issue

[Troya]

I have a issue at hosting World of Warcraft 3.3.5 Public.

I'm testing sunwell core, and it is a bit old one.

I have 2 PC, 1. is my main machine, and 2. is server machine.
I have public IP and all ports are open. There is no issue to players log in-game, it is only problem from me to log in-game.

Due my IP change i use domain system to update ip and i do not need overwrite everytime new ip.

Let me better explaine.

Server Machine:

IP is : domain.com and in auth-realmlist-address is domain.com
All players can log in-game and have no issue. However on my main pc i put in wow realmlist eternal ip of server machine set realmlist 192.168.0.173
and i was able log-in with account but can't open realm to make character.

If i set domain.com in wow realmlist such as set realmlist domain.com it will not even able conect to account.

Here is how auth-realmlist look

Id, name, address, port, icon, flag, timezone, allowedSecurityLevel, population, gamebuild
1, test, domain.com , 8085 , 0, 0, 1, 0, 0, 12340

I belive the issue is what it is a older version of auth and it do not have ExternalLocation and mask and that reason don't giv me access form my main pc to log in-game.

Is the issue fixable or i will need recode realmlist.cpp in the source

Note this is home hosting, on new version of TC which have externalLocation, mask work fine public and local log in-game.

 

[Troya]

There is no more options.

It looks i will need recode realmlist.cpp

 

[treetree]

setup the local address of the internal machine in the auth realmlist db as internally routed exp: 192.168.0.173 and explain it to the hosts.ect
in windows.

C:\Windows\System32\drivers\etc
hosts.etc

127.0.0.1 localhost
localhost 192.168.0.173 ----- your internal address
127.0.0.1 ----external ip

try explaining it to the hosts.etc first it
routs all the traffic

no need to recode anything it is just a routing issue.

gl

 

[Troya]

Not working.
Here is the video.

WoW Issue.mp4

drive.google.com

 

[Noxbox]

This could be a NAT loopback issue,
where your router might not support or is not configured to handle requests from the inside network to its public IP and back inside correctly.

Using the internal IP address bypasses the need for NAT loopback, which is why you might have been partially successful in connecting this way.

Try editing your hosts file on your main PC to directly map domain.com to the server's internal IP address, thus being treated as a external connection but still avoiding the loopback