1

Hello,

In our company’s spicework it seems like the IP-adress will resolve through DNS, but at the device in question the ip-adress does not change. In the overview of the scan it also shows the device at the old ip-adress.

If I, at the device inventory, ping or traceroute the device, it keeps using the old ip-adress, but if I use nslookup it finds the new ip-adress. The device is pingable with command prompt though.

I know that the ip-adress should be resolved at the point of a new scan and it does show up at the dns configuration where all the dns entries are shown, but still the device is not being inventorised.

We’re at spiceworks 7.4.00065

This looks like it’s not a DNS or DHCP problem, because spiceworks can indeed find the correct ip-adress. It seems like spiceworks won’t let go of the old ip-adresses.

Is this normal Spiceworks behaviour?

@Spiceworks

2 Spice ups
2

Moved to SpiceWorks support.

3

Thanks! Need to get used to this community website…

4

Are you seeing this just on one individual machine or on multiple machines? Also, are the machines that change IP addresses getting them from DHCP or are they statically assigned?

5

And no, this is not normal Spiceworks behavior.

6

Its on multiple machines, at least a few which were previously inventoried, and at least one device which wasn’t. They all give the same message of no ports available, but its obvious its looking at the wrong IP.
All the devices mentioned are getting their IP from dhcp.
Not sure if it matters, but last Friday was the first scan.

7

Does anyone have a suggestion?

8

Hey Jannick,

Spiceworks should let get of the old IP. I’ve seen this in the past and generally it does end up relating to a DNS issue. There could be some other issues too, though.

If you delete one of the devices out of your inventory completely, does it scan in with the correct IP address?

9

Deleting the device didn’t help. In the scan overview it stays put in red on the old IP-adress.

If I troubleshoot one of the computers with a scan error (in this case ‘avw-545-00’) and Run All this is the outcome:

Ping (13:53:37)

Pinging 172.22.32.93 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 172.22.32.93:
Packets: Sent = 5, Received = 0, Lost = 5 (100% loss),

Trace Route (13:53:37)

Tracing route to avw-532-08.gregorius.net [172.22.32.93]
over a maximum of 8 hops:

1 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.

Trace complete.

NS Lookup (13:53:37)
Server: dc01.gregorius.net
Address: 172.20.17.40

Name: avw-545-00.gregorius.net
Address: 172.22.32.98

Why would it ping the old ip, if it just found out with NSLookup another ip?

Could anyone point me in hopefully the right direction? I really appreciate any help you can provide.

Jannick

10

Hey Jannick,

Hmm, the first thing that comes to mind is that the reverse DNS entry might be causing a problem. Do you have a single, valid reverse lookup for your devices within DNS?

1 Spice up
11

It seems there ís a problem there. If I ping with attribute -a (in cmd), I get an IP, and when I subsequently ping that IP I get another device name. (Did a ‘ipconfig /flushdns’ on beforehand, and in between the pings)

Will have to get my collegues into that. Thanks for the help!

1 Spice up