Fix Windows Network Error 0x80070035 When Norton 360 Blocks Shared Folders

Quick Answer

Windows error 0x80070035 — The network path was not found can occur when a Windows computer cannot reach a shared folder on another computer. If one PC has Norton 360 and the other uses Microsoft Defender Antivirus, Norton 360's firewall or network trust settings are a strong possibility when connectivity improves after Norton is disabled. However, the exact cause must be confirmed with targeted tests.

In this scenario, the Norton-protected computer hosts Tally Prime data, the Windows Defender computer can obtain the Tally license over the network, but it cannot open the host's shared folder. The recommended approach is to configure Norton 360 to trust the local network appropriately, check its firewall rules for Windows file sharing, verify TCP port 445, and test access using the host's IP address. Do not permanently disable Norton, enable SMB1, or expose file sharing to public networks.

Understanding the Problem

The two computers may have partially working network connectivity even though Windows file sharing fails. Different network services use different protocols and ports, so successful communication for one application does not prove that SMB file sharing is working.

Before You Begin

1. Sign in to both computers using an account with administrator privileges when required.
2. Identify the computer that stores the Tally Prime company data. In this guide, it is called the Norton host.
3. Identify the computer that needs to access the shared data. It is called the client PC.
4. Record the Norton host's current IPv4 address and computer name.
5. Make sure the Tally data folder is backed up before changing its permissions or configuration.

Step 1: Test Access Using the Norton Host's IP Address

First, determine whether the problem involves computer-name resolution or the underlying SMB connection.

1.1 Find the Norton host's IP address

On the Norton host, open Command Prompt and run:

ipconfig

Locate the active Wi-Fi adapter and note its IPv4 address. For example, the address might be 192.168.1.20. Use the actual address shown on your computer, not this example.

1.2 Open the host by IP address

On the client PC, press Windows + R, enter the following path using the actual host address, and press Enter:

\\192.168.1.20

If the shared folders appear, try opening the required share. If the IP address works but the computer name does not, investigate name resolution and computer-name access rather than changing the Tally folder permissions unnecessarily.

If the IP address also fails, continue with the firewall and SMB connectivity tests.

Step 2: Check Norton 360 Firewall and Network Trust Settings

Norton 360 includes firewall and network protection features that can control inbound and outbound connections. Depending on the installed product version, network trust, traffic rules, and firewall settings may be available in different locations.

2.1 Check the network trust level

1. Open Norton 360 on the Norton host.
2. Open Settings and locate the Firewall or Network settings section. The exact labels vary by version.
3. Look for network trust, network details, or network access settings.
4. Check whether the current home Wi-Fi network is identified correctly and treated as a trusted or private network where the product supports that option.
5. Do not mark an unfamiliar, public, or untrusted Wi-Fi network as trusted merely to make sharing work.

Changing a network trust setting can affect more than one connection. Use the narrowest available setting that permits the required local network communication.

2.2 Inspect firewall traffic rules

1. In Norton 360, open the firewall settings and locate traffic rules or application/network rules, if available.
2. Look for rules affecting Windows system networking, file and printer sharing, SMB, or incoming local network connections.
3. Check for explicit block rules that could override the intended allow behavior.
4. If the installed version supports network-specific rules, allow only the necessary Windows file-sharing traffic from the trusted local subnet or specific client IP address.
5. Retain protection against connections from untrusted networks and the internet.

Do not assume that a rule for Tally Prime or a successful Tally licence connection automatically permits Windows SMB traffic. These are separate services.

Step 3: Perform a Controlled Norton Firewall Test

Because ping reportedly works after Norton is disabled, a controlled test can help establish whether Norton is involved. Disabling the entire security product is not a suitable permanent fix and may reduce protection.

1. Close unnecessary applications and ensure the Wi-Fi network is your trusted home or office network.
2. Use Norton's supported firewall controls to temporarily test the firewall only, if the installed version permits it. Avoid disabling antivirus, web protection, or other security components unnecessarily.
3. Immediately test both the ping response and SMB connectivity from the client PC.
4. Re-enable the firewall immediately after the test, regardless of the result.
5. If SMB access works only while the Norton firewall is disabled, concentrate on Norton's network trust and firewall rules. If SMB still fails, investigate Windows SMB configuration and permissions as well.

If Norton does not provide a safe, clearly scoped temporary test in your version, skip this step and proceed with the port and rule checks. Do not weaken the firewall simply to test a theory.

Step 4: Test SMB Connectivity on TCP Port 445

Windows file sharing using modern SMB commonly uses TCP port 445. Testing this port is more useful for diagnosing shared-folder access than relying on ping alone.

On the client PC, open PowerShell and run the following command, replacing the sample address with the Norton host's actual IPv4 address:

Test-NetConnection -ComputerName 192.168.1.20 -Port 445

This command does not normally require administrator privileges.

A failed test does not, by itself, prove that Norton is blocking the port. The service may be unavailable, another firewall may be filtering traffic, or the network may isolate wireless clients.

Step 5: Check Windows File and Printer Sharing Rules

