Multi-Device Setup
Run VetLoop across every computer in your practice — reception desk, consulting room, treatment area — all sharing one live dataset.
How It Works
VetLoop uses a server–client architecture over your local Wi-Fi or wired network. One PC acts as the Server and hosts the shared database. All other devices are Clients that connect to the server over the local network.
Data syncs in real time using HTTP over your internal network. No cloud service is required — everything stays on your premises.
Your VetLoop licence plan determines how many simultaneous client devices are allowed. The Clinic plan allows up to 5 devices; the Hospital plan is unlimited.
Setting Up the Server PC
The server PC should be a machine that stays on during practice hours — typically the reception or front-desk computer.
- Install VetLoop normallyFollow the Getting Started install steps. Activate your licence.
- Open Settings → Storage ModeIn VetLoop, go to Settings → Storage → Storage Mode and select Network Server.
- Note the server IP address and portVetLoop shows your local IP (e.g.
192.168.1.10) and the port it listens on (default4040). Write these down — client devices will need them. - Leave VetLoop runningThe server must be running for client devices to connect. VetLoop can run minimised in the background.
Connecting Client Devices
- Install VetLoop on the client PCThe same installer is used for all devices. Client devices do not need a separate licence key — they connect via the server's licence.
- Open Settings → Storage Mode on the clientSelect Network Client.
- Enter the server addressType the server's IP address and port, e.g.
192.168.1.10:4040. Tap Connect. - Log inUse your normal VetLoop username and password. The client fetches your practice data from the server.
Client devices cannot operate independently if the server is turned off. Ensure the server PC is always on during business hours, or use Windows Task Scheduler to start VetLoop automatically at login.
Firewall & Network Requirements
For client devices to reach the server, port 4040 (TCP) must be open in Windows Firewall on the server PC.
VetLoop attempts to add this rule automatically. If clients cannot connect, run this command on the server PC as Administrator:
netsh advfirewall firewall add rule name="VetLoop Server" dir=in action=allow protocol=TCP localport=4040
All devices must be on the same local network (same Wi-Fi router or wired switch). VetLoop does not work over the internet without a VPN.
Storage Mode Summary
| Mode | Use case | Works offline? |
|---|---|---|
| Local Only | Single PC — no network sharing | Yes |
| Network Server | The PC that hosts data for other devices | Yes (serves others) |
| Network Client | Any additional PC in the same practice | No — requires server |
Troubleshooting Sync
Clients show "Cannot connect to server"
- Confirm the server PC is on and VetLoop is running.
- Verify the IP address and port are correct.
- Run the firewall command above on the server PC.
- Check that both PCs are on the same Wi-Fi network (not guest vs main).
Data not updating on clients
- VetLoop syncs via Server-Sent Events (SSE). If changes aren't appearing, try Settings → Storage → Reconnect on the client.
- A slow or congested network can cause delays. Wired connections are more reliable than Wi-Fi for the server PC.
Server IP keeps changing
Assign a static IP address to the server PC in your router's DHCP settings. Look for a "DHCP Reservation" or "Static Lease" option and pin the server's MAC address to a fixed IP.