A common TallyPrime network issue occurs when TallyPrime works correctly on the server or main computer but client PCs show Educational Mode, cannot detect the license, or fail to connect to the license server.

This situation usually indicates that the TallyPrime license itself is active, but the client computer is unable to communicate correctly with the system or service providing the license.

The problem may be related to:

• Network connectivity
• Incorrect server name or IP address
• TallyPrime license configuration
• Windows Firewall
• Antivirus or endpoint security
• Required port being blocked
• Tally services not running
• DNS/name-resolution problems
• Different TallyPrime versions
• Network profile or Windows permissions
• VPN or multiple network adapters
• Changes to the server's IP address

This article explains how to systematically diagnose and resolve the problem.

1. Understand the Problem First

Suppose TallyPrime is installed on:

Server / Main PC

• TallyPrime opens normally.
• The license is detected.
• Licensed features are available.

Client PC

• TallyPrime opens in Educational Mode, or
• License cannot be detected, or
• TallyPrime cannot connect to the license server.

This generally means that the first thing to troubleshoot is communication between the client and the license-hosting system, rather than surrendering or reactivating the license immediately.

2. Do Not Reactivate the License Immediately

If TallyPrime is already working correctly on the server, avoid surrendering, reactivating, deleting, or otherwise changing the working license as your first troubleshooting step.

The license being functional on the server is an important clue.

First check:

1. Server-to-client network connectivity
2. License configuration
3. Firewall
4. Tally services
5. Port accessibility
6. TallyPrime versions
7. Windows network settings

Changing the working license unnecessarily can complicate troubleshooting.

3. Confirm That the Server Is Properly Licensed

Open TallyPrime directly on the server.

Verify that it is operating in the expected licensed mode rather than Educational Mode.

Also verify that the license displayed is the license you expect the client computers to use.

If the server itself has suddenly entered Educational Mode, the issue is no longer limited to client connectivity and should be troubleshot as a server/license problem first.

4. Check Whether Server and Client Are on the Same Network

The client must be able to communicate with the system providing the required TallyPrime licensing service.

On both computers, open Command Prompt and run:

ipconfig

For example:

Server:
192.168.1.10

Client:
192.168.1.25

With a normal subnet configuration, these may be on the same LAN.

However, IP addresses alone do not guarantee connectivity. VLANs, firewall rules, VPNs and routing policies can still prevent communication.

5. Ping the Server from the Client

On the client PC, open Command Prompt and run:

ping 192.168.1.10

Replace the IP address with the actual server IP.

You may receive:

Reply from 192.168.1.10

This confirms basic IP communication.

If you receive:

Request timed out

or:

Destination host unreachable

investigate the network before concentrating on TallyPrime.

Check:

• LAN cable
• Wi-Fi connection
• Network switch
• VLAN configuration
• Windows Firewall
• Server network profile
• Router configuration
• IP address
• Subnet mask
• VPN connection

Important

Ping can be blocked by Windows Firewall even when other network communication works. Therefore, a failed ping is useful evidence but is not by itself proof that the Tally licensing port is inaccessible.

6. Test the Server by Computer Name

If the client has been configured using the server's hostname, test name resolution.

Run:

ping SERVERNAME

If the server IP works but the hostname does not, the issue may be DNS or Windows name resolution.

Check:

nslookup SERVERNAME

You can also run:

ipconfig /flushdns

and retry.

If appropriate for your network, using a stable server IP can help avoid hostname-resolution problems.

7. Check the TallyPrime License Configuration on the Client

Open TallyPrime on the affected client and review its license-related configuration.

Confirm that the client is pointing to the correct:

Server name/IP address
Port

For example:

192.168.1.10:PORT

The actual value must match the configuration used in your TallyPrime environment.

Do not assume a port number based on an old installation or internet article. Check the currently configured port on the server/license environment.

8. Check the Tally License Service

On the server press:

Windows + R

Enter:

services.msc

Look for the applicable Tally licensing/service component installed in your environment.

Verify that the required service is:

Running

If it is stopped, start it.

If it is already running but clients cannot connect, restarting the appropriate service can sometimes restore communication.

Caution

Restarting a licensing or application service can temporarily affect connected Tally users. Perform service restarts during a suitable maintenance window if the server is in production.

9. Verify the License Port

Tally network licensing requires communication between the client and the appropriate server/service.

Determine the actual port configured in your installation.

Once you know it, test the port from the client.

In PowerShell:

Test-NetConnection 192.168.1.10 -Port PORTNUMBER

For example:

Test-NetConnection 192.168.1.10 -Port 12345

