Network Inventory Advisor scans wrong IP address
  • KlausKlaus November 2010

    Hello ClearApps Team!
    When I perform an AD import for some devicenames (workstations) NIA does not resolve the correct IP addresses. About 25% of the resolved IP's are wrong.

    I.E. 172.21.31.17 ist the correct IP address assigned by DHCP. During the NIA PING command the IP address is resolved correctly but the scan is beeing performed with an invalid IP address (see Scan-log below). This IP address 172.21.31.65 belongs to another device.

    ATKBWS104 WS 172.21.31.17 22.11.2010 15:07:51 - Trying to ping remote host
    ATKBWS104 WS 172.21.31.17 22.11.2010 15:07:51 - Trying to ping remote host
    ATKBWS104 WS 172.21.31.65 22.11.2010 15:07:51 - Starting scan by DNS name
    ATKBWS104 WS 172.21.31.65 22.11.2010 15:07:51 - Starting scan using agent
    ATKBWS104 WS 172.21.31.65 22.11.2010 15:07:51 - Logging on to the machine

    Settings:
    Connect by Node's name is ENABLED / try both connection methods if one fails is DISABLED / Auto-deploying agent utility SMB is ENABLED

    I already tried the following workarounds but without success: * IPCONFIG /DNSFLUSH * Deleted all devices in NIA * PC rebooted --> but unfortunately I got the same wrong result at the next Scan.
    I really would appriciate your help because at the moment I cannot really use the Network Advisor.

    Rgds. Klaus

  • jeffjeff November 2010

    Hi Klaus, let's check this!

    1. Ping the node by name (get IP #1).
    2. Now ping the IP that you receive in #1 and resolve the name: ping -a [IP-address]
    3. Now ping the name you received in #2 again (get IP #2).

    Are the IP-addresses different?

    Jeff, project designer
    Network Inventory Software

  • KlausKlaus November 2010

    H Jeff,
    IP #1 and IP #2 are the same. Everything seems to be correct from this point of view.

    The NAI scan after these checks had the same problem
    -> Trying to ping remote (172.21.31.17)
    -> Starting Scan by DNS (172.21.31.65)

    1. > ping atkbws104
    Ping atkbws104.atkb.eu.head.net [172.21.31.17] with 32 Bytes Data:
    Reply from von 172.21.31.17: Bytes=32 Time<1ms TTL=128<br />...
    2. >ping -a 172.21.31.17
    Ping atkbws104.atkb.eu.head.net [172.21.31.17] with 32 Bytes Data:
    Reply from 172.21.31.17: Bytes=32 Time<1ms TTL=128<br />...
    3.>ping atkbws104.atkb.eu.head.net
    Ping atkbws104.atkb.eu.head.net [172.21.31.17] with 32 Bytes Datea:
    Reply from 172.21.31.17: Bytes=32 Time<1ms TTL=128<br />...

  • jeffjeff November 2010

    Looking into this now.

    Jeff, project designer
    Network Inventory Software

  • KlausKlaus November 2010

    H Jeff,
    I guess I found the reason for this problem. In the DNS reverse lookup tables Windows stores more than one assignment. In this special case the workstation ATKBWS104 had 2 entries (172.21.31.17 and 172.21.31.65). The .17 is the newer one but I think NAI takes the first in the alhpanumeric order of the name.
    I

  • jeffjeff November 2010

    Hey! Thank you for this hint. We are looking into this now.

    Jeff, project designer
    Network Inventory Software

Add a Comment

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In Apply for Membership

Categories

In this Discussion

Tagged

Network Inventory Software
PC Inventory Software