Venue network

In a Lucky Touch venue, you enter no address, not on a device, not on a register, not on the router. The server, the devices and the registers find each other on their own, as long as they are on the same local network.

How everything finds everything

The device asks the router for an address (DHCP), then calls the server on the local network; the server tells it where to reach it. The device remembers what it found and starts again as soon as the server stops answering. If the server’s address changes, it finds it again on its own in about thirty seconds.
The register does the same with the Trouver le serveur de la salle (Find the venue server) button on its sign-in screen. The Serveur de la salle (Venue server) field is only a fallback.
The router only has to hand out addresses (DHCP) and, for the platform, let the venue PC go out to the Internet. No port forwarding, nothing opened to the outside.

What the network needs

	Why
A single local network for the venue PC, the devices and the registers	Discovery does not cross an intermediate router or a VPN.
A DHCP server (the router)	Devices get their address on their own. Without DHCP, a device gives itself a fallback address after 10 s, but it may not be in the right range.
A DHCP reservation for the venue PC (recommended)	A stable address avoids the short interruption when the PC changes address.
A single Lucky Touch server on this network	A new device takes the first server that answers.

In the back office, Exploitation (Operations) → Boîtiers (Devices) shows, for each device, its addressing (DHCP or statique (static)) and its hardware address (for a possible reservation in the router).

The Réseau (Network) screen, read-only, shows Ce que le serveur annonce (What the server announces) to the devices and the number of devices En DHCP (On DHCP), Statique (repli) (Static (fallback)) and Inconnus (Unknown), with the list.

What breaks discovery

Situation	What you see	What to do
The router redirects some connections to another server (a setting left by an old system)	Device: `SERVEUR REFUSE`, serious alarm; the register cannot reach the server	Have this redirection removed from the router, or limited to the old equipment. See below.
Wi-Fi client isolation (“guest” Wi-Fi)	The register on a tablet: “Aucun serveur trouvé sur ce réseau” (No server found on this network)	Put the tablets on a Wi-Fi without isolation; as a fallback, enter the back office address in Serveur de la salle (Venue server).
Two servers on the network (test PC, old server)	A new device connects to the wrong one	Switch off or disconnect the one that is not the venue’s.
Different subnet (device stuck on its fallback address, venue moved to another range without DHCP)	Device: `CHERCHE SERVEUR` over and over	Restore a DHCP server: the device recovers on its own.
Cable or switch	Device: `PAS DE RESEAU` or `ATTENTE ADRESSE`	Change the cable or the port, check the DHCP.
Router replaced	Interruption of about one minute	Nothing: the devices get a new address and find the server again on their own.

An old system in the venue?

This is the trap that takes longest to find. A router configured for another system can divert the devices’ connections to its old server, whatever address they are aiming for. The device shows SERVEUR REFUSE and the venue server receives nothing.

Look at the device’s screen: SERVEUR REFUSE = another server answered in its place. Do not look elsewhere.
Never draw conclusions from another device in the venue (an old device, a PC): it may be diverted too and “believe” it is reaching your server.
Have the router’s redirection rules checked by the person who administers it, and exempt the Lucky Touch devices and registers (or limit the rules to the old equipment only).

To go further, the device trace shows the address that refused it: see Diagnostics, and send it to the publisher with a description of the router.