The Connectivity Test helps you troubleshoot connectivity issues when accessing remote event logs.
To start the test, select the required computer in the tree, right-click it, and choose Connectivity Test from the context menu.
A list of diagnostic steps will appear, each with a checkmark indicating success.
If all steps are marked with a checkmark, the connection is functioning correctly.
If any step fails, refer to the table below for common causes and resolutions.
Failed Step
Possible Cause
Resolution
RPC port available
• No network connectivity between local and remote computer
• RPC port 135 is blocked on the remote computer
• Connection to port 135 is blocked by the local firewall
• RPC or RPC Endpoint Mapper services are not running on the remote computer
• Verify network connectivity between local and remote computer
• Ensure that the firewall on the remote computer allows inbound TCP 135
• Ensure that the firewall on the local computer allows outbound TCP 135
• On the remote computer, verify that Remote Procedure Call (RPC) and RPC Endpoint Mapper services are running
• On the remote computer, confirm that port 135 is listening
RPC service responded
• Port 135 is open, but RPC does not respond correctly
• Third-party firewall or security software interferes with RPC traffic
• RPC service on the remote computer is malfunctioning
• Check third-party firewall or security software on both local and remote computers
• Ensure that the RpcSs service is running properly (sc query RpcSs)
• Confirm that port 135 is in LISTENING state and associated with RpcSs (netstat -ab)
Event Log dynamic port resolved
• Windows Event Log service is not running on the remote computer
• On the remote computer, ensure that the Windows Event Log service is running and not disabled (sc query eventlog)
Event Log dynamic port available
• RPC dynamic ports are blocked by firewall
• Inbound rule Remote Event Log Management (RPC) is disabled on the remote computer
• Local firewall blocks outbound connections to RPC dynamic ports
• Enable the inbound rule Remote Event Log Management (RPC) on the remote computer
• Ensure that firewalls on both computers allow connections to the dynamic port range (commonly 49152–65535; check with netsh int ipv4 show dynamicport tcp)
• Ensure that the local firewall allows outbound connections to the dynamic ports
Event Log service responded
• Dynamic port is available, but Windows Event Log service does not respond correctly
• Third-party firewall or security software interferes with RPC traffic
• Windows Event Log service is malfunctioning or incompatible
• Check third-party firewall or security software on both computers
• Ensure that the remote computer runs a Windows version compatible with Event Log Explorer
