TallyPrime is frequently deployed in a multi-user environment where company data is stored on a central Windows computer or server and accessed by other computers over the LAN.

A typical environment may look like:

Server / Data Computer

• Stores TallyPrime company data
• Shares the Tally data folder
• May host other business applications
• Has a static or reserved IP address

Client Computers

• Run TallyPrime
• Access company data over the network
• May use a UNC path or mapped network drive

A working environment can suddenly stop functioning after seemingly unrelated infrastructure changes such as:

• Router replacement
• Server IP address change
• Network subnet change
• DHCP configuration change
• Windows Firewall policy change
• Antivirus installation or update
• Windows Update
• Server migration
• Network share modification
• Password or user account changes
• Mapped drive disconnection

The important point is that a message appearing to be a "TallyPrime network error" does not necessarily mean TallyPrime itself is damaged.

The problem may actually exist at one of several layers:

TallyPrime → Windows → Permissions → SMB/File Sharing → Firewall/Antivirus → TCP/IP → Router/Switch → Server

Troubleshooting these layers systematically is much safer than immediately reinstalling TallyPrime.

2. Common Symptoms

Users experiencing TallyPrime networking problems may report:

• TallyPrime company not appearing
• Company data not opening
• TallyPrime data path unavailable
• Network path not found
• Access denied
• Shared folder unavailable
• Mapped drive disconnected
• Server not reachable
• TallyPrime works on server but not client
• TallyPrime stopped working after router replacement
• TallyPrime stopped working after changing server IP
• Network drive displays a red X
• TallyPrime becomes slow while accessing company data
• Windows asks for network credentials
• Client PC can access Internet but cannot access Tally server
• Ping works but shared folder does not open
• Shared folder opens but TallyPrime cannot access company data

These symptoms must be diagnosed individually.

3. Understand a Typical TallyPrime Network Setup

Consider the following example.

Server:

Computer Name: TALLYSERVER
IP Address: 192.168.1.10
Tally Data Folder: D:\TallyData

Shared folder:

\\TALLYSERVER\TallyData

The same share might also be reachable through:

\\192.168.1.10\TallyData

A mapped drive may be configured as:

T: = \\TALLYSERVER\TallyData

TallyPrime could therefore be configured to access:

T:\

or a network path such as:

\\TALLYSERVER\TallyData

If the router is changed and the network moves from:

192.168.1.x

to:

192.168.0.x

the server may receive a different address.

For example:

Old:

192.168.1.10

New:

192.168.0.25

Anything depending directly on the old IP address may stop working.

4. TallyPrime Network Error After Changing Router

Changing a router can affect much more than Internet access.

The new router may introduce:

• Different DHCP range
• Different subnet
• Different default gateway
• Different DNS configuration
• New network profile
• Client isolation
• VLAN configuration
• Different firewall policies
• Different IP addresses for servers and clients

For example:

Old router:

Router: 192.168.1.1
Server: 192.168.1.10
Client: 192.168.1.20

New router:

Router: 192.168.0.1
Server: 192.168.0.15
Client: 192.168.0.25

If TallyPrime clients were accessing:

\\192.168.1.10\TallyData

the path will no longer work.

5. Check the Server's Current IP Address

On the server, open Command Prompt and run:

ipconfig

Look for:

IPv4 Address
Subnet Mask
Default Gateway

Example:

IPv4 Address: 192.168.0.15
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.0.1

Write down the correct IP address.

Do not assume that the server retained its old IP after changing the router.

6. Check the Client IP Address

Run:

ipconfig

on a client computer.

Suppose you see:

Server: 192.168.0.15
Client: 192.168.0.28
Mask: 255.255.255.0

Both computers are normally on the same /24 subnet.

However, if you find:

Server: 192.168.1.10
Client: 192.168.0.28

then they may be on different subnets.

Communication would require correct routing between those networks.

7. Test Network Connectivity Using Ping

From the client computer:

ping 192.168.0.15

If you receive replies such as:

Reply from 192.168.0.15

