Why does Tally show a network error or company not found?
Short answer: Tally Prime and Tally.ERP 9 use a server-client model for multi-user operation: one machine runs Tally as a Gateway of Tally server (the host), and other machines connect to it as clients. Network errors occur when: the Tally server process (Gateway of Tally) is not running on the host machine, Windows Firewall is blocking Tally's network communication after a Windows Update, the host machine's IP address or hostname has changed, or the Tally licence server (TSS — Tally Software Services) cannot be reached for activation. This is a configuration and network diagnosis problem, not a hardware problem.
How to fix — step by step
Step 1 — Verify Gateway of Tally is running on the server
On the machine that hosts the Tally company data: open Tally Prime (not from a client machine). In the startup screen, you should see "Gateway of Tally" mode active — it usually shows "License valid" and a green indicator. If Tally opened in normal client mode, go to Help → Settings → Connectivity → Enable Gateway of Tally. If the Gateway is running but clients still cannot connect, check that the server machine's firewall allows Tally. Also: the server machine must not be in sleep or hibernate mode — Tally's Gateway stops responding when Windows enters sleep, and clients see a network error even though the server is technically on. Disable sleep mode on the server machine: Settings → Power & Sleep → set both to Never.
Step 2 — Add Tally firewall exceptions in Windows
Windows Firewall regularly re-evaluates application permissions after Windows Updates and network profile changes. Tally.exe firewall exceptions are commonly removed. On both the server and client machines, open Windows Defender Firewall → Allow an app through Windows Firewall → Change Settings → Allow another app. Browse to the Tally installation folder (usually C:\Program Files\Tally\ or C:\Tally Prime\) and add Tally.exe for both Private and Public networks. Also add TallyVault.exe if it exists. Repeat this on both server and client machines. Always test the connection from the client after adding exceptions and before testing again. See our antivirus exclusion guide for related firewall scenarios.
Step 3 — Fix hostname resolution on the LAN
In Tally's network configuration (on the client machine), the server is identified by hostname (the computer's name on the network) or IP address. If the server's hostname cannot be resolved by the client (a DNS or WINS issue on the LAN), Tally shows "company not found". Diagnose: open Command Prompt on the client and run ping [server-hostname]. If ping fails, hostname resolution is broken. Fix options: (1) Use the server's IP address instead of hostname in Tally's network settings — go to Gateway Configuration and change the server field from the hostname to the IP address (find the server IP by running ipconfig on the server machine). (2) Add the server's hostname and IP to the client's C:\Windows\System32\drivers\etc\hosts file. Note: if the server's IP address changes (DHCP reassignment), option 1 breaks again — assign a static IP to the server for permanent stability.
Step 4 — The India angle: shared computers and power cuts
In Indian SMEs, the Tally server is often the owner's personal laptop that also runs other tasks — email, browsing, Zoom calls. After a meeting ends and Windows goes to sleep, Gateway of Tally goes offline and all connected accounting staff see network errors for the rest of the day. This is the most common Tally network complaint we hear from small businesses. The fix: either dedicate a specific machine as the Tally server and set it to never sleep, or use Tally Prime's cloud (TallyNet) to host data online so it does not depend on local network availability. Also, frequent power cuts to the server machine cause the Tally data directory to lock — if the company file is locked after a power cut, run Tally's built-in data splitter and rewriter tool from the Gateway settings to clear the lock. See our Outlook PST corruption guide for related power-cut data corruption patterns.
When to call a laptop repair service
When DIY ends
Call a technician if: the Tally data directory shows corruption or the company file cannot be opened even from the server machine locally (not a network error — a data file error); Tally's built-in rewrite tool reports errors it cannot fix; or the Tally licence (TSS) is expired and requires renewal with Tally's support team.
Typical repair cost in India
Network configuration fix (firewall rules, hostname resolution, static IP): ₹500–₹1,500. Tally data corruption repair using Tally tools: ₹1,000–₹3,000 depending on severity. Data recovery from a failed drive where Tally data is stored: ₹2,000–₹10,000.
A note from the LRW Engineer Team
The single most impactful action for preventing Tally network errors in Indian offices: assign a static private IP address to the Tally server machine. Dynamic IP assignment means the server's IP changes periodically, and every Tally client needs to be reconfigured. A static IP (e.g., 192.168.1.50) stays fixed and eliminates the majority of recurring connection issues. Set it in the server's Network Adapter settings under TCP/IPv4 Properties.