In a multi-user TallyPrime environment, company data is often stored on a central server, shared Windows folder, dedicated file server, or Network Attached Storage (NAS). Multiple computers then access the same company data over the local network.

A common problem occurs when:

• TallyPrime company data does not open from a network drive.
• Company data does not open when stored on a NAS.
• Company opens normally on the server but not on client computers.
• Company folder is visible from the client, but TallyPrime does not display the company.
• TallyPrime shows an error while loading company data.
• Mapped network drive is accessible in Windows but unavailable inside TallyPrime.
• One client can access the company while another cannot.

These symptoms do not automatically mean that the TallyPrime company data is corrupted.

When the same company opens correctly on the server, the problem is often related to network connectivity, permissions, mapped drives, SMB/file sharing, Windows credentials, firewall configuration, TallyPrime configuration, or NAS compatibility.

This article provides a systematic troubleshooting procedure.

1. Understand the Typical Network Setup

A typical TallyPrime multi-computer environment may look like:

Server / NAS

Stores the company data:

D:\TallyData

The folder may be shared as:

\\SERVER\TallyData

Client computers access it through either:

\\SERVER\TallyData

or a mapped network drive such as:

T:\

TallyPrime on each client must be able to reach the company data location with appropriate read/write permissions.

2. First Determine Whether It Is a Data Problem or Network Problem

This is the most important initial test.

Go directly to the server where the company data is stored.

Open TallyPrime and try opening the affected company locally.

If the company opens correctly on the server

The data itself is probably accessible locally, and investigation should concentrate on:

• Network connectivity
• Shared-folder permissions
• NTFS permissions
• NAS permissions
• SMB connectivity
• Windows credentials
• Client configuration
• TallyPrime data path
• Firewall/security software
• Mapped network drive
• Network stability

If the company also fails to open on the server

The issue may instead involve:

• Company data corruption
• Damaged TallyPrime data files
• Incorrect company folder
• Storage/disk problems
• Incomplete backup restoration
• TallyPrime version incompatibility

In this situation, troubleshoot the company data before concentrating on client network access.

3. Verify Basic Network Connectivity

From the client computer, check whether the server is reachable.

Open Command Prompt and run:

ping SERVERNAME

You can also test using the server IP:

ping 192.168.1.10

Replace the example IP with the actual server IP.

If the IP address responds but the server name does not, you may have a DNS or name-resolution problem.

Try opening:

\\192.168.1.10\TallyData

instead of:

\\SERVER\TallyData

If access works through the IP address but not the hostname, investigate:

• DNS configuration
• Windows name resolution
• Server hostname
• Local DNS server
• Network profile
• Cached DNS records

You can also try:

ipconfig /flushdns

and test again.

4. Test the Shared Folder Outside TallyPrime

Before changing TallyPrime settings, verify that Windows itself can access the company folder.

Press:

Windows + R

Enter:

\\SERVER\TallyData

or:

\\192.168.1.10\TallyData

The folder should open immediately.

Navigate to the TallyPrime company folder.

If Windows cannot open the folder reliably, TallyPrime will not be able to use it reliably either.

5. Perform a Read/Write Test

Simply being able to view the folder is not sufficient.

TallyPrime may need to create, modify, lock, and update files while the company is being used.

From the client PC:

1. Open the shared Tally data folder.
2. Create a new text file.
3. Rename the file.
4. Open and modify it.
5. Save it.
6. Delete it.

For example, create:

NetworkTest.txt

If you can view existing files but cannot create, modify, rename, or delete the test file, investigate permissions.

6. Check Windows Share Permissions

On a Windows server, there can be two permission layers:

Share Permissions

These control access through the network share.

NTFS Security Permissions

These control access to the underlying Windows folder.

A user may therefore have sufficient share permissions but insufficient NTFS permissions, or vice versa.

Right-click the Tally data folder on the server and check:

Properties → Sharing

and:

Properties → Security

Verify that the appropriate Tally users have the permissions required for normal operation.

Avoid randomly granting unrestricted permissions to Everyone merely to make the problem disappear. Permissions should follow your organization's security policy.

7. Check NAS User Permissions

NAS devices generally maintain their own user and shared-folder permission systems.

Depending on the NAS, check:

• User account
• User group
• Shared-folder permissions
• Read/write access
• SMB permissions
• Access Control Lists
• Guest access settings
• File locking
• Security policies