basic IP connectivity exists.

If you receive:

Request timed out

investigate:

• Firewall
• Wrong IP address
• Different VLAN
• Network isolation
• Cabling
• Switch configuration
• Router configuration
• Server NIC
• Incorrect subnet

However, remember:

Successful ping does not prove that Windows file sharing or TallyPrime access is working.

ICMP and SMB are different network services.

8. Test the Server by Computer Name

Run:

ping TALLYSERVER

If pinging the IP works but the server name fails, investigate name resolution.

You can also try:

\\TALLYSERVER

from File Explorer.

If:

\\192.168.0.15

works but:

\\TALLYSERVER

does not, the problem is likely related to hostname resolution rather than TallyPrime itself.

9. TallyPrime Not Working After Changing Server IP

This is one of the most common causes of sudden network failure.

Suppose the old server IP was:

192.168.1.10

and TallyPrime clients were accessing:

\\192.168.1.10\TallyData

If the server becomes:

192.168.1.25

the original path points to the wrong address.

Solution

Update all references to the server.

Check:

• TallyPrime data paths
• Windows mapped drives
• Desktop shortcuts
• Batch files
• Backup scripts
• Scheduled tasks
• Third-party backup programs
• Other software integrations

A better long-term configuration is often to use a stable server hostname where appropriate:

\\TALLYSERVER\TallyData

instead of:

\\192.168.1.10\TallyData

However, hostname-based access requires reliable name resolution.

10. Give the Server a Stable IP Address

A business server should normally not depend on an unpredictable DHCP address.

Two common methods are:

Option 1 – DHCP Reservation

Reserve an IP for the server's network adapter in the router or DHCP server.

Example:

TALLYSERVER → 192.168.1.10

Option 2 – Static IP

Configure an appropriate static IP on the server.

Example:

IP: 192.168.1.10
Subnet: 255.255.255.0
Gateway: 192.168.1.1

DNS settings should also match the network design.

Important

Never randomly assign an IP address without confirming that another device is not already using it.

Duplicate IP addresses can produce intermittent and confusing network failures.

11. Check for Duplicate IP Address Problems

If two devices receive the same IP, symptoms can include:

• Intermittent connectivity
• TallyPrime disconnecting
• Server appearing and disappearing
• Ping results changing
• Shared folder intermittently unavailable

You can inspect the ARP cache using:

arp -a

However, duplicate-IP troubleshooting should also include DHCP leases and network infrastructure.

12. Test the Shared Folder Directly

Before troubleshooting TallyPrime, verify whether Windows can access the data folder.

Press:

Windows + R

Enter:

\\TALLYSERVER\TallyData

or:

\\192.168.0.15\TallyData

If the folder opens correctly, basic Windows file-sharing access is working.

If it does not, solve the Windows networking issue first.

13. TallyPrime Network Sharing Permission Problem

Windows network shares have two important permission layers:

1. Share permissions
2. NTFS permissions

Both must permit the required access.

For example, suppose the actual folder is:

D:\TallyData

Right-click the folder and open:

Properties → Sharing → Advanced Sharing

Confirm that the folder is shared.

Then review:

Permissions

Next check:

Properties → Security

The appropriate users or security groups must have the permissions required for normal TallyPrime operation.

14. Share Permissions vs NTFS Permissions

Administrators sometimes modify only the Sharing tab and forget the Security tab.

Effective access depends on both.

For example:

Share permission:

Change / Read

NTFS permission:

Read only

The user may still be unable to modify files as required.

Conversely, NTFS Full Control does not help if the network share itself prevents the required access.

Use properly designed user/group permissions rather than broadly granting access to everyone unless the environment and security policy specifically justify it.

15. Test Whether the User Can Create a File

A useful diagnostic test is to open the shared Tally data location from the affected client.

Try:

1. Creating a temporary folder
2. Creating a temporary text file
3. Renaming it
4. Deleting it

If the user can only read files but cannot create, modify, or delete them, permissions are probably incorrect.

