Submit a ticketCall us

AnnouncementsWeb Help Desk Integrations eCourse

Looking to reduce response times? Sign up for our eCourse to learn how integrating Web Help Desk with Dameware Remote Support, Network Configuration Manager, Network Performance Monitor, and Server & Application Monitor can improve communication efficiencies.

Register here.

Home > Success Center > Network Performance Monitor (NPM) > NetPath Timeout Hops: No Response. The device at these hops did not respond to repeated access attempts

NetPath Timeout Hops: No Response. The device at these hops did not respond to repeated access attempts

Updated June 23, 2017

Overview

NetPath hops time out and the following is displayed in the NetPath view:

Timeout Hops

No Response. The device at these hops did not respond to repeated access attempts. This may be because it is blocking access.

orion.png

Environment

  • NPM 12.0
  • NetPath 1.0
  • NIC teaming (dual-homed)

Cause 

This issue can occur because of the following reasons:

  • There is a high TTL value for ICMP type 11 packets.
  • There is a security device between the endpoint and the Orion server.

Resolution

Note: The following procedure disables the content based on the captured filter (for example, icmp[0] == 11), which may alter the memory consumption for the NetPath probe.

 

A fix is expected in an upcoming release or hotfix. As a workaround, perform the following:

  1. Open the C:\ProgramData\Solarwinds\Orion\NetPath\NetPathAgent.cfg file in a text editor.
  2. Change the EnableAdvancedBpf value from true to false.
  3. Set the InterfaceIpAddress value to 10.1.1.184.
  4. Restart the Orion module engine service and wait for the probing interval to finish.
 

 

Last modified

Tags

Classifications

Public