Trouble getting access to server on another computer in the same network

[andyplaysgames]

Hello, I'll try to keep this as simple as possible:
I have 1 desktop (server, hard lined), one laptop (same network, wifi).
Maybe I just need to have it worded for me a different way than the guide. I am having trouble getting my laptop to log into the game properly.
Right now my laptop sees the server enough to open the game and create a character but I get hung up when the game tries to zone me in.
Seems like I would then have the Windower profile correct on my laptop to get that far.
My hunch:
I need to assign my zone IPs to my server's IPv4 address. But when I go into HeidiSQL and change them all to the correct IPv4 IP it still doesn't work.... HOWEVER
I also do not see the 2 characters I created (and still exist and playable on server computer) in the chars table in HeidiSQL. It's just blank.

TLDR:
I guess I need to figure out how to change the zone IPs in my DB correctly. HeidiSQL must not be seeing the correct DB. Is there a way to edit the LSB DB in Heidi? Or do I have to use something else for that?
<<< Amateur at this

[CageTV]

Open powershell to your c:\server\toolsfolder\ Then type the comman "py -3 dbtool.py" without the quotations and select maintenance option "T" Set external IP (IP OF YOUR SERVER) and then you will be fine.

…

On Sat, Mar 25, 2023, 7:43 PM andyplaysgames ***@***.***> wrote: Hello, I'll try to keep this as simple as possible: I have 1 desktop (server, hard lined), one laptop (same network, wifi). Maybe I just need to have it worded for me a different way than the guide. I am having trouble getting my laptop to log into the game properly. Right now my laptop sees the server enough to open the game and create a character but I get hung up when the game tries to zone me in. Seems like I would then have the Windower profile correct on my laptop to get that far. My hunch: I need to assign my zone IPs to my server's IPv4 address. But when I go into HeidiSQL and change them all to the correct IPv4 IP it still doesn't work.... HOWEVER I also do not see the 2 characters I created (and still exist and playable on server computer) in the chars table in HeidiSQL. It's just blank. TLDR: I guess I need to figure out how to change the zone IPs in my DB correctly. HeidiSQL must not be seeing the correct DB. Is there a way to edit the LSB DB in Heidi? Or do I have to use something else for that? <<< Amateur at this — Reply to this email directly, view it on GitHub <#3695>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQZOSMLYNGVVMDZUT4QOC33W557LBANCNFSM6AAAAAAWHZ7XEI> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[andyplaysgames]

So just to be clear on the IP question: the IPv4 address should be the zone-IP in the DB AND the "--server ip" for both my server computer client and the non server computer client?
And put in the --hairpin for both?
One is in the office and one is in the bedroom I'd like to use them interchangably.

[andyplaysgames]

If it helps:
The only way I can seem to get it to work right now at all (on the server PC) is if I let python auto detect the public facing IP (it is the IPv6 address but not quite identical) and change all the zone IDs to that.
Even then i'm still pointing my windower profile to '127.0.0.1' and it works.

Reminder I might need this dumbed down for me a bit. Not to a child's level, because I did get this far.

[TeoTwawki]

(it is the IPv6 address but not quite identical) and change all the zone IDs to that.

Just a warning: we literally never wrote any code that supports anything except IPv4 so anything else in that sql field is being resolved by something not even in our server executable and working for you by shear luck, and bound to eventually randomly stop working without us having any clue why.

And put in the --hairpin for both?

hairpin for any client connecting from within your ow lan. it kind of provides an "override" for the external IP so the client can find the server. Anyone connecting from the internet, should not use it. 127.0.0.1 is correct for a client connecting from the server machine to itself.

[andyplaysgames]

UPDATE:
So I changed my Windower profile on my server PC to look for 127.0.0.1.
My zone IPs are still set to what Python DB tool auto detected as my public-facing IP (which is the one very similar but not identical to what Windows Network and Internet properties show as my IPv6)
Server PC connects and logs in to zone correctly and I can play.
HOWEVER
Taking note of Teo's heads up about the IPv6 maybe not working at some point I decided to change the zone IPs to my IPv4 address.
I did this by using the Python DB tool but instead of accepting the auto detected, public-facing IP I chose NO and put in my own. (IPv4 copy and pasted from windows Network properties window).
I did not change the windower profile so it is still looking for 127.0.0.1
It connects to server and I can select my character but then cannot zone in.

