I noticed a strange behaviour of fing desktop, which is NOT reflected in FingBox on the same LAN: "Some Device is not able to get in network", quite regularly alternating with "All good in your network". I suspect this is a timing issue, affected are a managed switch of TP-Link (SG1016DE) and sometimes TP-Link access points (AP500, AP300). The switch at least is advertisd with "green IT", maybe it is not quick enough to wake up its dormant ports to respond to fing-desktop-pinging?
I remember, it was - falsely? - messaged by fing desktop also in earlier versions, so not specific to 2.2.2.
Fingbox V1 does not report such errors at all, sitting on the same LAN.
The platform (Lenovo T470) is likely not involved, else the annotation "not able to get in network" might also hit other clients as well.....
- 5.6K All Categories
- 2.8K Ask about Connected Technology
- How To...
- 1K Devices & Security
- 1.5K Network Troubleshooting & Connectivity
- 112 General Discussion, Weird & Wonderful
- 42 Network Infrastructure
- 5.2K Ask about Fing
- 530 Fing Account Change Request
- 1.1K Fing Desktop
- 1.3K Fing App
- 1.6K Fingbox
- 485 Announcements, Beta Testing & Release Notes
- 153 Community Updates
- 24 Getting started
- 13 Community User Guides