Here, 12345 is only an example.

Look for:

TcpTestSucceeded : True

If it shows:

TcpTestSucceeded : False

the client cannot establish a TCP connection to that server and port.

Investigate:

• Windows Firewall
• Antivirus firewall
• Endpoint security
• Server service
• Incorrect port
• Incorrect IP address
• VLAN/access-control rules
• Network firewall

10. Check Whether the Port Is Listening on the Server

On the server, you can investigate listening TCP ports with:

netstat -ano | findstr LISTENING

For a known port:

netstat -ano | findstr :PORTNUMBER

Example:

netstat -ano | findstr :12345

If the expected service is not listening on the configured port, investigate the server-side Tally configuration or service.

11. Check Windows Defender Firewall

Windows Firewall is one of the most common causes of server/client communication problems.

On the server, open:

Windows Defender Firewall with Advanced Security

Review:

Inbound Rules

Ensure the applicable Tally executable/service or required TCP port is permitted for the correct network profiles.

Depending on the environment, you may create an inbound rule for the required port.

Typical process:

1. Open Windows Defender Firewall with Advanced Security.
2. Select Inbound Rules.
3. Select New Rule.
4. Select Port.
5. Choose the appropriate protocol, normally TCP when required by the service.
6. Enter the actual configured port.
7. Select Allow the connection.
8. Apply only to appropriate network profiles.
9. Give the rule a descriptive name.

For example:

TallyPrime License Access

Do not unnecessarily expose a licensing port to public/untrusted networks.

12. Test Firewall as a Diagnostic Step

If you strongly suspect Windows Firewall, an administrator may temporarily disable the relevant firewall profile for a very short controlled test.

Immediately test TallyPrime from the client.

If it starts working, you have identified a firewall-rule problem.

Re-enable the firewall immediately and create the appropriate application/port rule.

Do not leave Windows Firewall permanently disabled.

13. Check Antivirus and Endpoint Security

Third-party security software can also block LAN traffic.

Examples include endpoint protection, antivirus firewalls, application-control products and corporate security agents.

Check whether the security software is blocking:

• TallyPrime executable
• Tally licensing service
• Server IP address
• Client/server communication
• Required TCP port

Do not permanently disable antivirus merely to make Tally work. Create a narrowly scoped, vendor-supported exception only when necessary.

14. Verify the Server's IP Address Has Not Changed

This is particularly important when the server receives its IP address automatically through DHCP.

For example, the server may originally have been:

192.168.1.10

and after a reboot it becomes:

192.168.1.18

If clients are still trying to reach:

192.168.1.10

they may no longer find the licensing service.

Run on the server:

ipconfig

Verify the current IPv4 address.

For servers, consider using an appropriately managed static IP address or DHCP reservation according to your network design.

15. Check Multiple Network Adapters

Servers sometimes have several adapters, such as:

• Ethernet
• Wi-Fi
• VPN
• Hyper-V virtual adapter
• VMware adapter
• VirtualBox adapter
• Tailscale adapter
• Other virtual NICs

Run:

ipconfig

Identify the IP address actually reachable from the client LAN.

Do not accidentally configure the client to use a virtual or VPN adapter address unless that is intentionally how the network is designed.

16. Check the Windows Network Profile

A Windows server connected to a network classified as Public may have more restrictive firewall behavior than expected.

Open:

Settings
→ Network & Internet
→ Ethernet

or the applicable network adapter.

Verify that the network profile is appropriate for your trusted business LAN.

Do not change an untrusted network to Private simply to bypass security restrictions.

17. Check TallyPrime Version on Server and Client

The server and client installations should be maintained at compatible supported versions/releases.

Check the TallyPrime release installed on:

Server
Client 1
Client 2
Client 3

If one computer is significantly different from the others, update or align the installations according to Tally's supported configuration.

Before upgrading a production installation:

• Back up company data.
• Record the current release.
• Check compatibility with TDL/customizations.
• Verify add-ons.
• Check integration software.
• Plan downtime if necessary.

18. Compare a Working Client with the Non-Working Client

If several client computers are available, this is one of the fastest diagnostic methods.

Suppose:

Server – Working
Client A – Working
Client B – Working
Client C – Not Working

The server and license service are probably functioning.

Compare Client C with Client A:

• TallyPrime version
• Server IP
• License configuration
• Port
• Windows Firewall
• Antivirus
• Network adapter
• DNS
• VPN
• Windows permissions

If all clients stop working simultaneously while the server still works, investigate the server/service/network path first.

19. Check for VPN Interference

VPN software can change:

