1

Hello everyone,

Firstly, kudos to what the great work Spiceworks is doing to IT.

We’ve been trying to deploy the software on our server here (No active directory) but almost all our devices are “unknown” and i can’t seem to be able to fix the scan errors.I’ve tried most of the solution i found here, but none seems to work. Is there any way out of this please?

I’ll appreciate a guided/step by step solution.

Thank you in advance.

3 Spice ups
2

First suggestions are.

  1. enable snmp on your devices. As an example my experience with multiple printer vendors is that it works if I go into the physical device and set the community name (ie public) even though according to the manufacturer it defaults to that.

  2. verify that your Spiceworks host is listed in the device config (ie snmp.xml on a VMWare host).

  3. do a bulk delete of the problem devices, SW7 seems to get stuck on them for some reason (I have HP 1536(s) that it would send me supply alerts for but see the devices as unknown until I completely removed them they recreated correctly).

3

Hi Demela,

Spiceworks scans Windows workstations via WMI. Because you’re not using a domain controller, I’d like you to take a look at this article , starting about half-way down with “Workgroup and Non-Domain Specific Information”.

Write back if you have any questions with any of this.

4

Hello Support,

Thanks for all the help, i have taken this long to respond because i wanted to try everything as much i could with your suggestions and links. Unfortunately, nothing has changed. Or is there anything i am doing wrong. Well, i haven’t looked at things from the workstations end though. please advise. Thanks again in advance.

5

Demela,

No worries; I’m only in a rush with this stuff if you are :slight_smile:

As for the workstations, my next suggestion was going to be to run the following tool on your workstations. One of our testers (who used to work with us on the Support team, so he knows how much of a pain these issues can be) built it to fix the exact kind of issues you are having.

http://community.spiceworks.com/help/Spiceworks_Unknowns_Tool

Let me know how that works out.

6

@Peter. Thanks. I have done that already. but still no success. Even though it narrowed down to firewalls and ports etc.

Any suggestions on that?

7

Demela,

Ah, so the Unknowns Tool reported the issue was due to a firewall or a port being blocked?

8

Issues bothering on firewall rules (which port to open and which is blocked) but i can’t seem to figure out where to modify those. We use Kasperky Enpoint Security 10. I followed the link but couldn’t get the exact same variables on my firewall settings.

9

Demela,

Its more likely a firewall problem then a port blocking problem. Can you temporarily disable Kaspersky on the Spiceworks server and on one of the workstations you are trying to scan, then run a manual scan to that machine, and then check if Spiceworks was successful?

10

I have tried this too with one PC. It doesn’t still recognize it.

11

Demela,

Alrighty, let’s dive a little deeper.

  • From the Spiceworks server, try to telnet using port 135, to one of your workstations that you want to scan into Spiceworks.

  • Open a Command Prompt window.

  • The following bit of text is what you should type. Please note that the IP address I added “192.168.1.1” is an example. You will need to replace that IP address with an IP address from one of your workstations that you want to scan.

telnet 192.168.1.1 135

If you are successfully able to connect, you will simply see a black screen.

Write back and let us know how that goes!

12

I tried and got “could not open connection to the host on port 135” connection failed.

13

Well that’s our problem right there :slight_smile:

Now, let’s try disabling the Kaspersky firewall on both the Spiceworks server and one of your Windows workstations. Once that’s done, try to use telnet again and let us know if it works this time.

14

I have done that, still not working…connection failed.

15

Demela,

Well then it must be something else that is blocking it. Do you have any other software firewalls in place?

If not, its likely something configured on a network device that is blocking traffic. Can you run a trace route, from your Spiceworks server, to one of the workstations, and post back what it prints out?

http://support.microsoft.com/kb/162326

16

Trace route completed successfully:

Microsoft Windows [Version 5.2.3790]

(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator>tracert 192.168.1.23

Tracing route to NNENNA-PC [192.168.1.23]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms NNENNA-PC [192.168.1.23]

Trace complete.

C:\Documents and Settings\Administrator>