ok, now I have figured out how to add 1 subnet (192.168.0.x) but the 2nd subnet (192.168.9.x) will not add to "covered", it stays as "uncovered"....
and on day 2, it is back to "uncovered". Anyone? help?
To cover a subnet you need a computer with an IP address in that subnet with a sensor installed on it. Ideally this computer needs to be always on.
Possible thoughts for your covered/uncovered issue
- A sensor being assign an IP by DHCP in one subnet one day and the other subnet the next
- maybe the sensor is installed on a laptop
- maybe you have a single computer with two IP's one in each subnet
- Maybe its a subnetting issue on your sensor install
Are your missing subnets listed and active under 'Rogue System Sensor Status' in 'Detected Systems' in ePO.
Also your RSD policy only needs to be assigned to your 'My Organization' System tree so don't worry about that.
Well, to give you a little that may help. The EPO server has 2 addresses (192.168.0.8, 192.168.0.62), would that play in? As per the covered subnets section: I figured out if I go to policy catalog, and set the RSD, under interfaces I removed the check from "only listen on an interface..." and added my 2 subnets (192.68.0.x - in office, 192.168.9.x - remote offce through VPN tunnel). the last tab, detection" is a little confusing but I have set DHCP monitor to "enable". should I force the disable and set "do not report systems..."?
Finally, back to the "detected systems", The sensor helth has 1 - passive (was active yesterday).
ty for the reply.
The ePO server is not the scanner itself. The scanning is done by a separately installed piece of software (Deployed and managed by ePO).
What's not clear from your posts is whether you have a sensor deployed to the 192.168.9.x subnet.
I have 13 subnets each one a separate node on a routed WAN. In each subnet i have one PC nominated as a sensor. Each one has had the sensor software installed, so i have 13 sensors. Each one scans it's own subnet and reports any rogue devices back to my ePO server.
I don't use the subnet tab of the policy as each sensor just listens on it's default interface/subnet. I also have the DHCP monitoring set to disabled.
it may be that I do not have the sensor properly installed. (but then again, everything was in the green yesterday) I ma not worried so much about the 9.x network (only 2 PC's) but the local 192.168.0.x is not working.
seriously? 176 views and only 1 person has a suggestion? Anyone?
Perfect, that seems to have fixed it. Thank you. (although I am a little skeptical as I have done this before and it stopped working. I will keep you posted).