• Routing
• DNS
• Network priority
• Firewall rules
• Interface metrics

Temporarily disconnect a nonessential VPN and test again.

If TallyPrime begins detecting the license, inspect the VPN's routing configuration rather than leaving the VPN permanently disabled.

20. Flush DNS and Reset Network Components

If network resolution appears corrupted, start with:

ipconfig /flushdns

If broader Windows networking problems exist, administrators may consider:

netsh winsock reset

and:

netsh int ip reset

A restart is normally required after network-stack resets.

Warning

netsh int ip reset can affect customized IP/network settings. Record important network configuration before using it, particularly on servers.

21. Test Access Using Both Hostname and IP Address

If you normally use:

TALLYSERVER

test the actual server IP.

If IP-based communication works but hostname-based communication fails, investigate:

• DNS
• Hosts file
• Local DNS suffix
• NetBIOS/name resolution
• Incorrect cached DNS record

22. Check Windows Hosts File

The Windows hosts file is located at:

C:\Windows\System32\drivers\etc\hosts

An old manual entry could point the server name to an incorrect IP.

For example:

192.168.1.5 TALLYSERVER

If the actual server is now:

192.168.1.10

the old hosts entry can cause connectivity problems.

Modify the hosts file only if you understand why the entry exists.

23. Check Date and Time

Ensure the server and client have reasonably synchronized:

• Date
• Time
• Time zone

Run:

w32tm /query /status

Severely incorrect system time can create authentication and other network problems.

24. Check Whether Tally Processes Are Running

On the server, open Task Manager:

Ctrl + Shift + Esc

Check the applicable Tally processes/services.

If a service appears frozen, first determine whether active users are connected before restarting anything.

25. Restart in the Correct Order

If maintenance downtime is available, a controlled restart can help.

A useful sequence is:

1. Close TallyPrime on clients
2. Close TallyPrime on server if appropriate
3. Restart the applicable Tally licensing service
4. Restart TallyPrime on the server
5. Confirm server license
6. Start TallyPrime on one client
7. Test additional clients

This helps isolate whether the problem is server-side or client-specific.

26. Check Network Isolation

Some routers and Wi-Fi systems have options such as:

• AP Isolation
• Client Isolation
• Guest Network Isolation

A client connected to a guest Wi-Fi network may have internet access but be unable to reach the server.

For example:

Internet → Working
Google → Working
Server → Not reachable
Tally license → Not detected

Move the PC to the appropriate business LAN or correct the network policy.

27. Check VLAN Configuration

In managed business networks, the server and clients may be on separate VLANs.

For example:

Server VLAN:
192.168.10.x

Client VLAN:
192.168.20.x

They can communicate only if inter-VLAN routing and firewall policies permit the required traffic.

Ask the network administrator to verify the required client-to-server access.

28. Client Works by IP but Not Server Name

If:

Server IP → Works
Server hostname → Fails

the likely area to troubleshoot is name resolution.

Try:

ipconfig /flushdns

Then:

nslookup SERVERNAME

and:

ping SERVERNAME

Confirm that the returned IP belongs to the correct server.

29. Server Name Works but License Still Does Not

Successful ping proves only basic reachability.

It does not prove that the licensing service's TCP port is accessible.

Therefore run:

Test-NetConnection SERVERNAME -Port PORTNUMBER

If:

PingSucceeded : True
TcpTestSucceeded : False

focus on the specific service/port/firewall path.

30. Check TallyPrime Installation on the Client

If only one client fails and network/port tests are successful, the local TallyPrime installation may be damaged or misconfigured.

Before reinstalling:

1. Record the existing configuration.
2. Back up any locally stored files/settings that matter.
3. Confirm the correct TallyPrime installer/release.
4. Close TallyPrime.
5. Repair/reinstall according to the supported deployment method.
6. Reconfigure licensing if necessary.
7. Test again.

Avoid deleting folders blindly because they may contain configuration or other important files.

31. Administrator Rights

If TallyPrime behaves differently when launched normally versus Run as administrator, investigate:

• Folder permissions
• Registry permissions
• Security software
• Installation permissions
• User profile configuration

Do not make permanent administrator access the default solution unless the application or your deployment specifically requires it.

32. Important PowerShell Diagnostic Command

One of the most useful tests is:

Test-NetConnection SERVER-IP -Port PORT

For example:

Test-NetConnection 192.168.1.10 -Port 12345

Again, 12345 is only an example.

Result 1

TcpTestSucceeded : True

Network connectivity to that port exists.

Result 2

TcpTestSucceeded : False

Investigate:

