Several registers in one outlet (local network) — Paloma365 Classic (Windows POS)

This article is about Paloma365 Classic, the POS application for Windows: how several registers work together in one outlet, what to do about "server not found" / "no database connection" errors, and which data the registers share.

Overview: how multiple registers work

When an outlet has several POS computers, they follow a "main computer + workstations" scheme:

• The main computer hosts the outlet database (a MySQL/MariaDB server installed together with the POS). It is usually the most reliable computer, switched on first and off last.
• The other registers do not keep their own database — they connect to the main computer's database over the local network (cable or the same router's Wi-Fi).
• Cloud sync covers the outlet as a whole — sales from every register reach the dashboard.

Hence the main rule: while the main computer is off or unreachable over the network, the other registers cannot work — they have nowhere to take data from.

Which data is shared

Since all registers of the outlet work with one database, the following is shared:

• menu, products, prices and stock;
• open orders and tables — an order opened on one register is visible on the others;
• shifts and cash operations;
• customers and discounts.

Only the POS local settings stay per-computer: printers, hardware, appearance, hotkeys.

Connecting an additional register

1. On the main computer: POS settings → Account settings tab → the network access block → «Create network credential» button. The POS creates network access to the database, shows the computer's IP address, and tries to open the required Windows firewall port itself. If it cannot (administrator rights are needed), it asks you to open the port manually — without this, other workstations will not connect.
2. On the additional register, when connecting to the database, tick «Network credentials». A server search button appears: the POS scans the local network and finds the main computer with your outlet's database by itself.
3. In the search window pick the found server (the POS marks it as "our server"; foreign databases are marked as another outlet or another account) and confirm — the POS connects and loads the data.

Connect additional registers together with Paloma365 support.

Server auto-discovery: when the main computer's address changed

The main computer's network address can change (for example, after a router restart). The POS handles this itself:

• On startup, if the database at the old address is unreachable, the POS automatically scans the network (a "scanning the network, please wait" indicator is shown) and, having found your outlet's database at a new address, reports that the database server was found at a new address and connects.
• The same auto-discovery also runs during work when the database connection is lost.
• If nothing is found, the POS shows a message that no servers were found and asks to check that the main computer is on and the network is available.

To keep the address stable, ask your network specialist to pin a permanent (static) IP address to the main computer in the router.

Common problems

"Lost connection to the database" / "No database connection"

The POS lost the main computer. The message asks to check the network connection to the computer where the database is installed ("Yes" — reconnect, "No" — close the program). Check in order:

1. Is the main computer on? If it is off, asleep or rebooting — switch it on, wait for it to fully boot, then press "Yes" (reconnect) on the register.
2. Does the network work? Check the cable or Wi-Fi on both machines: the Windows network icon, connection to the same router. Restart the router if in doubt.
3. Firewall. If registers stopped connecting after a Windows or antivirus reinstall on the main computer, the firewall has probably blocked database access. Press «Create network credential» on the main computer again (the POS re-opens the port) or message us here — a specialist will join.
4. The address changed. Let the POS run auto-discovery (see above) — it finds the database at the new address by itself.

If all steps check out and there is still no connection — message us here — a specialist will join.

"No servers found"

Auto-discovery scanned the network and did not find the outlet database. Either the main computer is off, or the registers are on different networks (e.g., one on cable, another on guest Wi-Fi), or the main computer's firewall blocks access. Check points 1–3 above and repeat the search.

One register works, the others don't

The working one is usually the register on the main computer (its database is local). So the problem is the network or firewall between the computers — check points 2–3 above.

No register works, including the main one

The problem is on the main computer: it is off, did not boot, or its database did not start. Reboot the main computer; if that does not help — message us here — a specialist will join.

FAQ

Which registers' sales reach the dashboard?

All of them: the registers share one database, and the outlet is synced to the cloud as a whole. More on cloud sync: Sync problems and fixes.

Can an additional register sell without internet?

Yes — the internet is needed for cloud sync, while inside the outlet the registers talk over the local network. But if the main computer is unreachable, additional registers cannot work.

An order was opened on one register — can it be closed on another?

Yes. Open orders live in the shared database and are visible on every register of the outlet.

Which computer should be the main one?

The most reliable one that is always on during working hours. Remember: switching off the main computer stops all other registers. Have a static IP address pinned to it in the router.

Wi-Fi or cable?

Cable is more reliable for the main computer and the registers: Wi-Fi drops are a frequent cause of "no database connection" errors.