Remove the test file afterward.

16. Windows Credentials Can Cause Access Problems

Windows may cache credentials for a server.

Open:

Control Panel → Credential Manager → Windows Credentials

Look for credentials associated with:

TALLYSERVER

or its IP address.

Incorrect or outdated credentials may prevent access after:

• Password change
• Server migration
• User account change
• Workgroup/domain change

Do not indiscriminately delete all stored credentials. Remove or update only the relevant server credentials after confirming their purpose.

17. Windows Defender Firewall Blocking TallyPrime

Windows Defender Firewall can block network communication even when TallyPrime itself is working correctly.

First determine whether the issue concerns:

• TallyPrime executable traffic
• Windows file sharing
• A Tally-related network service
• Another integration/service
• Network profile configuration

Do not simply disable Windows Firewall permanently.

That removes an important security layer.

18. Check the Windows Network Profile

Open:

Settings → Network & Internet

Check whether the network is:

Public

or:

Private

A trusted internal business LAN is commonly configured as a Private network where appropriate.

Windows applies more restrictive sharing/firewall behavior to Public networks.

A router replacement can sometimes cause Windows to identify the connection as a new network.

Therefore, after changing a router, always verify the network profile on the server and clients.

19. Check File and Printer Sharing Firewall Rules

Open:

Windows Defender Firewall with Advanced Security

Review inbound rules relating to:

File and Printer Sharing

Windows file sharing commonly uses SMB over TCP port:

TCP 445

Legacy environments may involve additional NetBIOS-related ports, but modern Windows environments should avoid enabling obsolete protocols unnecessarily.

Enable only the rules genuinely required for the environment and preferably limit them to the correct network profile and trusted network scope.

20. Create Firewall Rules Carefully

If a specific TallyPrime component needs network communication, application-based firewall rules can be preferable to unnecessarily opening broad port ranges.

Before creating rules:

1. Confirm the executable path.
2. Confirm whether inbound access is actually required.
3. Confirm the applicable network profile.
4. Restrict remote IP scope when possible.
5. Document the rule.

Avoid copying arbitrary firewall port lists from Internet forums without verifying that those ports are required for your exact TallyPrime configuration.

21. Temporary Firewall Test

For diagnosis only, an administrator may briefly test connectivity with a firewall profile disabled in a controlled trusted environment.

If TallyPrime immediately begins working, investigate firewall rules.

Then:

Re-enable the firewall immediately.

Do not leave Windows Defender Firewall disabled as the permanent solution.

22. Antivirus Blocking TallyPrime

Third-party antivirus, endpoint protection, EDR, anti-ransomware software, or controlled-folder features may interfere with business applications.

Possible symptoms include:

• TallyPrime not launching
• Company data not opening
• Company access becoming very slow
• Network data inaccessible
• File creation blocked
• TallyPrime executable quarantined
• Data files locked
• Network share blocked

Check the antivirus:

• Detection history
• Quarantine
• Application control
• Ransomware protection
• Network protection
• Firewall module
• Behavior monitoring
• Controlled folder protection

23. Do Not Exclude the Entire Drive Without Reason

A common troubleshooting mistake is adding exclusions such as:

C:\

or:

D:\

to antivirus.

This can expose the system to malware and ransomware.

Instead, if a vendor-approved exclusion is genuinely required, make it as narrow as possible.

For example:

• Specific application executable
• Specific Tally application directory
• Specific data location

Only create exclusions after determining that security software is actually causing the problem.

24. Check Antivirus Quarantine

If TallyPrime suddenly stops working after an antivirus update:

1. Open antivirus console.
2. Check quarantine.
3. Check detection history.
4. Check blocked applications.
5. Check behavioral protection events.

Do not automatically restore a quarantined file merely because its filename resembles a legitimate application.

Verify its path, digital signature, source, and security status first.

25. TallyPrime Mapped Drive Not Working

A mapped network drive may look like:

T:\

mapped to:

\\TALLYSERVER\TallyData

