[DiscordArchive] Trying to get an azerothcore server running on a windows machine accessible remotely. Followed https
[DiscordArchive] Trying to get an azerothcore server running on a windows machine accessible remotely. Followed https
Original source
Trying to get an azerothcore server running on a windows machine accessible remotely. Followed https://www.azerothcore.org/wiki/networking, but it's not working.
So far we've:
1. gotten external IP from whatsmyIP, and applied it via heidisql to the address field of the id=1 record in the realmlist table of the acore_auth db.
2. forwarded ports 3724 and 8085 from the router to the PC running the authserver and worldserver
3. opened port 3724 and 8085 on the router's firewall
4. opened ports 3724 and 8085 on the windows computer's firewall.
But the remote user is still stuck at 'Connecting...' Local user, who CAN connect on 127.0.0.1, also cannot connect via the external IP
Any immediately obvious things we're forgetting here? Or any other applicable doco for this?
rektbyfaith
05-03-2023, 04:13 AM #1Archived author: exec • Posted: 2023-05-03T04:13:17.757000+00:00
Original source
Trying to get an azerothcore server running on a windows machine accessible remotely. Followed https://www.azerothcore.org/wiki/networking, but it's not working.
So far we've:
1. gotten external IP from whatsmyIP, and applied it via heidisql to the address field of the id=1 record in the realmlist table of the acore_auth db.
2. forwarded ports 3724 and 8085 from the router to the PC running the authserver and worldserver
3. opened port 3724 and 8085 on the router's firewall
4. opened ports 3724 and 8085 on the windows computer's firewall.
But the remote user is still stuck at 'Connecting...' Local user, who CAN connect on 127.0.0.1, also cannot connect via the external IP
Any immediately obvious things we're forgetting here? Or any other applicable doco for this?
Original source
based on my latest testing with it that all sounds correct. one cool trick is to set your realm's `address` to `whoami.akamai.net`. DNS requests for that A record return the requestor's IP, so no need to update that ever again.
If you have anyone connecting from inside the network, you'll also need to update your `localAddress` and `localMask` values. `localAddress` should be the internal IP of the world server, while `localMask` should indicate the size of the private network you'll be coming from.
I setup something very similar sounding to what you're describing using a Linux server and it works fine. You can always install Wireshark on the external client PC to sniff the traffic - the actual packets are clear-text and Wireshark even deciphers them for you. Was very helpful in troubleshooting.
rektbyfaith
05-03-2023, 04:24 AM #2Archived author: KJack • Posted: 2023-05-03T04:24:34.730000+00:00
Original source
based on my latest testing with it that all sounds correct. one cool trick is to set your realm's `address` to `whoami.akamai.net`. DNS requests for that A record return the requestor's IP, so no need to update that ever again.
If you have anyone connecting from inside the network, you'll also need to update your `localAddress` and `localMask` values. `localAddress` should be the internal IP of the world server, while `localMask` should indicate the size of the private network you'll be coming from.
I setup something very similar sounding to what you're describing using a Linux server and it works fine. You can always install Wireshark on the external client PC to sniff the traffic - the actual packets are clear-text and Wireshark even deciphers them for you. Was very helpful in troubleshooting.
Original source
the external client is just sending packets off and never gets a return
rektbyfaith
05-03-2023, 04:25 AM #3Archived author: exec • Posted: 2023-05-03T04:25:14.153000+00:00
Original source
the external client is just sending packets off and never gets a return
1 Guest(s)
1 Guest(s)