1

Hello all,

It seems Spiceworks and I have come to an impasse.

I would like to add a couple of machines to our inventory (through IP scanning), but the addresses are tied to other devices. When I attempt a full subnet scan to update the DNS information, it may scan 1-5 machines, then kills the scan.

(I’ve tried a dozen+ times.)

Our network admin is too busy to do anything on the DNS side. Is there anything I can do to convince our Spiceworks installation to update the IPs? (We’re running version 7.4.00060)

I would rather not delete the old machines, as they are active in inventory and physically out of reach.

Thanks!

2 Spice ups
2

First of all I would update, there is a newer version and quirks are often fixed in new releases.

Second I am confused, you say the IPs are tied to other device and you don’t want to delete them from the inventory - if the IP of the machine in the inventory and the IP of the machine you want to scan are the same it will never work, unless you replace one.

You can leave the existing machines in the inventory by changing their scanning to manual and manually edit the IP, freeing up the actual IP to be rescanned - if that’s suitable.

1 Spice up
3

Rod,
If we change the device to be scanned manually, can we change it back to be scanned with the subnet? (For software updates, etc.) Or will we always need to run manual scans on the device?

I will try the update as well. I wasn’t sure if there were known issues with our current release, but we tend to wait a bit before updating to latest the releases of, well, everything.

4

Hey Gina,

If you change a device to be manually managed, you can change it back. Just head over to the device, edit it, and change the “manually managed” option to “no.”

1 Spice up
5

Jon got in first, but you can switch between managed and unmanaged at will.

6

Sounds good.
Unfortunately, getting the ‘old devices’ out of the way didn’t help as the Spiceworks scan still dies before it identifies the device.

I updated my installation to the latest release and rant he “spiceworks unknown assistant” on one of the troubled devices.
The Spiceworks server is able to identify the machine by SN, but scanning by IP address or name within Spiceworks fails.

I find that when I kick off a subnet scan, it identifies maybe 1-4 machines, and then the scan dies.

Any other thoughts?

7

Is file and printer sharing enabled on the devices?

8

It was not. Now it is. Spiceworks still isn’t seeing the machine.

Thanks!

9

Hey Gina,

I say we get some logs over this way and see what’s going on. I’m betting this is going to come down to DNS, but the logs will let us know for sure!

Hold tight and I’ll shoot over an email with some instructions.

10

Ah, it looks like you’re already working with Will on this one! I’ll let you two work on this together. Keep us posted on what you find out! :slight_smile: