RSD sensor not reporting back: which could be?

• A. Deployment failed
• B. Sensor service disabled after install
• C. Network issues
• D. Unable to resolve IP

Answer: (D)

Not being able to report back usually points to a failure in reaching the ePO server, and the most decisive cause is DNS—the sensor can’t translate the server’s hostname into an IP address. When DNS resolution fails, the sensor has no destination to send data to, so no reports ever reach the server, even if the service is running and the network is otherwise fine.

Deployment issues or the sensor service being disabled after install imply problems with the sensor’s presence or its ability to run, which would show up as installation or service-status symptoms rather than a pure DNS failure. While real network problems could also stop reporting, they typically don’t explain an inability to resolve the server’s address itself.

To troubleshoot, verify DNS resolution from the sensor host by resolving the server’s hostname (for example, using nslookup or dig). Check that the configured server hostname is correct, that DNS servers are reachable, and that nothing like a firewall or hosts file entry is interfering with name resolution.