Microsoft Defender Antivirus and Microsoft Defender Firewall are different components. Having Defender Antivirus installed does not mean every firewall setting is automatically correct. Both computers must permit the required local file-sharing traffic.

5.1 Verify the network profile

1. Open Settings on the Norton host.
2. Go to Network & internet and open the active Wi-Fi connection properties.
3. Confirm that the network profile is set to Private only if this is a trusted network.
4. Repeat on the client PC.

5.2 Enable the required sharing options

1. Open Control Panel.
2. Navigate to Network and Sharing Center.
3. Select Change advanced sharing settings.
4. Under the Private network profile, enable Network discovery and File and printer sharing as appropriate.
5. Save the changes.

Windows interface labels can vary by version. Avoid enabling sharing on the Public profile unless there is a specific, justified requirement.

5.3 Check Microsoft Defender Firewall on the Norton host

Open Windows Security, select Firewall & network protection, and inspect the firewall settings for the active network profile. If Microsoft Defender Firewall is enabled, verify that the built-in File and Printer Sharing inbound rules are enabled for the Private profile where appropriate.

Do not turn off Microsoft Defender Firewall simply because Norton is installed. If both products expose firewall or network protection controls, identify which component is filtering the connection before making changes.

Step 6: Verify SMB Server and Client Configuration

SMB (Server Message Block) is the protocol Windows uses for shared folders and network file access. Modern Windows systems normally use SMB 2 or SMB 3. SMB1 is an older protocol and should not be enabled just to troubleshoot a modern Windows file-sharing problem.

6.1 Check the Server service on the Norton host

Open PowerShell on the Norton host and run:

Get-Service LanmanServer

The Server service should normally be running when the computer hosts Windows file shares. If it is stopped, investigate why before changing the service configuration.

6.2 Check SMB configuration

In PowerShell, run the following commands on the Norton host:

Get-SmbServerConfiguration | Select-Object EnableSMB2Protocol
Get-SmbShare

These commands display the SMB2 protocol setting and the currently configured SMB shares. If the SMB server cmdlets are unavailable, use Windows' built-in management tools and confirm that the required Windows components are installed.

On the client PC, run:

Get-SmbClientConfiguration

Review the output for relevant client configuration. Do not change SMB signing, authentication, or protocol settings indiscriminately. If a specific setting appears to be responsible, verify the requirement for the installed Windows versions and environment before changing it.

6.3 Do not enable SMB1 as a shortcut

Enabling SMB1 can expose systems to security risks and is not a recommended fix for error 0x80070035 when accessing a modern Windows share. First diagnose port 445, firewall rules, SMB2/SMB3 availability, and share permissions.

Step 7: Check Whether the Tally Data Folder Is Actually Shared

Once SMB connectivity is available, verify that the intended Tally Prime data directory has a valid Windows share. A working Tally licence connection does not establish that the data folder itself is shared correctly.

1. On the Norton host, locate the actual Tally Prime data directory used by the installation. Do not assume that the program installation directory is the data directory.
2. Right-click the intended folder, select Properties, and open the Sharing tab.
3. Open Advanced Sharing and check Share this folder.
4. Confirm the share name and the accounts permitted to access it.
5. Open the Security tab and check the NTFS permissions for the intended users or groups.
6. Grant only the permissions needed by the authorized Tally users. Tally may require write access for normal data operations, so read-only access may not be sufficient.

From the client PC, open the share directly using its actual share name:

\\192.168.1.20\TallyData

Here, TallyData is an example share name. Replace it with the actual name configured on the Norton host.

Step 8: Check Credentials and Authentication

If the host is reachable and the share exists but Windows requests credentials or reports an access-denied message, check authentication separately from connectivity.

1. Use an authorized Windows account that exists on the host or is valid for the configured network authentication method.
2. Enter the host's account credentials when prompted. The account may need a password depending on the host's security configuration.
3. Open Control Panel and locate Credential Manager if Windows appears to be using saved credentials for the wrong account.
4. Remove or update only the saved credentials associated with the affected host if they are incorrect.
5. Retry access using the host IP address and the correct account.

Do not disable password-protected sharing or weaken Windows authentication without understanding the security impact. Avoid storing passwords in scripts or sharing them with unauthorized users.

Step 9: Check Wi-Fi Router Client Isolation

Some wireless access points and routers have settings such as AP isolation, client isolation, or wireless device isolation. These features can prevent devices on the same Wi-Fi network from communicating directly.

1. Confirm that both PCs are connected to the intended Wi-Fi network, not separate guest and main networks.
2. Check whether the router uses a guest network for either computer.
3. Review the router or access-point settings for client isolation if SMB access fails even though the local IP addresses appear correct.
4. Disable isolation only when required for a trusted local network and only if you administer the network. Keep guest networks isolated where appropriate.

If the two computers are on different subnets or VLANs, network firewall rules may also need to permit the required SMB traffic between them. Do not expose TCP port 445 to the public internet.

Step 10: Check Computer Name Resolution

If accessing the host by IP address works but accessing it by computer name fails, investigate name resolution.

On the client PC, test the host name:

ping HOSTNAME

Replace HOSTNAME with the actual Windows computer name. A failed ping by name can indicate a name-resolution problem, but a successful ping still does not confirm SMB access.

