1

I tried searching through the database of questions and answers with various keywords and I wasn’t able to find anything on this particular issue. When I run a network scan, Spiceworks will find (for example) 14 unknown devices. I take one of the devices and enter a valid administrator account name and password and then click Test. The test passes. I then click save and Spiceworks tells me that the account name I used for that one, has also resolved all 13 of the other ones. Then it says it’s going to go out and scan those devices to get the rest of the information it needs. It scans away for a while and then comes back up with the original 14 devices listed as unknown all over again. This can go on all day long. What do you think causes authentication to fail just moments after it passes? Do you know of any way to resolve this?

1 Spice up
2

  1. I think the authentication issue with the test and the actual scan differ which is why you get conflicting reports.

  2. I’ve seen that issue before but it happens for an entirely different reason. I had migrated my system to Full native 2003 active directory mode. I have problems with scanning NT and 98 machines, even with the WMI packs. Are you in a similar situation? What are the OSes of the machines you’re trying to scan?

  3. In the Settings > Network list, try changing the scan credentials to the domain\user format to see if that helps. You need to double-click the Windows user to have access to the options.

3

Thank you. I will give that a try. We’re running Windows server 2003 and all devices are on Windows XP.

4

Putting the domain in front of the user name worked beautifully! Thanks very much!

5

Not a problem. Glad to help.