Discovery Error - Scanning the VPN - End user laptops
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-29-2024 04:20 AM
We are trying to scan the devices in the VPN region (WFH users) using the ServiceNow Discovery application. On day 1 most of the devices are discovered from the VPN region and on day 2 the same devices on that VPN range are not discovered and show an "Active, Couldn't Classify" error. As those devices were discovered on day 1 with the same credentials we can rule out the credential error. Can anyone help us?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-29-2024 07:52 AM
Hi @Kalatheeswaran ,
Discover the device which connected to VPN is not best practices as IP always change , Might be this is the issue due to which you are not able to discover the Device.
Please check the Discovery logs whats the exact error , Also it will be good if you share the Discovery logs of Shazzam probe input and classification input probe to analyse the same
Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.
Thanks
AJ
Linkedin Profile:- https://www.linkedin.com/in/ajay-kumar-66a91385/
ServiceNow Community Rising Star 2024