Mapped drives can stop working because of:

• Server IP changed
• Server name not resolving
• User password changed
• Stored credentials invalid
• Share name changed
• Server offline
• Mapping created under another Windows account
• Drive mapping script failed
• Network not ready during login
• VPN unavailable
• SMB blocked

26. Check Existing Mapped Drives

Open Command Prompt:

net use

You may see:

T:    \\TALLYSERVER\TallyData

If the mapping points to an old location, remove only that mapping:

net use T: /delete

Then recreate it:

net use T: \\TALLYSERVER\TallyData /persistent:yes

Use the correct server and share name for your environment.

27. Mapped Drive Shows a Red X

A red X does not always mean the drive is permanently unavailable.

Windows may not have reconnected it yet.

Double-click the drive.

If Windows requests credentials, provide an authorized account.

If the mapping continues failing, test the underlying UNC path:

\\TALLYSERVER\TallyData

If UNC access works but the mapped drive does not, the issue is probably the drive mapping rather than the server share itself.

28. Prefer UNC Paths Where Appropriate

Mapped drives depend on per-user Windows configuration.

For some deployments, a UNC path can be more reliable:

\\TALLYSERVER\TallyData

instead of:

T:\

Advantages can include:

• No drive-letter conflict
• Less dependence on per-user mappings
• Easier troubleshooting
• More consistent path definition

Whether this is suitable depends on the TallyPrime version, environment, and organizational configuration.

29. TallyPrime Works on Server but Not Client

This is an important diagnostic clue.

If TallyPrime works locally on the server but fails on every client, investigate:

• Network connectivity
• Firewall
• SMB/file sharing
• Permissions
• Server name resolution
• Network profile
• Client network configuration
• Antivirus/EDR
• Incorrect data path

Do not immediately repair or rewrite company data simply because clients cannot access it.

If the same company opens locally on the server, the data itself may not be the primary problem.

30. One Client Fails but Others Work

If ten computers can access TallyPrime and only one cannot, the server is less likely to be the main cause.

Focus on the affected PC:

• IP configuration
• DNS
• Network profile
• Firewall
• Antivirus
• Credentials
• Mapped drive
• Windows permissions
• TallyPrime data path
• NIC configuration

Compare the affected PC with a working PC.

This can dramatically reduce troubleshooting time.

31. All Clients Fail Simultaneously

If every client suddenly loses access, investigate shared infrastructure first:

• Server
• Switch
• Router
• Firewall
• Server NIC
• Server IP
• Windows network profile
• Shared folder
• Server security software

A simultaneous failure across all clients usually points toward a common dependency.

32. Ping Works but TallyPrime Does Not

This situation is common.

Successful ping proves only that ICMP communication is functioning.

It does not prove:

• SMB is working
• TCP 445 is allowed
• Share permissions are correct
• NTFS permissions are correct
• Credentials are valid
• TallyPrime is using the correct path

Next test:

\\SERVER-IP

and:

\\SERVER-NAME

Then test the actual share.

33. Internet Works but TallyPrime Does Not

Internet access and local server access are different services.

A computer may browse websites normally while being unable to reach the local Tally server because of:

• Incorrect VLAN
• Client isolation
• Windows Firewall
• SMB blocking
• Incorrect subnet
• Wrong server address
• Wi-Fi guest network
• Permissions

Do not use Internet connectivity alone as proof that the LAN is correctly configured.

34. Wi-Fi Client Isolation

Some routers and Wi-Fi access points provide settings such as:

• AP Isolation
• Client Isolation
• Wireless Isolation
• Guest Network Isolation

When enabled, wireless devices may access the Internet but not other LAN devices.

This can cause:

Internet works → Tally server does not

If TallyPrime stopped working immediately after installing a new router or access point, check this feature.

35. Guest Wi-Fi Problem

Never assume that a device connected to Wi-Fi is on the same business LAN.

Guest Wi-Fi commonly prevents access to internal devices.

A client might receive:

192.168.50.x

while the server is:

