1

I’ve spent DAYS trying to get this to work, and it just goes from one error to the next.

I have errors such as:

Authentication failed for user mydomain/myuser

Authentication failed because no Windows account was specified

I’ve done just about everything and none of the results have worked, WMI rebuild, enable/disable UAC, turned off windows firewall completely, and uninstalled 3rd party firewall, logged onto each computer individually to test if the credentials worked, and they do! I even manually add the domain user on each computer with administrator rights.

I tried atleast 5 different scripts that did absolutely nothing,

netsh advfirewall firewall set rule name=“File and Printer Sharing (Echo Request - ICMPv4-In)” new enable=yes

netsh advfirewall firewall add rule name=“Allow RemoteAdmin to Spiceworks” dir=in protocol=tcp remoteip=%AdmIP% action=allow enable=yes

Just can’t seem to get SpiceWorks to work.

I’m on Windows 7 Pro/Ultimate/Enterprise, they are on the same domain, same subnet…

Is there something I’m missing???

5 Spice ups
2

have you tried the script on Grey’s page?

3

Is the account you’ve given Spiceworks a domain admin? Or does it have permission to scan machines?

Is that user also local to the machines you’re scanning?

From what you’ve listed so far, it looks like account issues. Not to say those are the only issues.

Here’s an easy guide to help with Authentication, and other issues.

4

I’m in the same boat. Just doesn’t work on Windows 7 (not on a domain but using a WorkGroup).

5

I’ve got some concerns here…

  1. There was a Windows firewall AND a third party firewall? That’s never a good thing. Could be any amount of lingering issues from that.
  2. You added domain users locally? You mean to the administrators group?
  3. If you shut down the firewall, the firewall management commands shouldn’t have worked.
  4. I don’t see that you shut down AV.
  5. What third party security products do you have installed? Symantec, I’m guessing?

If you can’t get Windows scanning to work, just use the Spiceworks Agent. That works every time. A little more effort to install, but a fraction of the effort of troubleshooting these issues and it sounds like you have a complex environment that might be problematic to scan.

6

i have had no issues running on windows 7 or scanning on a workgroup. None out of the ordinary or that i think AD will fix. I do have a few machines with scanning issues but they are in the minority and i dont want to waste time troubleshooting when I know i am rolling out AD soon.