Is anyone else having a problem getting LAN Watch by Network to work correctly on networks with 16-bit netmasks?
We have a network we support that has a 16-bit netmask. The CIDR is 10.5.0.0/16. When I try to setup LAN Watch by Network on this network, the default IP Scan Range is automatically computed as 10.5.1-254.1-254. However, that is incorrect. The true allowable IP range actually can't be represented well by the shorthand being used above. The allowable IP range is 10.5.0.1 - 10.5.255.254. The commonly accepted CIDR shorthand notation for this is 10.5.0.0/16.
You'll notice that the 3rd octet allows decimal values from 0 to 255 (and not 1-254 like what is currently shown in the default value). And, the fourth octet allows decimal values from 1 to 255 when the third octet value is 0, decimal values from 0 to 255 when the third octet decimal value is not 0 or 255, and decimal values from 0 to 254 when the third octet value is 255.
We need this fixed because we have devices in the parts of those allowable IP ranges that Kaseya's Discovery module doesn't recognize as valid.
I'm having the same problem. Has anyone seen or had this fixed?