I’ve run my Spiceworks Scan and it’s come back with the following errors
Windows firewall or permission issue (118 Devices)
Failed to establish connection to WMI service.
I followed the instructions however when I went into my default domain policy I’m seeing that Windows Firewall is disabled across the board. I created the GP just the same and pushed it out to my 650 Machines. Created a batch file to Mass Reboot all machines to ensure that they pulled the new policy. Spot checked machines and they had the new policy. I went ahead and deleted my DB and Data Files and ran the Spiceworks scan all over again.
Still Same Result…
Spiceworks is running on it’s own Server with Server 2003 R2. I have a mix of Windows 7 Pro and Win XP Pro machines on my network. I’ve attempted to Remove and Add machines off the domain and back on. I’ve attempted to run the scan at Night and also during the day. Power Features are all turned off none of my machines go to sleep and they auto turn on at 1:00AM everyday if they are turned off at any point during the day. They also reboot at 2:00AM everyday to ensure windows updates and anything else that I push out gets passed to them.
Please help… Let me know what other information you need to provide assistance.
5 Spice ups
For the username for the WMI authentication, did you use the syntax Domain\Username ?
1 Spice up
Yes… I’ve tried my Domain Admin Account, My Local Admin Account, My Local Account and My Enterprise Admin Account none work. Yet I can go up to the machine and log in without any trouble with any of these accounts.
cody1308
(Cody5281)
4
Have you tried to connect to the remote workstation’s WMI from the server that spiceworks is installed on ?
http://community.spiceworks.com/help/Resolving_Unknown_Devices#Windows
http://community.spiceworks.com/help/Troubleshooting_WMI
i found a lot of my scan error’s were WMI configuration error’s. The above cleared most of mine up.
Try running this script “netsh firewall set service RemoteAdmin enable”
Chris - Ran the command on several machines - started my scan and those machines continue to be an issue
Cody - Tried both of those and still having trouble.
BTW the command in the help file is incorrect or I had to do it differently to get it to work. They have systemclosure in the help file but as you can see below I had to put systemenclosure
C:\WINDOWS\system32>wmic /user: me\Administrator /password: ****** /node: "
ME-***-350" systemenclosure get serialnumber
Running this command the station does return the serial number.
I’ve disabled my Antivirus on the stations as well, Disabled Windows Firewall and everything that goes with it.
Symantec Endpoint Protection
Lenny,
Here’s a link where it appears that Symantec was the culprit. Although being turned off, there were some rules still in affect that were causing it to be blocked. It appears they found the fix towards the end after much troubleshooting.
http://community.spiceworks.com/topic/136956-cannot-get-spiceworks-working-through-symantec-endpoint-protection-firewall
Let me know if that helped.
Still no go even going through all of these documents…
Just a bit more information we have 8 sites all 8 sites are using the same .msi file for symantec and all 8 sites have a Spiceworks box I’m currently the only site having the problem. We also all use the same Domain Policy just modified slightly for each domain.
Any other idea’s?
I’m sorry, no. I have little experience with your AV, and have given you all the tidbits that have worked for me in the past. Hopefully someone more knowledgeable will come behind me.
Good luck!
Anyone else have any idea’s on how to resolve these.
molan
(molan)
14
on one of the troubled machines log into your spiceworks web portal but after the port # put /fix
example
https://spiceworks:9676/fix
then select the machine you are on and it will give you a guide to walk through some items to try and resolve the issues.
There will also be a link on the right side of the page to download a utility (beta) that you can run on the problem machine.
The utility will check it for common issues that prevent SW scanning it and help you resolve them.
It works