discovery device history statuses

[Ravish Shetty]

hi all,

we are seeing some of these statuses for the discovery for windows servers from the device history. any known reason for these apart from credentials not authenticating?

[daniel_badyan]

i would also suggest looking into the WMI port, it the machine is up and running and port is closed you should get a similar message.

also, to be able to get more info, i suggest going to the ecc queue for a specific discovery, and take a look at the input records of both shazzam probe and the windows classification probe(if it even showed up).

[doug_schulze · Accepted solution]

Active = There were classification ports open 

Active couldnt classify = We saw the classification ports open but when we tried to authenticate it failed

Active couldnt classify, no wmi connection = We saw port 135 open but when we tried to talk WMI no response was given.

Alive, not active, not classified = No Classification ports were open but we got some level of response such as refused. 

Hope that helps.

[arordeep]

Hi Doug,

We are getting "Active, couldn't classify" for some windows (Win 2012) servers but others are working fine.  We have validated the credentials are fine, able to validate them on the same server.  Also, the port 135 is open, verified in the logs.  What else could be the reason for Discovery not able to classify these servers?

Regards,

Deepak 

[arordeep]

We are getting "Active, couldn't classify" for some windows (Win 2012) servers but others are working fine.  We have validated the credentials are fine, able to validate them on the same server.  Also, the port 135 is open, verified in the logs.  What else could be the reason for Discovery not able to classify these servers?