TallyPrime Slow on Multi-User LAN: Complete Network Fix Guide

A common frustration in medium-sized accounts offices is the slow execution of TallyPrime in multi-user setups. While TallyPrime runs fast on the server machine where the company data is locally hosted, client workstations connected via the Local Area Network (LAN) often experience lags. This results in screen freezing when opening ledgers, delays during voucher saves, and progress bars hanging during report exports.

This issue is rarely caused by the TallyPrime application itself. Instead, it typically stems from network bandwidth bottlenecks, misconfigured Windows firewall ports, active antivirus scans on the database directory, or network card configuration settings. This technical guide outlines the step-by-step diagnostic and configuration fixes to restore peak performance across your LAN environment.

1. Setting the Network Card Speed & Duplex

By default, Windows configures Network Interface Card (NIC) speeds to auto-negotiation. If there are minor fluctuations in network quality, the card may auto-downgrade to 10 Mbps or 100 Mbps Half-Duplex, causing transmission delays for TallyPrime's flat-file database queries.

To force Gigabit speeds on both the server and all client workstations:

1. Press Windows + R, type ncpa.cpl, and press Enter to open Network Connections.
2. Right-click your active network connection (Ethernet) and select Properties.
3. Click the Configure button near your network card model name.
4. Navigate to the Advanced tab.
5. Select Speed & Duplex (or Link Speed) from the Property list.
6. Change the value from Auto Negotiation to 1.0 Gbps Full Duplex. If 1 Gbps is missing, choose 100 Mbps Full Duplex. Never select Half Duplex.
7. Click OK. The network connection will drop for 2 seconds and reconnect at locked maximum speed.

2. Configuring Windows Defender Firewall and Port Exceptions

TallyPrime Server operates on port 9000 by default (or any port configured in your License Admin panel). If the Windows Firewall inspects every database packet sent over this port, TallyPrime will lag. You must add explicit inbound and outbound rule exceptions:

1. Open the Control Panel and navigate to System and Security > Windows Defender Firewall.
2. Click Advanced Settings in the left pane to open the security console.
3. Select Inbound Rules and click New Rule in the Actions pane.
4. Choose Port and click Next. Set the protocol to TCP.
5. Select Specific local ports and enter 9000 (or your custom Tally port). Click Next.
6. Select Allow the connection and click Next.
7. Apply the rule to Domain, Private, and Public profiles, name it "Tally Server Port", and save.
8. Repeat the process for Outbound Rules to allow bi-directional traffic on that port.

3. Excluding Tally Data Directories from Antivirus Scans

TallyPrime reads and writes to flat-file formats (e.g. `Company.900` database files). Antivirus programs (including Windows Defender) inspect these files during read/write cycles, causing database locks and lagging.

To configure exclusions:

1. Open your security software and navigate to the Exclusions / Exceptions settings.
2. Add an exclusion for the file extensions: .900, .tsf, and .xml.
3. Exclude the entire TallyPrime application directory (e.g. C:\Program Files\TallyPrime).
4. Exclude the Shared Company Data folder path on both the server and client machines (e.g. \\SERVER\TallyData).

4. Adjusting the tally.ini Configuration Settings

The tally.ini file located in your TallyPrime directory contains parameters that govern network memory allocation. Modifying these settings can optimize performance:

1. Navigate to the TallyPrime application folder and open tally.ini using Notepad.
2. Locate the line [TallyPrime] or the general parameters section.
3. Verify or add the following network performance parameters:
   • TallyServerMode = Yes (For the server machine).
   • ForceNoOSBuffering = Yes (Prevents Windows from caching incomplete database states).
   • TCPAcceptThreads = 10 (Increases concurrent thread allocations for network clients).
4. Save the file and restart TallyPrime.

5. Disabling IPv6 Conflicts

Many local routers resolve names using IPv6, which can lead to connection delays if your Tally client uses IPv4. Disabling IPv6 on your LAN network cards can resolve name-resolution lag:

• Open Network Connections via ncpa.cpl.
• Right-click your network card and select Properties.
• Uncheck the box next to Internet Protocol Version 6 (TCP/IPv6).
• Click OK and restart the system.

6. LAN Performance Checklist

7. Operating System Registry Tweaks for Tally

For network setups experiencing persistent delays during file-locking operations, editing SMB parameters in the Windows registry of the Tally server can resolve transaction queues:

• Disable SMB OpLocks: Opportunistic locking (OpLocks) allows clients to cache file portions locally. In TallyPrime setups, this can lead to database conflicts. To disable OpLocks, navigate to HKLM\System\CurrentControlSet\Services\LanmanServer\Parameters and set the registry value OplocksDisabled to 1.
• Adjust Connection Timeout: Reduce network handshake timeouts to avoid hanging connections. Navigate to HKLM\System\CurrentControlSet\Services\LanmanWorkstation\Parameters and set KeepConn value to 600 seconds.

8. Network Switch Quality & Backbone Speed

Many SME offices daisy-chain cheap, unmanaged 5-port network switches together. TallyPrime database reads require high packet delivery rates:

• Ensure all local switches are **Gigabit Switch** hardware supporting a non-blocking backplane bandwidth capacity.
• Avoid using USB-to-Ethernet adapters on client workstations. These adapters use CPU cycles for packet processing, introducing micro-lags.
• Keep Ethernet cables away from high-voltage electrical lines inside wall cavities to prevent electromagnetic interference from causing packet dropouts.

9. Impact of Router and Switch Overloads on Tally Database

High volume offices with multiple client workstations editing database records simultaneously place a heavy load on local network switches. Using non-gigabit switches throttles packet throughput, causing write operations to queue. This lag triggers TallyPrime to freeze or display data response errors. Upgrading switch hardware to managed gigabit switches is the most effective way to eliminate multi-user slowness.

10. Additional Router Settings to Verify

Some modern routers have built-in security scans or Quality of Service (QoS) rule allocations that dynamically limit bandwidth. Ensure that you add your Tally server IP to the QoS high-priority list. This ensures that licensing and database transactions receive unthrottled bandwidth priority across the LAN switch channels.