Troubleshooting "Network path not found error code 35/53" in the GPO Settings Changes report

Troubleshooting "Network path not found error code 35/53" in the GPO Settings Changes report

In this article  :

  • Issue description

  • Prerequisites

  • Possible cause

  • Resolution

  • Related topics and articles

  • How to reach support

Issue description

Learn how to resolve the “Network path not found error code 35/53" encountered when accessing the GPO Settings Changes report in ADAudit Plus, typically caused by an inaccessible SYSVOL share on the primary domain controller (PDC).

Prerequisites  

  • You must have administrative privileges on the ADAudit Plus server.

  • Gather the DC’s flat name and fully qualified domain name (FQDN).

  • Ensure you have the necessary permissions to modify network and DNS settings if required.

  • Verify that the following ports are open and accessible: 135 and 49152–65535.

 Possible cause 

  • The PDC is unreachable from the ADAudit Plus server due to network connectivity or DNS name resolution issues.

  • The SYSVOL share on the PDC is not accessible from the ADAudit Plus server.

  • Required network ports, such as TCP 135 (RPC Endpoint Mapper) and the high-range dynamic RPC ports, are blocked by a firewall.

Resolution  

Ping the PDC

  1. Open Command Prompt on the ADAudit Plus server.

  2. Ping the PDC using both its flat name and FQDN to verify name resolution and connectivity.

Test SYSVOL share access  

  1. Open File Explorer on the ADAudit Plus server.

  2. Navigate to the SYSVOL share using both of the following paths:

    • \\<PDC_Name>\sysvol

    • \\<PDC_FQDN>\sysvol

  1. If access fails, proceed to the next step.

Append DNS suffix  

  1. Open Control Panel > Network and Internet > Network and Sharing Center.

  2. Select your active adapter > Properties > Internet Protocol Version 4 (TCP/IPv4) > Properties > Advanced > DNS tab.

  3. Under DNS suffix for this connection, add the appropriate domain suffix.

  4. Alternatively, add a host record in the DNS server mapping the flat name to the IP address of the PDC.

Check port access  

  1. Ensure that TCP port 135 and dynamic RPC ports 49152–65535 are open from the ADAudit Plus server to the DC.

  2. Use the following PowerShell command to test connectivity:

  3. test-netconnection <PDC_IP> -port 135

  4. Repeat the test for a few random ports in the 49152–65535 range.

Enable agent-based GPO watcher  

  1. Log in to the ADAudit Plus web console.

  2. Navigate to Admin > Configuration > GPO Settings Changes.

  3. Enable the Watch via agent option.

  4. Click Save to apply the changes.

Related topics and articles  

How to reach support  

If the issue persists after performing these steps, contact support@adauditplus.com.

                  New to ADSelfService Plus?