In this article:  

• Issue description

• Prerequisites

• Possible causes

• Resolution

• Related topics and articles

• How to reach support

Issue description  

The message "Error Code 1726: The remote procedure call failed" occurs when ADAudit Plus is unable to fetch event logs from a monitored server. This is often due to high network latency, connectivity interruptions, or blocked RPC communication between the ADAudit Plus server and the destination server.

Prerequisites  

• The target server must be reachable over the network.

• Admin rights to configure firewall rules and test connectivity.

• RPC-related ports are not blocked between ADAudit Plus and the destination machine.

Possible causes  

• High network latency or traffic congestion between ADAudit Plus and the monitored server.

• Connection routed through WAN, VPN, or across geographically distant sites.

• RPC Port 135 or the dynamic RPC port range (49152–65535) is blocked by firewalls.

• Firewall rules required for Remote Event Log Management are not enabled on the target server.

Resolution  

Resolution 1: Verify network connection and install the agent   (NOTE: recommended for remote or high-latency environments)

• Check if the monitored server is located on a different site, WAN, or VPN segment.

• If the server is not in the same LAN, install the ADAudit Plus agent on the destination server to improve reliability and avoid RPC dependency.

Resolution 2: Verify RPC and dynamic port availability  

• Ensure the following ports are open between ADAudit Plus and the target server:

• TCP 135 

• TCP 49152–65535 

• You can test this using tools like telnet or PortQry.

Resolution 3: Update firewall rules to allow RPC traffic  

On the monitored server, enable the following Windows Firewall inbound rules:

• Remote Event Log Management (NP-In)

• Remote Event Log Management (RPC)

• Remote Event Log Management (RPC-EPMAP)

To verify connectivity:

1. Open Run, type eventvwr.exe, and press Enter.

2. Click Action > Connect to Another Computer.

3. Enter the name of the target server and attempt to view its logs.

If the connection fails, revisit the firewall and port configurations.

Related topics and articles  

• Ports required by ADAudit Plus

How to reach support  

If the issue persists after following the steps above, please contact our support team with log details for further investigation:

📧 support@adauditplus.com