Getting Active, couldn't classify: No WMI connection in discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-21-2020 02:11 PM
Getting Active, couldn't classify: No WMI connection in discovery. I was able to see 5 computers classify but all others were getting this message. I tested my credentials on my laptop and it failed but passed on the 5 computers that were classify. Is there something I need to do to have them scan? Since we are remote I'm scanning the VPN ip address subnets.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-22-2020 03:09 AM
Hi,
You have to open port 135 and 445. Also check if there is any Firewall blocking the connection between MID server and this computer.
Try to ping or telnet the device, check if RDP service is running on this machine.
Thanks,
Ashutosh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-22-2020 03:29 AM
Ashutosh,
I've enable RDP and the port came back open after the scan. But I get this error now
I'm 100 percent sure that my username and password are correct in the credentials. It worked when we were in the office but now since we are remote it's not working. Also that servicenow account I use has local admin rights on all the computers.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-22-2020 03:42 AM
Hi,
I think you should check this:
https://hi.service-now.com/kb_view.do?sysparm_article=KB0564282
and
https://hi.service-now.com/kb_view.do?sysparm_article=KB0549834
I am sure there is a firewall issue or the user has some issue on target machine.
Thanks,
Ashutosh Munot