We have machines on 2 AD Domains. We also have an IP Scan Range setup to scan one particular IP range with the credentials for the 2nd Domain specified. This seems to work, machines are found & data collected.

What else happens is we got errors in these Machine's Windows Security Logs (wIn 7) about failed login attempts, with the other Domains credentials, on average every 143 seconds. So, even though we specify the correct credentials for that domain and items get found is it also trying to connect to these devices with the Spiceworks default set of credentials? over & over?

We have machines on 2 AD Domains. We also have an IP Scan Range setup to scan one particular IP range with the credentials for the 2nd Domain specified. This seems to work, machines are found & data collected.

What else happens is we got errors in these Machine's Windows Security Logs (wIn 7) about failed login attempts, with the other Domains credentials, on average every 143 seconds. So, even though we specify the correct credentials for that domain and items get found is it also trying to connect to these devices with the Spiceworks default set of credentials? over & over?

We decided it wasn't worth setting up another full installation of Spiceworks on the other domain to collect data (nor have a suitable VM / machine for it at the moment). The main install still actually collects data fine so we're just putting up with the log spam for now. Spiceworks support advised that v6 has a re-worked scan engine that may help with the issue.