Active, couldn't classify
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-06-2012 12:38 PM
I'm getting Active, couldn't classify on a laptop I know thats on the network. I can ping it and its on our network. But discovery can't seem to find it. Any help would be appreciated.
- Labels:
-
Discovery
-
Service Mapping

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-17-2012 08:44 AM
"Active, couldn't classify" usually means that Ping is successful, but connection or authentication failed on WMI (presuming it is a Windows Laptop) or which ever protocol was attempted.
Take a look at the DETAILS link on that Device and see if it is a connection issue or authentication.
I used the word "usually" because it could be a case where classification actually failed because the laptop did not match any of the CI CLASSIFICATIONs defined in the system. This is unlikely with a Windows laptop, but possible.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-29-2020 03:18 AM
Hi, This means SNMP credentials are incorrect.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-30-2020 07:48 AM
Community article might be helpful: I am getting this error Active Couldn't Classify
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-31-2020 11:04 AM
Hi,
"Active, couldn't classify" error usually means the credentials are not correct/appropriate ports are not opened. I would suggest checking if the correct ports are opened from your MID server to the device and then validating the credentials(Windows/SSH) before attempting the discovery. Go to credentials- windows- select the appropriate credential for the server-keep the port 135 or change it to 5985(customer specific) and test it. If it is validated, you don't generally encounter any error in discovery. Same for Linux server/laptop with SSH credential for port 22.
Regards,
Akshatha