192.168.1.x

The user gets Internet access but cannot access TallyPrime.

Connect the workstation to the appropriate trusted corporate network.

36. Check Windows SMB Configuration

Windows file sharing normally relies on SMB.

Modern Windows systems should use supported SMB versions.

Avoid enabling SMB 1.0/CIFS merely as a generic troubleshooting measure.

SMB1 is obsolete and presents significant security concerns.

If an old device or NAS requires SMB1, upgrading or replacing that device is generally preferable.

37. DNS and Name Resolution Problems

If:

\\192.168.1.10\TallyData

works

but:

\\TALLYSERVER\TallyData

does not,

investigate name resolution.

Useful commands include:

ping TALLYSERVER

nslookup TALLYSERVER

ipconfig /flushdns

The exact name-resolution mechanism depends on whether the environment uses:

• Active Directory DNS
• Router DNS
• Local DNS server
• Workgroup networking

Do not use permanent hosts-file entries as the first solution unless there is a specific design reason.

38. Check the Server Name

On the server:

hostname

or:

echo %computername%

Confirm that clients are using the correct computer name.

Server migration or renaming can leave old mappings pointing to a hostname that no longer exists.

39. Check Windows Services

Windows networking depends on several services.

Depending on the environment, relevant services can include:

• Server
• Workstation
• DNS Client
• Function Discovery Provider Host
• Function Discovery Resource Publication

Do not randomly enable or disable services.

Instead, investigate whether a required service has unexpectedly stopped or has been disabled by a hardening utility or security policy.

40. Network Discovery

On trusted business networks, check:

Control Panel
    ↓
Network and Sharing Center
    ↓
Advanced sharing settings

Review:

• Network discovery
• File and printer sharing

Remember that Network Discovery affects visibility in Windows Explorer, but direct UNC access may still work even if the server is not displayed under Network.

Therefore:

"Server not visible in Network" does not necessarily mean "Server unreachable."

Always test the UNC path directly.

41. Test TCP Port 445

PowerShell can be used to test SMB connectivity:

Test-NetConnection 192.168.1.10 -Port 445

Look for:

TcpTestSucceeded : True

If it returns False, investigate:

• Windows Firewall
• Third-party firewall
• Router/VLAN ACL
• Endpoint security
• Server service
• Network path

This is often more useful than ping for diagnosing Windows file-sharing problems.

42. Check Share Availability

From the client:

net view \\TALLYSERVER

This may help determine whether Windows can enumerate server shares.

You can also test the share directly:

\\TALLYSERVER\TallyData

Direct testing is usually more useful than relying only on Windows Network browsing.

43. Clear Stale Network Sessions Carefully

Windows may maintain an existing connection using old credentials.

Check:

net use

If appropriate, remove only the problematic connection.

Avoid casually running commands that disconnect every network share on a production workstation, because users may have other mapped business resources open.

44. Router Replacement Checklist

After replacing a router, verify:

1. Router LAN IP
2. DHCP scope
3. Server IP
4. Client IP addresses
5. Subnet mask
6. Default gateway
7. DNS configuration
8. Server DHCP reservation
9. VLAN configuration
10. Wi-Fi isolation
11. Guest network settings
12. Firewall policies
13. Server hostname resolution
14. Shared folder access
15. Mapped drives
16. TallyPrime data path

Document the old network configuration before replacing networking equipment whenever possible.

45. Server IP Change Checklist

After changing the server IP, review:

• TallyPrime data paths
• Mapped drives
• Backup software
• Scheduled backup jobs
• Desktop shortcuts
• Batch scripts
• Network scanners
• Accounting integrations
• Remote-access configurations
• Firewall rules containing old IP scopes
• DNS records
• DHCP reservations

Changing a server IP can affect applications other than TallyPrime.

46. Recommended Troubleshooting Order

When TallyPrime stops working over the network, troubleshoot in this order:

Step 1 – Confirm Server Is Running

Check whether the server is powered on and Windows is operational.

Step 2 – Check Server IP

