Submit a ticketCall us

WebinarUpcoming Webinar: How Help Desk and Remote Support Pays for Itself

Learn how help desk software can simplify ticketing management, allow you to track hardware and software assets, and accelerate the speed of IT support and service delivery. Gain insights on how remote support tools allow your IT team to maximize their efficiency and ticket resolution by expediting desktop troubleshooting, ultimately helping keep end-users happy and productive.

Register here.

Home > Success Center > User Device Tracker (UDT) > User Device Tracker (UDT) Documentation > UDT Administrator Guide > Troubleshooting > Node discovery fails for some devices

Node discovery fails for some devices

Table of contents
Created by Steven Bansil_ret, last modified by Steven Bansil_ret on Feb 02, 2017

Views: 108 Votes: 0 Revisions: 2

Issue

The device discovery fails when it's done for specific devices.

Solution

  • UDT Discovery runs on the poller the nodes are affiliated with (i.e. it respects main and additional polling engines) since UDT 2.5. Make sure the machine where appropriate poller is installed has access to the selected device.
  • Run UDT Compatibility Checker (discovery target ) from machine with the right polling engine against the device and check the results.
  • Increase Port/Layer3 Discovery Job Timeout (Advanced Settings page)
  • Increase SNMP Timeout (Advanced Settings page)
 
Last modified

Tags

Classifications

Public