Tally Slow or Not Responding Due to Network Card Not Negotiating Gigabit Speed (10/100 Mbps Issue)
In multi-user Tally Prime / Tally ERP environments where both Tally License and Data reside on a central server, network performance plays a critical role. A...
In multi-user Tally Prime / Tally ERP environments where both Tally License and Data reside on a central server, network performance plays a critical role. A very common yet often overlooked issue is when a Gigabit Ethernet network card operates only at 10 Mbps or 100 Mbps instead of 1 Gbps.
This Knowledge Base article explains why this happens, how it impacts Tally performance, and provides step-by-step technical remediation suitable for Windows Server–based Tally installations.
Technical Explanation
How Tally Uses the Network
Tally is a file-based accounting application. In a multi-user setup:
-
Client systems continuously read/write small data blocks
-
Data locking, voucher saving, and report generation depend on low latency + high bandwidth
-
Even small network delays cause freezes or “Not Responding” states
What Happens When Network Runs at 100 Mbps
Although the network adapter may be labeled Gigabit, Windows only shows speeds supported by:
-
Network card
-
LAN cable
-
Switch port
-
Intermediate wiring
If any component does not support Gigabit, the link falls back to 100 Mbps.
Resulting impact:
-
Sluggish voucher save
-
Delay while switching reports
-
Random Tally hangs for multiple users
-
Very low Ethernet activity despite active users
Use Cases Where This Issue Commonly Occurs
-
Tally Server upgraded, but old LAN cable reused
-
Server connected to legacy 10/100 switch
-
Damaged or partially wired RJ45 cable
-
Patch panel or wall socket not fully wired (4-wire instead of 8-wire)
-
Energy Efficient Ethernet / power-saving features enabled
-
NIC driver auto-negotiation failing due to physical layer issue
Step-by-Step Solution / Implementation
Step 1: Verify Current Network Speed
On the Tally server:
ncpa.cpl
→ Right-click Ethernet
→ Status
Check:
-
Speed: 1.0 Gbps → Correct
-
Speed: 100 Mbps → Problem confirmed
Step 2: Keep Speed & Duplex on Auto Negotiation
⚠ Never force 1 Gbps manually if it is not shown.
Step 3: Replace LAN Cable (Most Effective Fix)
-
Use Cat6 (preferred) or Cat5e
-
Avoid hand-crimped cables
-
Replace cable end-to-end
After replacement:
-
Disable/Enable adapter or reboot server
-
Recheck Ethernet Status
Step 4: Verify Switch Capability
Ensure the connected switch:
-
Supports 10/100/1000 Mbps
-
Is not a legacy Fast Ethernet (10/100) switch
-
Port LED indicates Gigabit (refer to switch manual)
If unsure:
-
Move server cable to another known Gigabit port
Step 5: Disable NIC Power Saving
Reboot the server.
Step 6: Disable Energy Efficient Ethernet (Recommended)
Step 7: Update Network Driver (If Required)
-
Download NIC driver from server OEM website (Dell / HP / Lenovo)
-
Avoid generic driver updates
-
Reboot after update
Commands & Examples
Check Network Configuration
Monitor Network Throughput
Check Power Plan
Common Issues & Fixes
| Issue | Root Cause | Fix |
|---|---|---|
| Gigabit not showing | Bad LAN cable | Replace with Cat6 |
| Speed stuck at 100 Mbps | 10/100 switch | Use Gigabit switch |
| Random Tally freezes | NIC power saving | Disable power management |
| Low Ethernet usage | Duplex mismatch | Auto negotiation |
| Works sometimes | Loose RJ45 | Re-crimp / replace |
Security Considerations
-
Avoid USB-to-Ethernet adapters on servers
-
Do not install unknown NIC drivers
-
Restrict physical access to network ports
-
Maintain consistent network configuration
-
Avoid unmanaged switches in server rooms
Best Practices for Tally Servers
-
Dedicated Gigabit LAN (minimum)
-
Cat6 structured cabling
-
High Performance power plan
-
NIC power saving disabled
-
SSD/NVMe for Tally data
-
Antivirus exclusions for Tally folders
-
Periodic LAN health audit
-
Monthly Tally data rewrite
Conclusion
A Tally server running on a 100 Mbps network instead of Gigabit can appear healthy in terms of CPU and RAM, yet still cause severe performance issues for users. In most cases, the problem lies not in Tally or Windows, but in the physical network layer—cables, switches, or power-saving features.
Ensuring true Gigabit connectivity is a mandatory baseline requirement for stable, responsive multi-user Tally operations.
#Tally #TallyPrime #TallyServer #TallyPerformance #TallyNetwork
#GigabitLAN #LANIssue #WindowsServer #AccountingSoftware
#NetworkTroubleshooting #ITSupport #ServerOptimization
#Broadcom #Ethernet #Cat6 #GigabitSwitch
#MultiUserTally #TallySlow #TallyNotResponding
#Infrastructure #ITAdmin #SystemAdministrator
#NetworkCard #SpeedDuplex #LANPerformance
#EnterpriseIT #AccountingIT #ServerMaintenance
Was this guide useful?
Your answer helps us keep BISONKB accurate and practical.