ipconfig

Step 3 – Check Client IP

ipconfig

Step 4 – Test Ping

ping SERVER-IP

Step 5 – Test SMB Port

Test-NetConnection SERVER-IP -Port 445

Step 6 – Test Server Share

\\SERVER-IP\ShareName

Step 7 – Test Hostname

\\SERVERNAME\ShareName

Step 8 – Check Share Permissions

Review Sharing permissions.

Step 9 – Check NTFS Permissions

Review Security permissions.

Step 10 – Check Firewall

Verify Windows Defender Firewall and any third-party firewall.

Step 11 – Check Antivirus/EDR

Review blocked events and quarantine.

Step 12 – Check Mapped Drive

net use

Step 13 – Check TallyPrime Data Path

Confirm TallyPrime is accessing the correct location.

This layered approach helps identify the real failure instead of making unnecessary changes.

47. Do Not Reinstall TallyPrime First

Reinstalling TallyPrime is rarely the correct first response to a network problem.

If:

\\SERVER\TallyData

cannot be opened in Windows Explorer, reinstalling TallyPrime will probably not solve the underlying issue.

Fix the Windows/network problem first.

Only investigate the TallyPrime installation itself after confirming that the underlying network path and permissions are healthy.

48. Do Not Rewrite Company Data for a Network Problem

TallyPrime data repair/rewrite operations should not be performed simply because a network share stopped working.

A network-access problem is different from data corruption.

Before performing data repair:

• Take a verified backup.
• Confirm the issue is actually data-related.
• Prefer testing the company locally in a controlled environment.
• Follow the applicable Tally support guidance.

Unnecessary repair operations can complicate recovery.

49. Important Data Safety Warning

Never perform aggressive troubleshooting directly against the only copy of live accounting data.

Before major changes:

1. Take a backup.
2. Confirm that the backup is readable.
3. Keep another copy away from the live data.
4. Avoid experimenting with permissions on the only data copy.
5. Do not move or rename live company folders while users are working.
6. Ensure users exit TallyPrime before major server maintenance.

For business-critical accounting data, backups should also be protected against ransomware and accidental deletion.

50. Recommended Network Design for TallyPrime

A more reliable small-business setup might use:

Internet
    │
  Router
    │
Managed/Business Switch
    │
┌───┴─────────────┐
│                 │

Server Clients
192.168.1.10 DHCP Range
│
│
D:\TallyData
│
Shared as
\TALLYSERVER\TallyData

Recommended practices include:

• Stable server IP
• Reliable Ethernet connectivity
• Gigabit or faster LAN where appropriate
• Proper DNS/name resolution
• Correct NTFS permissions
• Controlled share permissions
• Firewall enabled
• Endpoint protection enabled
• Tested backups
• UPS for critical server/network equipment
• Documented network configuration

51. Ethernet vs Wi-Fi for TallyPrime

For critical multi-user accounting environments, wired Ethernet is generally preferable for the server and heavily used workstations.

Wi-Fi is more vulnerable to:

• Signal interference
• Roaming
• Temporary disconnections
• Congestion
• Power-saving behavior
• Access-point issues

Short network interruptions during file-based application activity can increase operational risk.

Where possible:

Server → Wired Ethernet

and preferably:

Accounting workstations → Wired Ethernet

52. Avoid Storing Live Tally Data in Consumer Sync Folders Without Validation

Do not automatically place actively used company data inside consumer synchronization folders merely to obtain cloud backup.

File-sync applications can introduce:

• File locking
• Synchronization conflicts
• Partial synchronization
• Version conflicts

Use a backup solution designed for the required workload and confirm compatibility with the application's live data.

53. Ransomware Considerations

A shared Tally data folder may be reachable from many computers.

If one client becomes infected with ransomware and has write permission to the share, accessible company files may also be encrypted.

Consider:

• Least-privilege permissions
• Endpoint protection
• Controlled administrative access
• Offline/immutable backups
• Versioned backups
• Multiple backup generations
• Backup monitoring
• Periodic restore tests

