When a device has been scanned into inventory and then moves to another subnet which is also scanned by Spiceworks, I am realizing that Spiceworks keeps that device as having the original IP even after the device’s IP changes. So DHCP hands a newer device that original IP and Spiceworks doesn’t seem to be updating the first device at all. Is this how Spiceworks handles things?<\/p>","upvoteCount":4,"answerCount":7,"datePublished":"2019-09-19T17:34:48.000Z","author":{"@type":"Person","name":"gregchin","url":"https://community.spiceworks.com/u/gregchin"},"suggestedAnswer":[{"@type":"Answer","text":"
When a device has been scanned into inventory and then moves to another subnet which is also scanned by Spiceworks, I am realizing that Spiceworks keeps that device as having the original IP even after the device’s IP changes. So DHCP hands a newer device that original IP and Spiceworks doesn’t seem to be updating the first device at all. Is this how Spiceworks handles things?<\/p>","upvoteCount":4,"datePublished":"2019-09-19T17:34:49.000Z","url":"https://community.spiceworks.com/t/inventory-when-ip-changes/730945/1","author":{"@type":"Person","name":"gregchin","url":"https://community.spiceworks.com/u/gregchin"}},{"@type":"Answer","text":"
I’ve a similar problem even within the same network. I reconfigured DHCP to assign a fixed IP address to one device, keeping its device name unchanged. Then I rebooted it to take the new IP address (static local instead of dynamic local). After that I could access it normally under the name and the new IP address. So I requested Spicework to do a rescan of the network in order to discover this configuration change. But Spicework still thought it under its previous address and didn’t discover the new address. I then tried a reboot of Spiceworks and its computer without any effect on Spiceworks. It declares that device as unreachable and sticks with that devices old IP address. I would have expected in case of its inventory setting as manually managed. But the device is configured as non-manual managed.<\/p>\n
So I don’t understand why this new IP address wasn’t discovered by Spiceworks. And why Spiceworks didn’t updatte this devices records.<\/p>\n
Now I tried to change the inventory setting to manually managed (temporarily) in order to become able to reset the IP address of that device. That worked. Now that device is in maintenance and hence can’t tell yet, if Spiceworks keeps the manually changed IP address after setting back this inventory record to non-manually managed and asking a rescan of the network. So can’t yet report if that was sufficient. (And this device is not running Windows but Linux instead.)<\/p>\n
So if my trial succeeds, it represents a work around although not matching my expectations of Spiceworks inventory!<\/p>","upvoteCount":0,"datePublished":"2019-09-19T18:13:51.000Z","url":"https://community.spiceworks.com/t/inventory-when-ip-changes/730945/2","author":{"@type":"Person","name":"scheff1","url":"https://community.spiceworks.com/u/scheff1"}},{"@type":"Answer","text":"
I have been dealing with this problem for well over a year. The best thing I found that works is to just install the Spiceworks Agent on the client devices. This will guarantee the IP is correct on those devices with the Agent installed (if it’s online)and the updates are much more responsive as well.<\/p>\n
We have also added to our decommissioned devices to be set to manually manged and remove the IP, as it helps as well.<\/p>","upvoteCount":1,"datePublished":"2019-09-19T20:32:36.000Z","url":"https://community.spiceworks.com/t/inventory-when-ip-changes/730945/3","author":{"@type":"Person","name":"joshmecahm","url":"https://community.spiceworks.com/u/joshmecahm"}},{"@type":"Answer","text":"\n\n
<\/div>\n
scheff1:<\/div>\n
\nSo if my trial succeeds, it represents a work around although not matching my expectations of Spiceworks inventory!<\/p>\n<\/blockquote>\n<\/aside>\n
My trial was only partially successful. (I forgot to mention that I’m running the actual Spiceworks 7.5.00107 on-premise in the installed variant for a about four month now.)<\/p>\n
In manual managed mode, I could edit and change the IP address to the new one and save it. In device view, that entry turned back green (reachable). I was able to connect with various Spiceworks troubleshooting tools successfully too. But when looking at complete (device) profile, I still can see old IP address and old reboot data, and not the actual IP address in the network adapter section although the correct one in the manually edited field at the top level. Also when trying the new Spiceworks beta troubleshooting view, I get certain subsections displayed (partially, meaning correct legend and fixed HW data but no content [CPU Activity, System Memory Activity, Network Activity, Processes, Services]) while another subsection remains loading (disk activity). The device in question is a NAS running OEM variant of Linux and Spiceworks configured to use ssh access for scanning.<\/p>\n
When then switching back to non-manually managed mode, the display of the IP address didn’t change and the device turned back into offline although displaying the correct IP address of the time of manual editing. When then looking in the scan section, this device is still displayed at the old IP address which is no longer in use!<\/p>\n\n\n
<\/div>\n
Josh_the_Geek:<\/div>\n
\nWe have also added to our decommissioned devices to be set to manually manged and remove the IP, as it helps as well.<\/p>\n<\/blockquote>\n<\/aside>\n
Hence I tried that proposed work around. Same result as above.<\/p>\n
Can’t use the agent variant as this device is a NAS running Linux and the agent is a Windows application. Haven’t seen wine on the NAS and don’t expect wine to be able to run. It’s an ARM CPU with not sufficient memory to take on the load of wine in addition to its main storage task.<\/p>","upvoteCount":0,"datePublished":"2019-09-20T13:21:49.000Z","url":"https://community.spiceworks.com/t/inventory-when-ip-changes/730945/4","author":{"@type":"Person","name":"scheff1","url":"https://community.spiceworks.com/u/scheff1"}},{"@type":"Answer","text":"\n\n
<\/div>\n
scheff1:<\/div>\n
\n\n\n
<\/div>\n
scheff1:<\/div>\n
\nSo if my trial succeeds, it represents a work around although not matching my expectations of Spiceworks inventory!<\/p>\n<\/blockquote>\n<\/aside>\n
My trial was only partially successful. (I forgot to mention that I’m running the actual Spiceworks 7.5.00107 on-premise in the installed variant for a about four month now.)<\/p>\n
In manual managed mode, I could edit and change the IP address to the new one and save it. In device view, that entry turned back green (reachable). I was able to connect with various Spiceworks troubleshooting tools successfully too. But when looking at complete (device) profile, I still can see old IP address and old reboot data, and not the actual IP address in the network adapter section although the correct one in the manually edited field at the top level. Also when trying the new Spiceworks beta troubleshooting view, I get certain subsections displayed (partially, meaning correct legend and fixed HW data but no content [CPU Activity, System Memory Activity, Network Activity, Processes, Services]) while another subsection remains loading (disk activity). The device in question is a NAS running OEM variant of Linux and Spiceworks configured to use ssh access for scanning.<\/p>\n
When then switching back to non-manually managed mode, the display of the IP address didn’t change and the device turned back into offline although displaying the correct IP address of the time of manual editing. When then looking in the scan section, this device is still displayed at the old IP address which is no longer in use!<\/p>\n\n\n
<\/div>\n
Josh_the_Geek:<\/div>\n
\nWe have also added to our decommissioned devices to be set to manually manged and remove the IP, as it helps as well.<\/p>\n<\/blockquote>\n<\/aside>\n
Hence I tried that proposed work around. Same result as above.<\/p>\n
Can’t use the agent variant as this device is a NAS running Linux and the agent is a Windows application. Haven’t seen wine on the NAS and don’t expect wine to be able to run. It’s an ARM CPU with not sufficient memory to take on the load of wine in addition to its main storage task.<\/p>\n<\/blockquote>\n<\/aside>\n
I see, Anything non Windows in our environment has a static IP, and anything that isn’t that or Windows isn’t allowed on the network.<\/p>","upvoteCount":0,"datePublished":"2019-09-20T14:53:31.000Z","url":"https://community.spiceworks.com/t/inventory-when-ip-changes/730945/5","author":{"@type":"Person","name":"joshmecahm","url":"https://community.spiceworks.com/u/joshmecahm"}},{"@type":"Answer","text":"
I’m hoping someone who works there might actually chime in and give us some insight.<\/p>","upvoteCount":0,"datePublished":"2019-09-20T16:54:00.000Z","url":"https://community.spiceworks.com/t/inventory-when-ip-changes/730945/6","author":{"@type":"Person","name":"gregchin","url":"https://community.spiceworks.com/u/gregchin"}},{"@type":"Answer","text":"
We’ve been dipping out toe’s into Spiceworks for years and this one issue has been a major reason we cannot get on-board.<\/p>\n
I’m sorry it’s still an issue and hasn’t been properly addressed by the developers.<\/p>","upvoteCount":0,"datePublished":"2020-02-10T15:10:14.000Z","url":"https://community.spiceworks.com/t/inventory-when-ip-changes/730945/7","author":{"@type":"Person","name":"adamb3","url":"https://community.spiceworks.com/u/adamb3"}}]}}
gregchin
September 19, 2019, 5:34pm
1
When a device has been scanned into inventory and then moves to another subnet which is also scanned by Spiceworks, I am realizing that Spiceworks keeps that device as having the original IP even after the device’s IP changes. So DHCP hands a newer device that original IP and Spiceworks doesn’t seem to be updating the first device at all. Is this how Spiceworks handles things?
4 Spice ups
scheff1
September 19, 2019, 6:13pm
2
I’ve a similar problem even within the same network. I reconfigured DHCP to assign a fixed IP address to one device, keeping its device name unchanged. Then I rebooted it to take the new IP address (static local instead of dynamic local). After that I could access it normally under the name and the new IP address. So I requested Spicework to do a rescan of the network in order to discover this configuration change. But Spicework still thought it under its previous address and didn’t discover the new address. I then tried a reboot of Spiceworks and its computer without any effect on Spiceworks. It declares that device as unreachable and sticks with that devices old IP address. I would have expected in case of its inventory setting as manually managed. But the device is configured as non-manual managed.
So I don’t understand why this new IP address wasn’t discovered by Spiceworks. And why Spiceworks didn’t updatte this devices records.
Now I tried to change the inventory setting to manually managed (temporarily) in order to become able to reset the IP address of that device. That worked. Now that device is in maintenance and hence can’t tell yet, if Spiceworks keeps the manually changed IP address after setting back this inventory record to non-manually managed and asking a rescan of the network. So can’t yet report if that was sufficient. (And this device is not running Windows but Linux instead.)
So if my trial succeeds, it represents a work around although not matching my expectations of Spiceworks inventory!
joshmecahm
September 19, 2019, 8:32pm
3
I have been dealing with this problem for well over a year. The best thing I found that works is to just install the Spiceworks Agent on the client devices. This will guarantee the IP is correct on those devices with the Agent installed (if it’s online)and the updates are much more responsive as well.
We have also added to our decommissioned devices to be set to manually manged and remove the IP, as it helps as well.
1 Spice up
scheff1
September 20, 2019, 1:21pm
4
My trial was only partially successful. (I forgot to mention that I’m running the actual Spiceworks 7.5.00107 on-premise in the installed variant for a about four month now.)
In manual managed mode, I could edit and change the IP address to the new one and save it. In device view, that entry turned back green (reachable). I was able to connect with various Spiceworks troubleshooting tools successfully too. But when looking at complete (device) profile, I still can see old IP address and old reboot data, and not the actual IP address in the network adapter section although the correct one in the manually edited field at the top level. Also when trying the new Spiceworks beta troubleshooting view, I get certain subsections displayed (partially, meaning correct legend and fixed HW data but no content [CPU Activity, System Memory Activity, Network Activity, Processes, Services]) while another subsection remains loading (disk activity). The device in question is a NAS running OEM variant of Linux and Spiceworks configured to use ssh access for scanning.
When then switching back to non-manually managed mode, the display of the IP address didn’t change and the device turned back into offline although displaying the correct IP address of the time of manual editing. When then looking in the scan section, this device is still displayed at the old IP address which is no longer in use!
Hence I tried that proposed work around. Same result as above.
Can’t use the agent variant as this device is a NAS running Linux and the agent is a Windows application. Haven’t seen wine on the NAS and don’t expect wine to be able to run. It’s an ARM CPU with not sufficient memory to take on the load of wine in addition to its main storage task.
joshmecahm
September 20, 2019, 2:53pm
5
scheff1:
My trial was only partially successful. (I forgot to mention that I’m running the actual Spiceworks 7.5.00107 on-premise in the installed variant for a about four month now.)
In manual managed mode, I could edit and change the IP address to the new one and save it. In device view, that entry turned back green (reachable). I was able to connect with various Spiceworks troubleshooting tools successfully too. But when looking at complete (device) profile, I still can see old IP address and old reboot data, and not the actual IP address in the network adapter section although the correct one in the manually edited field at the top level. Also when trying the new Spiceworks beta troubleshooting view, I get certain subsections displayed (partially, meaning correct legend and fixed HW data but no content [CPU Activity, System Memory Activity, Network Activity, Processes, Services]) while another subsection remains loading (disk activity). The device in question is a NAS running OEM variant of Linux and Spiceworks configured to use ssh access for scanning.
When then switching back to non-manually managed mode, the display of the IP address didn’t change and the device turned back into offline although displaying the correct IP address of the time of manual editing. When then looking in the scan section, this device is still displayed at the old IP address which is no longer in use!
Hence I tried that proposed work around. Same result as above.
Can’t use the agent variant as this device is a NAS running Linux and the agent is a Windows application. Haven’t seen wine on the NAS and don’t expect wine to be able to run. It’s an ARM CPU with not sufficient memory to take on the load of wine in addition to its main storage task.
I see, Anything non Windows in our environment has a static IP, and anything that isn’t that or Windows isn’t allowed on the network.
gregchin
September 20, 2019, 4:54pm
6
I’m hoping someone who works there might actually chime in and give us some insight.
adamb3
February 10, 2020, 3:10pm
7
We’ve been dipping out toe’s into Spiceworks for years and this one issue has been a major reason we cannot get on-board.
I’m sorry it’s still an issue and hasn’t been properly addressed by the developers.