Starting to pull my hair out.

[andyplaysgames]

FURTHER UPDATE (and hunch)
I port forwarded one port 54230 and then the network went down (for a restart) and people in the house got mad at me so I stopped.
Is that why I can only get to the lobby on my laptop and not zone in?

[Aeisu]

so your server is projecting to your ipv4 so anyone on the outside can connect.
since you are on a routed network and not directly connected to the modem you need to port forward more.
TCP 54230,54321,54001,54002
UDP 54230

[andyplaysgames]

So I was able to port forward all those ports. My router app on my phone gave me to option to do external and internal so I did both.
And right now it is still not working. Should I have done only external?

[Aeisu]

did you change any of the settings in settings/network.lua? aside from the sql password and database name

[andyplaysgames]

I don't believe I did, but here is what i have:

---

-- NETWORK SETTINGS

-- All settings are attached to the xi.settings object. This is published globally, and be accessed from C++ and any script.

-- This file is concerned mainly with networking between the database, client, and server executables.

xi = xi or {}
xi.settings = xi.settings or {}

xi.settings.network =
{
SQL_HOST = "127.0.0.1",
SQL_PORT = 3306,
SQL_LOGIN = "root",
SQL_PASSWORD = "MYPASSWORD",
SQL_DATABASE = "xidb",

LOGIN_DATA_IP   = "0.0.0.0",
LOGIN_DATA_PORT = 54230,
LOGIN_VIEW_IP   = "0.0.0.0",
LOGIN_VIEW_PORT = 54001,
LOGIN_AUTH_IP   = "0.0.0.0",
LOGIN_AUTH_PORT = 54231,
LOGIN_CONF_IP   = "0.0.0.0",
LOGIN_CONF_PORT = 51220,

MAP_PORT = 54230,

SEARCH_PORT = 54002,

ENABLE_HTTP = false,
HTTP_HOST   = "localhost",
HTTP_PORT   = 8088,

-- Central message server settings (ensure these are the same on both all map servers and the central (lobby) server
ZMQ_IP   = "127.0.0.1",
ZMQ_PORT = 54003,

-- ===========================
-- NOTE: The settings that follow will not necessarily need to be modified
--       in any way for the server to work out of the box.  This should only
--       be modified by those who understand networking.  Modifying these
--       values could potentially make it so that you can not log in to your
--       server.
-- ===========================

-- ===========================
-- UDP Sockets Configuration
-- ===========================

-- Display debug reports (When something goes wrong during the report, the report is saved.)
UDP_DEBUG = false,

-- ===========================
-- TCP Sockets Configuration
-- ===========================

-- Display debug reports (When something goes wrong during the report, the report is saved.)
TCP_DEBUG = false,

-- How long can a socket stall before closing the connection (in seconds)
TCP_STALL_TIME = 60,

-- ===========================
-- IP Rules Settings
-- ===========================

-- If IP's are checked when connecting. This also enables DDoS protection.
TCP_ENABLE_IP_RULES = true,

-- Order of the checks
--   deny,allow     : Checks deny rules, then allow rules. Allows if no rules match.
--   allow,deny     : Checks allow rules, then deny rules. Allows if no rules match.
--   mutual-failure : Allows only if an allow rule matches and no deny rules match.
-- (default is deny,allow)
TCP_ORDER = "deny,allow",
--TCP_ORDER = "allow,deny",
--TCP_ORDER = "mutual-failure",

-- ===========================
-- IP rules
-- ===========================
--   allow : Accepts connections from the ip range (even if flagged as DDoS)
--   deny  : Rejects connections from the ip range
-- The rules are processed in order, the first matching rule of each list
-- (allow and deny) is used

TCP_ALLOW = "",
--TCP_ALLOW = "127.0.0.1,192.168.0.0/16",
--TCP_ALLOW = "127.0.0.1"
--TCP_ALLOW = "192.168.0.0/16"
--TCP_ALLOW = "10.0.0.0/255.0.0.0"
--TCP_ALLOW = "all"

TCP_DENY = "",
--TCP_DENY = "10.0.0.0/8,192.168.0.0/16",
--TCP_DENY = "127.0.0.1",
--TCP_DENY = "10.0.0.0/255.0.0.0",

-- ===========================
-- Connection Limit Settings
-- ===========================

-- If connect_count connection request are made within connect_interval
-- msec, it blocks it

-- Consecutive attempts interval (msec)
-- (default is 3000 msecs, 3 seconds)
TCP_CONNECT_INTERVAL = 3000,

-- Consecutive attempts trigger
-- (default is 10 attempts)
TCP_CONNECT_COUNT = 10,

-- The time interval after which the connection lockout is lifted. (msec)
-- After this amount of time, the connection restrictions are lifted.
-- (default is 600000 msecs, 10 minutes)
TCP_CONNECT_LOCKOUT = 600000

}

-- EOF

[Aeisu]

that's good then
btw the line of code you want for heidi is
UPDATE zone_settings SET zoneip = '127.0.0.1'; (replace the 127.0.0.1 with whatever IP you want) I just keep this saved and run it when i need to change things.

[Aeisu]

are you using any addons or plugins with windower that might cause a problem at the start cutscene like a a fps uncap?
or is there a firewall on the server pc preventing connections?

I had to disable any and all firewalls on my home network and the server computer just to be on the safe side so no connections get turned away fromthe server.

[andyplaysgames]

Laptop client side looks like:
< args>--server 192.168.1.89 --hairpin < /args>
This is will immediately close the connect window.
If I take out the --hairpin I can get to the lobby but won't zone in.

Server side looks like: (And works)
< args>--server 127.0.0.1 < /args>

All of this is while I have my IPv6 set as my zone IPs. That is what python auto-detects as the public facing IP.
Neither server client or laptop client will connect if I set zone IPs to IPv4

[andyplaysgames]

Right now I have Windows Firewalls:
Domain Network, Private Network and Public Network all ON

[TeoTwawki]

Laptop client side looks like: < args>--server 192.168.1.89 --hairpin < /args> This is will immediately close the connect window. If I take out the --hairpin I can get to the lobby but won't zone in.

Server side looks like: (And works) < args>--server 127.0.0.1 < /args>

All of this is while I have my IPv6 set as my zone IPs. That is what python auto-detects as the public facing IP. Neither server client or laptop client will connect if I set zone IPs to IPv4

thats internal addressing, you need external for ppl outside your network

[TeoTwawki]

stop trusting your python detection and look up your external ip v4 manually

[Aeisu]

Laptop client side looks like: < args>--server 192.168.1.89 --hairpin < /args> This is will immediately close the connect window. If I take out the --hairpin I can get to the lobby but won't zone in.

Server side looks like: (And works) < args>--server 127.0.0.1 < /args>

All of this is while I have my IPv6 set as my zone IPs. That is what python auto-detects as the public facing IP. Neither server client or laptop client will connect if I set zone IPs to IPv4

192.168.1.89 is a network IP which your server isn't projecting too the ZoneIP needs to be your IPv4
https://whatismyipaddress.com/ will tell you what it is

Note: be sure it gets your physical address correct or you have bigger issues. Eg. Starlink ISP uses CGNAT which has a single IP for multiple users and making it not forward facing, you can't get past this with any ease at all, I know this since i had starlink and did alot of digging on the subject.

I would also shut off all firewalls on the server for windows to be sure you know the connection is getting through. I have all mine turned off and it works great.

[andyplaysgames]

I changed my zone IPs to my external IP address, and changed my laptop windower setting to point to that IP address and not I can't even find the server.
Firewall?

[andyplaysgames]

OK SO........
I changed my zone IPs to my internal IPv4 (192.)
And my laptop windower is set to point to it. (no hairpin)
And I am now logged in on my laptop! SUCCESS
Also I had to change my server PC client to IPv4 (192.xx) and that works too. And at the same time as my laptop.
So all working right now.
It must have been the Firewall on server (I also turned off laptop firewall).

SO thanks you for the help!

[andyplaysgames]

And yes, github is giving me to business as well. I can't seem to delete that duplicate message below ><

[andyplaysgames]

I don't suppose you might know why my controller on my laptop is working for horizon server (with Ashita 4) but not on my newly working personal server?

[andyplaysgames]

It works to config the controller but not when in game.

[andyplaysgames]

Nevermind, I guess i config'd the wrong of the 3 config programs. I just did all 3 just in case.

[andyplaysgames]

Thank you everyone for the help!