Is Windows 2003 Server discovery still supported on New York?

[jcanjura]

Hi, 

Is "Windows 2003 Server" Discovery still supported on New York?

I'm getting the error "Active, couldn't classify: No WMI connection, now finished" even when I can RDP into the box, credentials are fine, and if I open a Discovery Debug session I can connect and see attributes populated.

There is no Firewall between the server and the MID servers.

Thanks.

[Azim Kazi]

Hi,

Is "Windows 2003 Server" Discovery still supported on New York?

👉 Yes it is supported as You can see below's snap

I'm getting the error "Active, couldn't classify: No WMI connection, now finished" even when I can RDP into the box, credentials are fine, and if I open a Discovery Debug session I can connect and see attributes populated.

👉 this kind of error you get when there is no classification criteria so you need to check naming convention or update this "Windows 2003 Server" classification rule by making few changes it will be working fine just do this.

There is no Firewall between the server and the MID servers.

👉if your discovery finding but doesn't classifying the ci that means there is no error is occurring due to firewall this error comes due to mismatch or unavailable discovery CI classification rule you can make changes in that CI classification rule or you can also create new one if you want.

Hope this helps !

If my response helps you in any way then please mark answer helpful 👍and correct ✔ based on impact.

Regards,

Ajim

[chuckm]

Did you also check that the local Windows firewall (Windows Firewall with Advanced Security) isn't blocking discovery?  Discovery for Windows 2003 servers require port 135 open for initial communication AND high ports 1025 - 5000 (Windows version Windows 2000, Windows XP, and Windows 2003) open for the remainder of the communication.  It is possible the high ports are being blocked by the local firewall installed on Windows.

[Ashutosh Munot1 · Accepted solution]

HI,

Yes i also use to get this errors.

First thing i used to do is:

1) login to  MID Server and try to do RDP to target machine.

2) telnet on port 135 on target machine

3) I will open powershell on MID Server and run below script to see if this script executes fine or not:

• WMI and Powershell
  • The impersonation of the user failed.
  • Ensure that the domain is specified, along with the username in the credentials.

• Connection failed to WMI service and other common Windows (WMI/Powershell) error messages:
  
  Error: The remote server machine does not exist or is unavailable
  
  Failed to access target system. Please check credentials and firewall settings on the target system to ensure accessibility: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
  
  Failed to access target system. Please check credentials and firewall settings on the target system to ensure accessibility: The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)
  
  
  • WMI, does the mid server service account have access to the targeted machine? What if a domain admin account is used as the mid server service account?
  • From the command prompt on the mid server host, execute for runner_type=WMI
    
    wmic /node:"<target>" /user:"<user>" /password:"<password>" path win32_operatingsystem
     
  • From within a Powershell console on the mid server host, execute for runner_type=Powershell
    
    gwmi win32_operatingsystem -computer <ip> -credential '<username>'
     
  • It is possible that probe is timing out while waiting for a response. If the command is successful from a command prompt, try extending the wmi_timeout value of the probe.

Check this as well:

https://hi.service-now.com/kb_view.do?sys_kb_id=16eb857edbde9bc04816f3231f9619a5&sysparm_rank=6&sysp...

https://community.servicenow.com/community?id=community_question&sys_id=4ad529a1db52ef004abd5583ca96...

https://hi.service-now.com/kb_view.do?sysparm_article=KB0564282

Thanks,
Ashutosh