Discovery Schedule of Subnet fails, individual IP succeeds.

[Michael Lineba2]

We are seeing Windows Server discovery failing in Schedules containing IP range.     But if I go into a Quick Discovery of a single IP it works fine.      For example Schedule is to discover a /24 subnet.     ALL the Windows discoveries fail, all credentials are tried by the logs in order as expected but no valid credential is found.

<results error="Adding target to blacklist. No valid credential found for type [Windows]" probe_time="10820" result_code="42">

If we go into the range and pick a single IP for the Quick Discovery it succeeds.        Has anyone seen this issue ?

[Appli]

Hi, do you use the same MID server for both discovery sessions (quick and regular)?

What if Schedule contains just one IP you use for quick discovery, will it also fail?

[Doci1]

As Appli reccomend, I would start with "Quick ranges" of a single IP from Discovery Schedule record. Not Quick discovery from list of schedules 😉 

[Michael Lineba2]

Thanks for those suggestions I will reach out to try those, it may take a bit since this is in a Production environment and we cannot do changes without CRB permission.

[Doci1]

so do it in dev! 😉