• Wrong IP
• Wrong port
• Firewall
• Service not running
• Network security
• Routing
• VLAN rules

33. Quick Troubleshooting Flow

Follow this sequence:

Does TallyPrime work on the server?
        |
        +-- NO → Troubleshoot server/license first
        |
        +-- YES
             |
             v
Can client reach server?
             |
        +----+----+
        |         |
       NO        YES
        |         |
Network issue    Check configured
                 license server/port
                      |
                      v
              Is required TCP port reachable?
                      |
                +-----+-----+
                |           |
               NO          YES
                |           |
          Firewall /       Check Tally
          service /        configuration,
          routing          version and
                           local installation

34. Recommended Diagnostic Checklist

Before making major changes, record:

Server Name:
Server IPv4:
Client IPv4:
TallyPrime Version on Server:
TallyPrime Version on Client:
License Status on Server:
Configured License Server:
Configured Port:
Ping Result:
Hostname Resolution:
TCP Port Test:
Windows Firewall Status:
Antivirus/Endpoint Security:
VPN Active:
Network Profile:
Other Clients Working:

This information makes troubleshooting significantly faster.

Common Causes at a Glance

Problem	Typical Symptom	What to Check
Wrong server IP	Client cannot find license	Verify current server IPv4
Server IP changed	Previously worked, suddenly stopped	DHCP/static IP configuration
Firewall blocking	Server works, clients fail	Inbound firewall rules
Wrong port	License connection fails	Server/client license configuration
Service stopped	Multiple clients fail	Tally licensing/service status
DNS issue	IP works, hostname fails	DNS/name resolution
Antivirus blocking	Random or persistent failure	Endpoint firewall/application rules
Different Tally versions	Compatibility problems	Release/version alignment
VPN interference	Works when VPN disconnected	VPN routes and interface priority
Guest Wi-Fi	Internet works but server doesn't	Client/AP isolation
VLAN restriction	Server unreachable across subnets	Inter-VLAN firewall/routing
Client installation issue	Only one PC fails	Repair/reinstall client
Wrong network profile	LAN communication restricted	Windows firewall profile

Best Troubleshooting Order

For the fastest diagnosis, use this order:

Step 1: Confirm TallyPrime is licensed on the server.

Step 2: Determine whether one client or all clients are affected.

Step 3: Verify the server's current IP address.

Step 4: Test client-to-server communication.

Step 5: Verify hostname resolution.

Step 6: Confirm the license server address and configured port.

Step 7: Test the required TCP port using PowerShell.

Step 8: Check the applicable Tally licensing service.

Step 9: Check Windows Firewall and endpoint security.

Step 10: Compare TallyPrime versions.

Step 11: Check VPN, VLAN and multiple network adapters.

Step 12: Repair/reinstall the client only after connectivity has been confirmed.

FAQ

1. Why does TallyPrime work on the server but not the client?

The most common reason is that the client cannot correctly communicate with the server or licensing service. Incorrect server details, firewall rules, blocked ports, network configuration or client-side settings may be responsible.

2. Why does the client show Educational Mode while the server is licensed?

If the server is licensed but the client cannot obtain or detect the required network license, the client may operate in Educational Mode. Verify the license configuration and network path.

3. Should I surrender the license?

Not as the first step if the server's license is already working. Troubleshoot network and licensing-service communication first.

4. How can I test whether the client can reach the server?

Run:

ping SERVER-IP

Then test the required application port separately.

5. How do I test the Tally license port?

Use PowerShell:

Test-NetConnection SERVER-IP -Port PORTNUMBER

Replace the placeholders with the actual server IP and configured port.

6. What does TcpTestSucceeded : False mean?

It means the client could not establish a TCP connection to that server and port. Possible causes include firewall rules, wrong IP/port, routing problems or a service that is not listening.

7. Can Windows Firewall cause this issue?

Yes. The server can run TallyPrime locally while Windows Firewall prevents remote client connections.

8. Should I permanently disable Windows Firewall?

No. If temporarily disabling it proves that the firewall is responsible, re-enable it and create an appropriate restricted rule.

9. Can antivirus software block Tally licensing?

Yes. Endpoint security software can block programs, ports or network connections.

10. Why did Tally stop working on clients after restarting the server?

The server may have received a different DHCP IP address, a required service may not have started correctly, or network/firewall conditions may have changed.

11. Should the server have a static IP?

For business servers, a stable addressing method such as a properly configured static IP or DHCP reservation is generally preferable.

12. Can different TallyPrime versions cause problems?

Version differences can contribute to compatibility or configuration problems. Keep the deployment aligned with supported TallyPrime releases.

