Online / Offline Status not working since 2.2.1

[karel.krobath]

Hi,

There is an issue regarding the display of the online / offline status in TNI since the version 2.2.1. The Issue occurs especially in routed networks with more than 300 clients to monitor.

Usually the status stalls with a yellow dot, the first half of the clients is displayed, and the rest is not even pinged. (The status is not displayed properly even if I change the engine, which should be used.)

When I downgrade to the Version 2.2.0 with the nmap engine, it works fine.

Greetings, Karel

 

 

[rarens]

• I have the same problem, the most devices are with yellow dot ... :(

[Support]

Please update to the latest version 2.2.2 (build 1483) released today and let us know if it fixes the issue. Thank you.

[laola1]

After the update the yellow dots will disappear. Maybe you have to "ping" your store one more time. 

[karel.krobath]

After the update to build 1483 the online status worked quite fine. (it took about 1 minute to update the status for 321 PCs)

 

With the update to build 1490 the bug is a bit back again with the nmap engine and the async engine. (it takes about 5 to 10 minutes to update the status for 321 PCs)

[Support]

Karel,

 

What about the Classic engine in build 1490?

 

What we changed between 1483 and 1490 is that the ARP ping is not used for monitoring of the online state anymore. In 1483 it's still used. However it gives incorrect results on Windows XP (when an asset goes offline, it still shows as online for about 10 minutes, as its MAC is still present in the ARP table), and also if there is Proxy ARP enabled on a switch or router.

 

Are all your PCs on static or dynamic IP addressing? (static IPs have a padlock icon next to the IP address in the tree, and dynamic IPs don't have it).

[karel.krobath]

Hi,

 

the classic engine works quite well after the start of the program.

 

About 10 minutes later the status disappears.

[Support]

Hi Karel,

 

Please check if the Async and Nmap engines work fine in the latest version (2.2.3 build 1528). We've made some changes and now all dynamic IP addresses should be pinged in 1-2 minutes after the program start. Thank you.