Make every KalOnline configuration value agree

Build one configuration sheet

Create a simple table before editing files. List each server process, its configuration file, database or DSN, bind address, destination address, listening port and log path. This turns a folder full of cryptic files into one system map.

Edit safely

• Copy the original file before every change.
• Change one class of value at a time.
• Preserve encoding and line endings where possible.
• Do not replace every occurrence of 127.0.0.1 blindly; some values are intentionally local.
• Do not publish database credentials in screenshots or forum posts.

Understand address roles

A bind address tells a service which local interface to listen on. A destination address tells one component where another component lives. A public address is what remote clients may use through NAT. These are not automatically interchangeable.

For the first test, keep everything on one VM and use the package’s local convention. For the second test, move only the client to another LAN machine and update the client-facing address. Public access comes last.

Verify after every change

Restart only the affected process, then read its newest log lines. Confirm the listening socket with Windows networking tools. If the process fails earlier than before, restore the previous file instead of stacking more edits.

A practical configuration review

Search all files before changing an address

Use a text-search tool on a copy of the package to find old IP addresses, instance names, DSNs and database names. Review each match in context. Some packed or encrypted configuration will not appear in plain-text search and may require the package’s legitimate configuration utility.

Separate server-internal and client-facing values

The authentication service may talk to a database service on localhost while the client needs the server’s LAN address. Replacing both with a public IP can break internal communication and expose services unnecessarily.

Validate ports by observation

After a process starts, verify which local address and port it is listening on. This is stronger evidence than a forum list. Custom packages frequently change defaults, and a port written in one config may be disabled or superseded elsewhere.

Keep a change ledger

For every edit, record the filename, original value, new value, reason and result. If a later step fails, the ledger shows which change introduced it and makes rollback precise.