13. Why can I ping the server but Tally still does not work?

Ping and application communication are different. ICMP ping may succeed while the TCP port required by the licensing service is blocked.

14. Why does the IP address work but the server name fail?

This normally points toward DNS or Windows name-resolution problems.

15. Can a VPN cause TallyPrime license problems?

Yes. VPN software can modify routes, DNS settings, adapter priority and firewall behavior.

16. Can Wi-Fi client isolation block TallyPrime?

Yes. Guest Wi-Fi or AP/client isolation can prevent a PC from communicating with LAN devices even though internet access works.

17. What if only one client PC has the problem?

Compare the failing PC against a working client. Check its Tally version, license configuration, firewall, antivirus, VPN, DNS and local installation.

18. What if every client has stopped working?

If the server remains licensed but every client fails, concentrate on the server-side service, port, firewall, IP address and network infrastructure.

19. Should I reinstall TallyPrime immediately?

No. First verify connectivity and the license port. Reinstallation will not fix a blocked firewall port or incorrect server address.

20. Can VLAN configuration cause the issue?

Yes. If clients and the server are on different VLANs, routing and firewall policies must permit the required communication.

21. Can a Windows Update cause this problem?

Potentially. Updates can coincide with changes in firewall, network adapters, security software or system configuration. Diagnose the actual network and service state rather than assuming the update itself is the cause.

22. What is the most useful command for this problem?

After identifying the correct server IP and port:

Test-NetConnection SERVER-IP -Port PORTNUMBER

is particularly useful because it tests connectivity to the actual TCP port rather than only testing ping.

23. Do I need internet access for a client to communicate with a local Tally server?

Local server/client communication primarily depends on the LAN path between the systems. Internet availability and local LAN connectivity are separate issues.

24. Why does Tally work after disabling antivirus?

The antivirus or endpoint firewall may be blocking the application or its network traffic. Re-enable security and configure an appropriate exception rather than leaving protection disabled.

25. When should I contact Tally support?

Contact authorized Tally support if the server/license configuration appears correct, the network path and required port have been verified, but the licensing problem persists, or if license activation/reactivation itself appears damaged.

Important Security Note

Avoid using broad security changes merely to solve a Tally connectivity issue.

Do not permanently:

• Disable Windows Firewall
• Disable antivirus
• Disable endpoint protection
• Expose Tally-related ports directly to the public internet
• Give every user administrator rights
• Change server network configuration without documenting it

Troubleshoot the specific communication path and make the minimum necessary change.

Conclusion

When TallyPrime works on the server but not on client PCs, the active license itself is often not the first component to change.

Start by confirming:

Server license
        ↓
Server IP
        ↓
Client-to-server connectivity
        ↓
Server name resolution
        ↓
License server configuration
        ↓
Configured port
        ↓
TCP port connectivity
        ↓
Tally service
        ↓
Windows Firewall
        ↓
Antivirus/security software
        ↓
TallyPrime version
        ↓
Client installation

This structured approach helps prevent unnecessary license surrender/reactivation and makes it much easier to identify whether the failure is related to TallyPrime, Windows or the network.

 

Disclaimer

This article is intended for technical education and general troubleshooting purposes only. TallyPrime versions, licensing architecture, menus, services and configuration options may change between releases. Always verify current procedures with official Tally documentation or authorized Tally support before modifying production licensing.

Before making changes to a production server, firewall, network configuration, Tally installation or company data, maintain a verified backup and record the existing configuration. The author/publisher is not responsible for data loss, license problems, downtime, security issues or other consequences resulting from the use of this information.

 

#TallyPrime #Tally #TallyPrimeLicense #TallyLicense #TallyPrimeSupport #TallySupport #TallyPrimeTroubleshooting #TallyTroubleshooting #TallyPrimeServer #TallyServer #TallyPrimeClient #TallyClient #TallyPrimeNetwork #TallyNetwork #TallyPrimeLAN #NetworkLicense #LicenseServer #TallyEducationalMode #EducationalMode #TallyPrimeError #TallyLicenseError #TallyPrimeFix #TallyFix #WindowsServer #Windows11 #WindowsNetworking #NetworkTroubleshooting #LAN #ServerTroubleshooting #ClientServer #WindowsFirewall #Firewall #FirewallTroubleshooting #TCP #TCPPort #PowerShell #TestNetConnection #NetworkDiagnostics #ServerIP #StaticIP #DNS #DNSTroubleshooting #Antivirus #EndpointSecurity #VPN #VLAN #ITSupport #TechnicalSupport #WindowsSupport #TallyPrimeGuide