A network share alone is not a backup.

54. Practical Diagnostic Matrix

Symptom	Likely Area
Server IP cannot be pinged	Network/firewall/IP
IP works but hostname fails	DNS/name resolution
Ping works but port 445 fails	Firewall/SMB/network ACL
Server opens but share fails	Sharing/permissions
Share opens but cannot create files	NTFS/share permissions
UNC works but T: fails	Mapped drive
All clients fail	Server/network infrastructure
Only one client fails	Client configuration
Works locally but not remotely	Network/share/firewall
Stopped after router change	IP/subnet/profile/router
Stopped after antivirus update	Endpoint security
Internet works but server doesn't	LAN/VLAN/isolation/firewall

55. Useful Diagnostic Commands

IP configuration

ipconfig /all

Ping server

ping SERVER-IP

Ping hostname

ping SERVERNAME

Check hostname

hostname

Test SMB

Test-NetConnection SERVER-IP -Port 445

Check mapped drives

net use

List server shares

net view \\SERVERNAME

DNS lookup

nslookup SERVERNAME

Clear DNS cache

ipconfig /flushdns

View ARP table

arp -a

Use administrative privileges only where necessary.

56. Preventive Maintenance Recommendations

To prevent repeated TallyPrime network problems:

• Reserve a stable IP for the server.
• Document server IP and hostname.
• Document the Tally data path.
• Document share names.
• Use security groups for permissions.
• Keep Windows Firewall enabled.
• Maintain antivirus/EDR protection.
• Maintain verified backups.
• Test restore procedures periodically.
• Use UPS protection.
• Prefer wired LAN for the server.
• Avoid guest Wi-Fi for accounting PCs.
• Document router configuration before replacement.
• Test TallyPrime after infrastructure changes.
• Keep server and network diagrams updated.

Frequently Asked Questions (FAQ)

1. Why did TallyPrime stop working after changing the router?

The new router may have changed the server's IP address, subnet, DHCP range, DNS configuration, Windows network profile, VLAN, or client-isolation settings. Verify the server and client IP configuration first.

2. Why does TallyPrime not work after changing the server IP?

Clients may still be using the old IP address in their Tally data path, mapped drive, shortcut, firewall scope, backup script, or other configuration.

3. Can Windows Defender Firewall block TallyPrime?

Yes. It can block application traffic or the Windows file-sharing communication required to reach network-hosted data.

4. Should I disable Windows Firewall permanently?

No. Use temporary disabling only as a controlled diagnostic test when appropriate, then create the necessary restricted rules and re-enable protection.

5. Which port does Windows file sharing normally use?

Modern Windows SMB file sharing commonly uses TCP port 445.

6. Should I enable SMB1 for TallyPrime?

Do not enable SMB1 merely as a generic fix. SMB1 is obsolete and insecure. Use supported SMB versions whenever possible.

7. Why can I ping the server but not open TallyPrime data?

Ping tests ICMP connectivity. Tally data access may additionally require working SMB, permissions, credentials, firewall rules, and the correct data path.

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

The likely problem is network-related: connectivity, firewall, sharing permissions, credentials, name resolution, antivirus, or incorrect data path.

9. Why does only one client computer have the problem?

Check that PC's IP settings, firewall, antivirus, stored credentials, network profile, mapped drives, and TallyPrime configuration.

10. Why are all clients unable to access TallyPrime?

Check the server, router, switch, server IP, server firewall, server network profile, shared folder, and security software.

11. Why does the mapped Tally drive show a red X?

The server may have been temporarily unavailable, the mapping may use an old path, or Windows may not have reauthenticated the connection.

12. Should I use a mapped drive or UNC path?

Both can work. A UNC path can eliminate drive-letter mapping dependencies, provided the application and environment support the configuration.

13. Can antivirus block TallyPrime?

Yes. Antivirus, EDR, anti-ransomware, application-control, and firewall products can block executables or data access.

14. Should I exclude the whole Tally drive from antivirus?