A user may be able to browse the NAS but still lack sufficient permission to modify TallyPrime company files.

8. Avoid Guest Access for Business Data

Guest access may appear convenient but can create security and permission problems.

Prefer authenticated access using:

• Dedicated NAS user
• Windows/domain account
• Appropriate group permissions

For example:

TallyUsers

could be a group containing authorized accounting users.

Assign the required permissions to that group rather than configuring every user independently.

9. Check Saved Windows Credentials

A client PC may be connecting to the server using outdated or incorrect credentials.

Open:

Control Panel → Credential Manager → Windows Credentials

Look for credentials associated with:

• Server hostname
• Server IP address
• NAS hostname
• NAS IP address

Remove incorrect credentials if appropriate and reconnect using the correct account.

You can also inspect network connections from Command Prompt:

net use

Disconnecting and reconnecting the relevant network share can sometimes resolve stale authentication sessions.

10. Check the TallyPrime Data Path

A very common problem is an incorrect data path.

For example, the server may use:

D:\TallyData

But a client cannot normally use that server-local path directly.

The client should use the shared network path, such as:

\\SERVER\TallyData

or a correctly mapped network drive.

Verify the data location configured in TallyPrime and make sure the client is pointing to the actual shared company-data directory.

11. Prefer UNC Path for Troubleshooting

A mapped network drive might be:

T:\TallyData

The equivalent UNC path could be:

\\SERVER\TallyData

When troubleshooting, try the UNC path directly.

This helps determine whether the problem is specifically related to drive mapping.

For example:

Problematic

T:\

Test

\\SERVER\TallyData

If the UNC path works but the mapped drive does not, investigate the mapped-drive configuration rather than the Tally data.

12. Mapped Drive Visible in Explorer but Not TallyPrime

This can happen because of differences in the Windows security context.

For example:

• Explorer is running normally.
• TallyPrime is running as Administrator.
• The mapped drive was created under the standard user session.

The elevated application may not see the same mapped network drive.

This creates a confusing situation where:

Windows Explorer sees T:

but:

TallyPrime does not see T:

Test

Instead of using:

T:\TallyData

try:

\\SERVER\TallyData

If the UNC path works, the issue is likely associated with the mapped drive/elevation context.

13. Check Whether TallyPrime Is Running as Administrator

Right-click the TallyPrime shortcut and inspect:

Properties → Compatibility

Check whether:

Run this program as an administrator

is enabled.

If TallyPrime unnecessarily runs elevated while the mapped network drive belongs to the normal user context, network drive visibility may differ.

Do not change administrator requirements blindly in a production environment. Test carefully and understand why elevation was configured.

14. Recreate the Mapped Network Drive

If you use a mapped drive, disconnect and recreate it.

Example:

T: → \\SERVER\TallyData

Enable:

Reconnect at sign-in

when appropriate.

After reconnecting, verify that the drive opens normally before starting TallyPrime.

15. Check Whether the Network Drive Is Actually Connected

Windows can display a mapped drive even when the connection is unavailable.

Before opening TallyPrime:

1. Open File Explorer.
2. Open the mapped drive.
3. Browse the company directory.
4. Confirm files appear normally.

If Windows takes a long time to open the drive, repeatedly asks for credentials, or reports that the location is unavailable, resolve the network problem first.

16. Check SMB/File Sharing Configuration

Windows servers and most NAS systems use SMB for file sharing.

Problems can occur because of:

• SMB configuration
• Disabled file sharing
• NAS protocol configuration
• Authentication restrictions
• Firewall rules
• Old NAS firmware
• Security policy changes
• Windows updates

Avoid enabling obsolete SMB protocols merely as a quick workaround.

If a NAS requires an outdated SMB version, check whether the NAS firmware or configuration can be upgraded instead.

17. Check Network Discovery and File Sharing

On Windows systems, verify the appropriate network configuration.

Go to:

Settings / Control Panel → Network and Sharing settings

Depending on your Windows version and environment, verify:

• Network Discovery
• File and Printer Sharing
• Appropriate network profile

A business LAN would normally be configured according to the organization's security requirements rather than using overly permissive sharing settings.

18. Check Windows Firewall

Temporarily testing firewall behavior can help identify blocked file-sharing traffic.

Check firewall configuration on:

• Server
• Client
• NAS, if applicable
• Endpoint security software

Relevant Windows file-sharing rules must be enabled according to your network design.

Do not permanently disable Windows Firewall as a solution.

