Is the client machine DHCP client or static? If the client machine is DHCP then do you see the same issue on other subnets of same DHCP? If yes then I will suggest you to restart the RSD sensor service on DHCP server.
If static and you don't see RSD sensor service in the services window then please install RSD sensor on this machine.
If you restarted the service then you should go to that machine click on the McAfee Icon and then open the status monitor and hit collect and send props then open yoiur Rouge sensor interface and see if its there you can also go to that system under systems tree and submit a wake up agent to and wait for 10 minutes
Great i got to restart de service at the machine. Now, how do i make de ePO to see again? Do i need to resintall de Sensore again so it can see ti?
I think am getting the hang of this. I found a machine with the service, i restart it but nothing, then went to the epo tagged the machine and reintalled the sensor but still waitting after wakeup command. Do i have to delete it from the epo so it can discover it again? by the way that will be 1 machine. there are 484 more that are still in the missing state. thanks again for the help.
There is no need to re-install the sensor. Just restart the McAfee RSD service in the MMC services console. If for some reason it is still not talking after you run a collect and send props, then you should uninstall/reinstall the sensor.
If for some reason it is still not working, I would check your firewall and perhaps also uninstall the agent/all endpoints and reinstall.
After giving it sometime. I finally got them back. It was that we had move the server to a new location, the ip had change but not the policy. So i change the ip to the new address... Presto! there back. Thanks everyone for the help!
A reboot of the RDS service seemed to re-establish the link between the sensor and server (I initiated a collect and send) and after it passed info back to the server is went to passive and then to active within a few minutes.