- On same CRE, I had a success to scan a smaller subnet and had 40 IPs discovered in 192.168.4.0/22 subnet.
-
Looks like it is using plain ping, not fping, to scan the subnet.
-
Is there a way to trigger a network scan manually,after I expand/shrink subnet range ?
-
Another /16 failed scan due to 110sec timed out.