Instead, identify the required rule and configure it properly.

19. Check Antivirus or Endpoint Security

Security software may interfere with network files or application access.

Possible examples include:

• Antivirus real-time scanning
• Ransomware protection
• Controlled folder access
• Endpoint Detection and Response
• Network protection
• File locking
• NAS security software

Do not permanently disable security protection.

If testing confirms interference, configure a carefully scoped exclusion only after evaluating the security implications.

20. Check TallyPrime Version on Server and Clients

All computers participating in the same Tally environment should use an appropriate compatible TallyPrime release.

Check:

Help → About

Compare the TallyPrime release/build on:

• Server
• Client 1
• Client 2
• Other systems accessing the company

If one client uses a substantially different release, update or standardize the installation as appropriate.

Always maintain a verified backup before performing upgrades involving important company data.

21. Test Another Client Computer

This is an excellent isolation test.

Suppose:

• Server → Company opens
• Client A → Company does not open
• Client B → Company opens

The problem is probably specific to Client A.

Investigate Client A for:

• Windows credentials
• Firewall
• Antivirus
• TallyPrime installation
• Mapped drive
• Network configuration
• User permissions
• DNS/name resolution

If all clients fail but the server works locally, investigate the server share, permissions, firewall, or network infrastructure.

22. Test with Server IP Instead of Hostname

Suppose this fails:

\\ACCOUNTSSERVER\TallyData

but this works:

\\192.168.1.10\TallyData

This strongly suggests a name-resolution problem rather than TallyPrime company corruption.

Check:

ping ACCOUNTSSERVER

and:

nslookup ACCOUNTSSERVER

where appropriate.

23. Check Wi-Fi Versus LAN

TallyPrime company data involves ongoing file access.

A weak or unstable Wi-Fi connection can cause:

• Slow company opening
• Intermittent errors
• Temporary disconnection
• File-access failures
• Session interruptions

For business-critical accounting data, a stable wired LAN is generally preferable where practical.

If the problem occurs on Wi-Fi, test the same client temporarily using Ethernet.

If the problem disappears, investigate:

• Wi-Fi signal quality
• Access point
• Network congestion
• Roaming
• Packet loss
• Power saving
• Wireless adapter driver

24. Check for Packet Loss

A network can appear connected while still losing packets.

Run:

ping SERVERNAME -t

or:

ping 192.168.1.10 -t

Watch for:

• Request timed out
• Large latency spikes
• Frequent packet loss

Stop the continuous test using:

Ctrl + C

A stable local network should not repeatedly lose connectivity to the file server.

25. Test Network Copy Performance

Copy a reasonably large test file between the client and server.

Observe whether:

• Transfer speed is stable
• Transfer stops unexpectedly
• Explorer freezes
• Network disconnects
• Errors appear

If normal Windows file transfers are unstable, the TallyPrime issue may simply be a symptom of the underlying network problem.

26. Check Network Adapter

On the affected client:

Device Manager → Network adapters

Check for:

• Driver problems
• Warning icons
• Outdated drivers
• Power-management settings

You can also test:

ipconfig /all

Verify:

• IP address
• Subnet mask
• Default gateway
• DNS servers

27. Check Server Network Adapter

If several clients experience the same problem, inspect the server-side network connection.

Check:

• NIC driver
• Ethernet cable
• Switch port
• Link speed
• Packet errors
• Power-saving configuration
• Server resource utilization

A server opening TallyPrime locally does not prove that its network connection is healthy.

28. Check Switch and Cabling

Intermittent TallyPrime access may sometimes be caused by physical network problems.

Check:

• Ethernet cable
• RJ45 connector
• Network switch
• Switch port
• Patch panel
• NIC port

Move the affected computer to a known-good switch port or cable as a diagnostic test.

29. Check NAS Health

If company data resides on a NAS, examine its health dashboard.

Check:

• Disk/RAID health
• Storage pool status
• Volume status
• Available free space
• SMART warnings
• CPU utilization
• Memory utilization
• Network interface
• System logs
• SMB service logs

A NAS may remain accessible even while experiencing disk, RAID, network, or filesystem problems.

30. Check NAS Free Space

Insufficient storage can cause application problems.

Verify that the NAS volume has sufficient free space for:

• Company data growth
• Temporary operations
• Snapshots
• Backups
• NAS filesystem requirements

Do not operate critical accounting data on a nearly full storage volume.

31. Check NAS Sleep or Hibernation

