Network & Multi-User Errors

Why multi-user setups break

Multi-user accounting setups depend on several things staying in sync at once: one machine correctly configured as the file host, every other machine pointing to the correct network path, a firewall that allows the software's specific ports through, and a network that doesn't silently drop long-idle connections. When any one of those pieces shifts — a router reset, a workstation reassigned as the host, a Windows update resetting firewall rules — the whole setup can stop working with a vague, unhelpful error message.

Common symptoms

• A teammate receives a "file is in use" message even though no one else has it open
• The software can't find the company file over the network despite the correct folder path
• A generic network or "H202"-style connection error appears when multiple users try to connect
• One workstation can access the file while others time out
• Performance is fine for one user but crawls to a stop as more users connect

Step-by-step resolution sequence

Step 1 — Confirm which machine is the actual host

Multi-user accounting setups require exactly one machine to act as the file host, running the background database service. Confirm this service is running only on the intended host machine and not accidentally left running on a former host.

Step 2 — Restart the hosting service in the correct order

Stop the network/database service on the host machine, restart the host computer, restart the hosting service, and only then have other workstations attempt to reconnect. Connecting in the wrong order is a common source of persistent lock errors.

Step 3 — Verify the shared folder path is identical across machines

Confirm every workstation is pointing to the exact same network path (not a locally mapped drive letter that differs machine to machine) to reach the company file.

Step 4 — Check firewall rules on the host machine

Accounting software typically requires specific ports to be open for multi-user access. Confirm your firewall (including any recently updated Windows security settings) allows the software's process and ports through, on both the host and connecting machines.

Step 5 — Clear stale lock files

Some accounting programs create a temporary lock file while a company file is open. If a previous session ended abnormally (a crash or forced shutdown), this lock file can persist and falsely report the file as "in use." Look for a lock file with a name matching your company file and remove it only after confirming no one currently has the file open.

Step 6 — Rule out router or switch interference

Some consumer-grade routers apply aggressive idle-connection timeouts that interrupt long multi-user sessions. If disconnections happen consistently after a fixed period of inactivity, this is a strong signal to check router-level settings.

Step 7 — Test with a reduced user count

If performance (not access) is the issue, test with only two users connected to see whether the slowdown scales with user count — this helps determine whether the bottleneck is network bandwidth, host machine hardware, or the software configuration itself.

Preventing future network issues

Document which machine is your designated host, keep firewall exception rules written down so they can be quickly restored after a security update, and avoid changing router settings during business hours when multiple users are actively working in the shared file.