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 ?