Some NAS devices or external storage systems use aggressive disk sleep settings.

This can result in:

• Delayed access
• Temporary timeout
• Slow company opening

Review NAS power-management settings if users consistently experience problems after periods of inactivity.

32. Avoid Access Through Internet-Mapped Storage

Do not assume that every network-like storage service is suitable for live TallyPrime company data.

Examples requiring special caution include:

• Cloud-synchronized folders
• Internet-mounted drives
• Consumer sync applications
• Remote NAS accessed over unstable WAN links
• Offline synchronization systems

Live accounting databases should be hosted only on storage and network architectures supported for the application's workload.

Synchronization is not the same thing as safe multi-user database access.

33. Do Not Put Active Company Data Inside Ordinary Sync Folders Without Verification

Be cautious with services that continuously synchronize files while TallyPrime is modifying them.

Possible risks include:

• File conflicts
• Partial synchronization
• Multiple versions
• File locking issues
• Data inconsistency

Cloud storage can be excellent for backup copies, but that does not automatically make a sync folder suitable for live multi-user company data.

34. Check Folder Structure After Copying Data

If Tally data was recently moved from a server to NAS, verify that the complete company folder was copied.

Do not manually select only files that appear important.

Preserve the complete folder structure.

Also verify that:

• Copy completed without errors
• Files were not skipped
• Permissions did not change unexpectedly
• Source and destination sizes are reasonable
• Backup is available

35. Avoid Opening the Same Copied Company from Multiple Locations

Administrators sometimes accidentally maintain:

D:\TallyData

and:

\\NAS\TallyData

with separate copies of the same company.

Some users may then enter transactions into one copy while others use another.

This can create a serious business problem because each copy may contain different transactions.

Maintain a clearly defined single production data location.

36. Test Locally on the Client

For diagnostic purposes only, take a backup/copy of the affected company while users are out of it and place the diagnostic copy on the client PC.

Try opening that separate copy locally.

If the copied company opens locally but not from the network location, the problem strongly points toward network/storage access rather than basic company readability.

Do not allow users to enter live transactions into the diagnostic copy.

37. Check Whether the Problem Affects One Company or All Companies

This distinction is important.

Only one company fails

Possible causes:

• Specific company data issue
• Company folder permissions
• Incomplete copy
• Damaged files
• Company-specific problem

All companies fail from the client

Possible causes:

• Network path
• Shared-folder permissions
• NAS access
• TallyPrime configuration
• Firewall
• Client computer issue

38. Check Access with Another Windows User

Sign in to the affected client with another authorized Windows account.

Test the network location and TallyPrime.

If the second account works, investigate:

• User profile
• Credentials
• Mapped drives
• Permissions
• Per-user Tally settings

39. Check Date and Time

Incorrect system time can sometimes cause authentication and domain-related issues.

Verify the date, time, and timezone on:

• Server
• Client
• NAS
• Domain controller, if applicable

Systems in a domain environment should have properly synchronized clocks.

40. Restart the Correct Components

Instead of immediately restarting everything, restart systematically when appropriate:

1. Close TallyPrime on affected clients.
2. Confirm no critical operation is running.
3. Reconnect the network share.
4. Restart the affected client if necessary.
5. Restart relevant services only when appropriate.
6. Reboot the server/NAS only during a safe maintenance window if required.

Never restart a production server or NAS while users are actively working without considering the risk of data loss.

41. Server Opens Company but Client Cannot – Recommended Diagnostic Sequence

When TallyPrime opens correctly on the server but not on a client, follow this order:

1. Confirm company opens locally on server.
2. Confirm client can ping server.
3. Open server share from client.
4. Test read/write/delete permissions.
5. Try UNC path.
6. Try server IP address.
7. Verify Windows credentials.
8. Verify share permissions.
9. Verify NTFS permissions.
10. Verify NAS permissions if applicable.
11. Check TallyPrime data path.
12. Check mapped drive status.
13. Check Administrator/elevation mismatch.
14. Check firewall.
15. Check endpoint security.
16. Compare TallyPrime versions.
17. Test another client.
18. Test Ethernet instead of Wi-Fi.
19. Check packet loss.
20. Check server/NAS health.

This sequence helps avoid unnecessary data-repair attempts.

42. NAS-Specific Troubleshooting Checklist

When TallyPrime data is stored on NAS, check:

• NAS is reachable
• SMB service is running
• NAS firmware is current and supported
• Shared folder is online
• User has read/write permissions
• No disk or RAID warning exists
• Sufficient free storage exists
• NAS network link is stable
• Client authentication is working
• File locking behaves correctly
• No excessive snapshots or storage errors
• No antivirus process is excessively locking files
• No synchronization application is interfering
• Network latency is acceptable
• NAS configuration is appropriate for live TallyPrime usage

Also verify current Tally documentation and your NAS vendor's recommendations before using NAS storage as the primary live multi-user data location.

43. What Not to Do

Avoid these actions during troubleshooting:

• Do not format the server/NAS storage.
• Do not delete company files randomly.
• Do not rename internal company files without understanding their purpose.
• Do not run disk repair tools blindly.
• Do not overwrite the only working copy.
• Do not disable antivirus permanently.
• Do not disable the firewall permanently.
• Do not grant unrestricted permissions unnecessarily.
• Do not enable obsolete SMB protocols without understanding the security risk.
• Do not move live data while users are working.
• Do not restore an old backup over current production data without verification.
• Do not assume every failure is data corruption.

44. Backup Before Major Troubleshooting

Before making significant changes, maintain a verified backup of the TallyPrime data.

Prefer multiple backup layers:

Primary Data → Local Backup → Separate Storage/NAS Backup → Off-site/Cloud Backup

Where appropriate, maintain versioned backups so an older known-good state can be recovered.

A backup is valuable only when it can actually be restored, so periodic restore testing is recommended.

45. Quick Troubleshooting Table

Symptom	Likely Area to Check
Opens on server, not client	Network/permissions/path
Share not opening	Network/SMB/firewall
Folder opens but cannot create file	Permissions
IP works but hostname fails	DNS/name resolution
UNC works but mapped drive fails	Drive mapping/elevation
One client fails	Client configuration
All clients fail	Server/share/network
NAS folder accessible but Tally fails	Permissions/locking/configuration
Company very slow	Network/NAS performance
Random disconnection	LAN/Wi-Fi/NIC/switch
Only one company fails	Company-specific data/folder issue
All companies fail	Network or Tally configuration
Problem after moving data	Path/permissions/incomplete copy

46. Useful Windows Commands

Check IP Configuration

ipconfig /all

Test Server

ping SERVERNAME

Continuous Connectivity Test

ping SERVERNAME -t

Test by IP

ping 192.168.1.10

Clear DNS Cache

ipconfig /flushdns

View Network Connections

net use

Test Name Resolution

nslookup SERVERNAME

These commands are diagnostic tools and should be interpreted together rather than relying on one result alone.

47. Recommended Network Architecture

For a small office environment:

Client PCs → Gigabit Ethernet Switch → Windows Server/File Server → TallyPrime Data

Where NAS is used:

Client PCs → Managed/Gigabit Switch → NAS → Dedicated Shared Folder

Recommended practices include:

• Reliable wired LAN
• Gigabit or faster infrastructure where appropriate
• Quality switches
• Good Ethernet cabling
• UPS protection
• Regular NAS/server backups
• Restricted user permissions
• Monitoring of disk health
• Consistent TallyPrime versions
• Stable server naming/IP design
• Tested disaster-recovery procedure

48. Important Observation

If the company opens perfectly on the server but fails on the client, do not immediately conclude that the company data is corrupted.

First prove whether the client has stable read/write access to exactly the same company folder.

A simple Windows file test can reveal a great deal:

Open → Create → Modify → Rename → Delete

If any of these operations fail, resolve the underlying network or permission issue before attempting TallyPrime data repair.

Frequently Asked Questions (FAQ)

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

The most common reasons are incorrect data path, network permissions, mapped-drive problems, Windows credentials, SMB/file-sharing issues, firewall restrictions, or client-specific configuration.

2. Does this mean my TallyPrime company is corrupted?

Not necessarily. If the same company opens correctly on the server, investigate network access first.

3. Can TallyPrime data be accessed through a network share?

TallyPrime is commonly used in networked environments, but the exact deployment should follow the licensing, product, and data-access recommendations applicable to your TallyPrime edition and release.

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

Both may work depending on configuration, but UNC paths such as \\SERVER\TallyData are particularly useful for troubleshooting mapped-drive problems.

5. Why can Windows Explorer see my mapped drive but TallyPrime cannot?

This can happen when TallyPrime runs under a different security/elevation context, such as Run as Administrator, from the one in which the drive was mapped.