Generally no. Use narrowly scoped exclusions only when necessary and after verifying that the security product is causing the problem.

15. Why does Internet work but TallyPrime does not?

Internet access does not guarantee access to local servers. VLANs, Wi-Fi isolation, firewall rules, SMB restrictions, or incorrect addressing may block local communication.

16. Can guest Wi-Fi block TallyPrime?

Yes. Guest networks commonly prevent clients from communicating with internal LAN devices.

17. How can I check whether SMB is reachable?

Use PowerShell:

Test-NetConnection SERVER-IP -Port 445

18. How can I check my mapped network drives?

Run:

net use

19. How can I access the Tally server directly?

Try:

\\SERVERNAME\ShareName

or:

\\SERVER-IP\ShareName

using the actual server and share details.

20. Should the Tally server have a fixed IP?

A stable IP address or DHCP reservation is strongly recommended for servers providing business-critical network services.

21. Can incorrect folder permissions prevent TallyPrime from working?

Yes. Both share permissions and NTFS Security permissions must provide the access required by authorized users.

22. Why can users open the folder but not modify anything?

They may have read-only permissions. Check both share and NTFS permissions.

23. Should Everyone receive Full Control?

Not automatically. Use properly designed user accounts and security groups following least-privilege principles.

24. Can changing the router change Windows Firewall behavior?

Yes. Windows may identify the new connection as a different network and apply a different network profile and firewall policy.

25. Is reinstalling TallyPrime a good first solution?

Usually not for network-access problems. First confirm network connectivity, SMB, permissions, firewall, antivirus, and the Tally data path.

26. Can I repair or rewrite company data to fix network connectivity?

No. Data repair should not be used as a generic fix for networking problems.

27. Is Wi-Fi suitable for TallyPrime?

It can work, but wired Ethernet is generally preferable for critical multi-user accounting environments because of its stability.

28. Can duplicate IP addresses affect TallyPrime?

Yes. Duplicate IPs can cause intermittent connectivity and unpredictable access to the server.

29. What should I check immediately after replacing a router?

Check server IP, DHCP range, subnet, gateway, DNS, network profile, VLANs, Wi-Fi isolation, firewall policies, shared folders, and mapped drives.

30. What should I back up before network troubleshooting?

Maintain a verified backup of Tally company data before significant server, permission, storage, or application changes.

 

Technical Disclaimer

The procedures in this article are provided for educational and general troubleshooting purposes. TallyPrime versions, Windows configurations, firewall policies, antivirus products, server environments, and network architectures can differ significantly.

Always maintain a verified backup of TallyPrime company data before making changes to server storage, folder permissions, security software, firewall rules, networking, or company data.

Do not disable firewalls, antivirus protection, ransomware protection, or other security controls permanently merely to make an application work. Determine the actual requirement and apply the minimum necessary configuration.

For production environments or business-critical accounting data, consult your qualified IT administrator, network administrator, security professional, or authorized Tally support provider before making major changes.

 

#TallyPrime #Tally #TallyPrimeSupport #TallyPrimeTroubleshooting #TallySupport #TallyNetwork #TallyPrimeNetwork #TallyServer #TallyPrimeServer #TallyMultiUser #TallyPrimeMultiUser #NetworkTroubleshooting #WindowsNetworking #WindowsServer #Windows11 #Windows10 #WindowsFirewall #WindowsDefender #DefenderFirewall #Firewall #FirewallConfiguration #Antivirus #EndpointSecurity #NetworkSecurity #SMB #SMBNetworking #TCP445 #FileSharing #WindowsFileSharing #NetworkSharing #FolderPermissions #NTFSPermissions #MappedDrive #NetworkDrive #UNCPath #ServerIP #StaticIP #DHCP #DNS #LAN #BusinessNetwork #ServerTroubleshooting #NetworkAdministrator #SystemAdministrator #ITSupport #ITTroubleshooting #AccountingSoftware #AccountingTechnology #DataSecurity #TallyData