Submit a ticketCall us

WebinarUpcoming Webinar: Should I Move My Database to the Cloud?

So you’ve been running an on-premises SQL Server® for a while now. Maybe you’ve moved it from bare metal to a VM, and have seen some positive benefits. But, do you want to see more? If you said “YES!”, then this session is for you, as James Serra will review the many benefits that can be gained by moving your on-prem SQL Server to an Azure® VM (IaaS). He’ll also talk about the many hybrid approaches, so you can gradually move to the cloud. If you are interested in cost savings, additional features, ease of use, quick scaling, improved reliability, and ending the days of upgrading hardware, this is the session for you.

Register now.

Home > Success Center > User Device Tracker (UDT) > UDT - Knowledgebase Articles > Unable to find ports for User Device Tracker

Unable to find ports for User Device Tracker

Table of contents
No headers
Created by Interspire Import, last modified by MindTouch on Jun 23, 2016

Views: 1,190 Votes: 0 Revisions: 8

Issue:

No ports were found in a network discovery that was expected to return devices with active ports.

 

Resolution:

Typically, a network discovery fails to find ports to import for one or more of the following reasons:

  • You have provided incorrect SNMP credentials for the devices you expected to discover
  • You did not check the option to "Ignore nodes that only respond to ICMP (ping)" on the Discovery Settings view of Network Discovery, and the devices discovered are ICMP-only with no ports.
  • The nodes discovered do not currently have any actively operational ports.

In either case, confirm the following, and then run discovery again:

  • Your discovery criteria do not exclude the devices on which you expect to find ports
  • All ports you expect to see on discovered nodes are fully operational.

This article applies to all versions of SolarWinds UDT.

Last modified

Tags

Classifications

Public