6. Can TallyPrime data be stored on a NAS?

A NAS may provide SMB network storage, but suitability depends on the NAS, configuration, locking behavior, performance, TallyPrime requirements, and vendor support. Verify compatibility before using NAS as the primary live data store.

7. Why does the company take a long time to open from NAS?

Possible reasons include slow disks, overloaded NAS, network latency, weak Wi-Fi, SMB issues, antivirus scanning, RAID problems, insufficient NAS resources, or network congestion.

8. Why does the company work with the server IP but not server name?

This usually indicates a hostname/DNS/name-resolution problem.

9. Why does TallyPrime work on one client but not another?

The failing client may have different credentials, permissions, firewall settings, TallyPrime configuration, network adapter problems, or mapped-drive settings.

10. Should I disable Windows Firewall?

No. You may temporarily test under controlled conditions, but the permanent solution should be correct firewall rules rather than disabling protection.

11. Should I disable antivirus?

Not permanently. Determine whether security software is actually causing the problem before configuring any exclusion.

12. Can Wi-Fi cause TallyPrime network problems?

Yes. Weak signals, roaming, packet loss, or intermittent Wi-Fi can affect applications that continuously access files over a network.

13. Is Ethernet better for TallyPrime clients?

For fixed office systems accessing live company data over the LAN, wired Ethernet generally provides more consistent connectivity than Wi-Fi.

14. Why can I see Tally data files but cannot open the company?

Being able to read a directory does not prove that the account has sufficient permissions to create or modify files.

15. How can I test network permissions?

Create a test text file in the shared folder, modify it, rename it, and delete it. Failure at any stage indicates that permissions or access need investigation.

16. What should I check on NAS?

Check SMB configuration, users, groups, permissions, storage health, RAID status, free space, network connectivity, logs, firmware, and file-locking behavior.

17. Should all computers use the same TallyPrime version?

Keeping systems on an appropriate consistent/compatible release reduces compatibility and troubleshooting issues.

18. Can a Windows Update cause network access problems?

Updates can occasionally expose configuration, driver, security, or SMB compatibility issues. Troubleshoot the exact failure rather than immediately rolling back security updates.

19. Should I copy the company locally to test?

A separate backup/copy can be used for diagnosis. Do not allow users to enter production transactions into the diagnostic copy.

20. What if the company does not open even locally?

Then investigate the company data, storage health, TallyPrime release, and possible corruption rather than treating the issue only as a network problem.

Conclusion

When TallyPrime company data does not open from a network drive or NAS but opens correctly on the server, troubleshooting should begin with the network path and access permissions rather than immediately attempting company-data repair.

The most useful diagnostic sequence is:

Server Test → Network Connectivity → Shared Folder → Read/Write Test → UNC Path → Permissions → Credentials → SMB → Firewall → TallyPrime Configuration → NAS/Server Health

Systematic isolation helps determine whether the actual cause is TallyPrime, Windows, the client PC, the network, the file server, or the NAS.

Disclaimer

This article is provided for technical information and educational purposes only. Network configuration, permissions, TallyPrime releases, licensing requirements, Windows security policies, and NAS behavior may vary between environments.

Always maintain a verified backup before changing company data, server permissions, storage configuration, SMB settings, or TallyPrime configuration. For business-critical data or suspected corruption, consult your authorized Tally service provider, qualified IT administrator, storage/NAS vendor, or Tally support documentation before proceeding.

 

#TallyPrime #Tally #TallySupport #TallyPrimeSupport #TallyTroubleshooting #TallyPrimeTroubleshooting #TallyData #TallyPrimeData #TallyCompany #TallyNetwork #TallyPrimeNetwork #TallyServer #TallyPrimeServer #TallyClient #TallyPrimeClient #TallyNAS #NAS #NetworkDrive #MappedDrive #UNCPath #NetworkShare #FileServer #WindowsServer #WindowsNetwork #SMB #NetworkTroubleshooting #NetworkPermissions #FolderPermissions #SharePermissions #NTFSPermissions #NetworkSecurity #NetworkConnectivity #LAN #BusinessNetwork #AccountingSoftware #AccountingTechnology #ITSupport #TechnicalSupport #WindowsSupport #ServerSupport #NASStorage #DataBackup #DataRecovery #DataSecurity #CompanyData #TallyDataBackup #TallyDataRecovery #TallyError #TallySolution #KnowledgeBase