Use the IP-based share path as a diagnostic step. For a lasting setup, use a stable host address or a reliable local name-resolution method, and ensure that the host's address does not change unexpectedly. Do not manually edit the hosts file unless necessary and documented.

Step 11: Use Windows Network Diagnostics and Logs

If the previous steps do not resolve the problem, inspect the relevant Windows event logs and configuration before making broader changes.

• Windows Defender Firewall: Review firewall rules and available logging for dropped traffic on the affected profile.
• Norton 360: Review firewall alerts, traffic rules, network trust, and available event or connection logs.
• SMB client: Check Event Viewer under Applications and Services Logs for SMB client events where available.
• SMB server: Check the corresponding SMB server logs on the Norton host.

Log names and availability can differ between Windows versions and Norton releases. Use the event details and timestamps to correlate a failed connection with a specific firewall or SMB event.

Do not reset the entire network stack or modify the Windows registry as an initial troubleshooting step. Such changes may disrupt other applications and do not specifically identify the cause of the SMB failure.

Recommended Diagnostic Order for This Scenario

How to Verify the Fix

After making a change, restore all security protections and perform these checks from the client PC:

1. Run Test-NetConnection against the Norton host's IP address on TCP port 445.
2. Open \\HOST-IP in File Explorer.
3. Open the specific Tally data share.
4. Confirm that an authorized user can read and write the files required by Tally Prime.
5. Open Tally Prime and verify that the client can access the intended company data using the supported multi-user configuration.
6. Confirm that the Norton firewall and Windows Firewall remain enabled with appropriate protections.

Do not test by editing, moving, or deleting live company data. Use an approved test procedure or a backed-up test dataset where possible. If file sharing works but Tally cannot open the company data, investigate the Tally Prime data path, multi-user configuration, and application-specific requirements separately.

Recovery and Rollback

If a firewall or sharing change causes unexpected problems:

• Undo the specific rule or setting you changed, or restore its previous value.
• Remove any temporary firewall exception created solely for testing.
• Ensure the firewall and other Norton protection features are enabled.
• Return network discovery and sharing to their previous state if the network is not trusted.
• Restore any altered folder permissions to the documented intended configuration.

If you cannot determine which rule is safe to change, collect the host and client IP addresses, Windows versions, Norton version, TCP port 445 test result, and relevant firewall logs before contacting Norton or Microsoft support.

Frequently Asked Questions

Why can Tally obtain its licence when Windows file sharing fails?

The licence connection and Windows SMB file sharing may use different network services, ports, and firewall rules. Successful licence communication does not prove that TCP port 445 or the shared data folder is accessible.

Does error 0x80070035 always mean Norton is blocking the connection?

No. Norton firewall settings are a reasonable suspect when disabling Norton changes connectivity, but the error can also result from name-resolution problems, unavailable SMB services, another firewall, network isolation, or an incorrect share path.

Why does ping work in only one direction?

Firewalls can filter ICMP echo requests differently by direction or network profile. Ping is a diagnostic for ICMP reachability, not a test of SMB access. Test TCP port 445 separately.

Should SMB1 be enabled to fix error 0x80070035?

Not as a routine troubleshooting step. Modern Windows file sharing normally uses SMB2 or SMB3. SMB1 is an older protocol with security disadvantages and should not be enabled without a verified legacy compatibility requirement and a controlled security assessment.

Should I disable Microsoft Defender Firewall because Norton is installed?

No. Determine which firewall or network protection component is blocking the connection. Keep appropriate firewall protections enabled and make only the narrowly scoped changes required for authorized local file sharing.

Can I share the entire Tally installation folder?

Share only the actual data folder or other location required by your supported Tally Prime configuration. Program files and company data are different, and the required paths depend on the installation and deployment.

Is it safe to open TCP port 445 on the router?

No public internet exposure is required for ordinary local Windows file sharing. Do not forward TCP port 445 from the internet to the Tally host. Permit SMB only on the trusted internal network as required.

What should I do if TCP port 445 is reachable but the folder still will not open?

Check the exact share name, SMB server status, authentication, saved credentials, share permissions, and NTFS permissions. A reachable port confirms only that a TCP connection can be established; it does not guarantee authorization to the folder.

Conclusion

For a Windows computer hosting Tally Prime data with Norton 360 installed, the first priority is to determine whether the Norton firewall is blocking SMB traffic or whether another Windows sharing configuration is responsible. Test access by IP address, verify TCP port 445, review Norton's network trust and firewall rules, and then check the Windows sharing service, share configuration, and permissions.

Keep the security software enabled, avoid enabling SMB1, and restrict file-sharing access to authorized computers and users. This approach helps isolate the actual cause while protecting the Tally Prime data stored on the host.

Sources

• Microsoft Support — File sharing over a network in Windows
• Microsoft Learn — Troubleshoot SMB
• Microsoft Learn — Secure SMB traffic in Windows
• Microsoft Learn — Test-NetConnection PowerShell command
• Norton Support — Norton 360 firewall and network protection assistance
• Tally Solutions Help — Tally Prime configuration and support documentation