​@Sathiya.K 

What level of permissions scan account has on the Windows Server?

When you do the nslookup on the IP Address from the Discovery Agent server (Appliance or Resource Broker), Is it able to resolve the IP Address from DNS?

Good morning Kathiya,

Scan troubleshooting can be complicated, particularly if it’s a large scan with a number of endpoints and the scan is distributed across different discovery agents. I would recommend running a test scan against an individual endpoint from one discovery agent (Resource broker if you’re using Password Safe Cloud). Then you can look in the scan logs for the scan details, the Phoenix log in the log location (KB0018833 shows what logs to look at for what). You can start searching through the log file by scanned host name, but you’ll need to switch to IP address once Password Safe finds it. Walking through the log by IP address, Password Safe will attempt to perform a port scan to see what ports are open and then attempt to connect to the endpoint with the scan account selected. The logs will show what permission on the endpoint the scan account has if it successfully connects. If the scans only returned the IP addresses, I’m thinking the scan either couldn’t reach the endpoint and only found the IP address from DNS, or that Password Safe reports that all ports are closed on the endpoint (either truly closed on the endpoint or a firewall is blocking the traffic). If some scan data were returned, like hostname and operating system but nothing else, I would suspect the scan account selected didn’t have the necessary permissions.

TLDR: I suspect that the scan either couldn’t reach the endpoint(s) and only found the IP address from DNS, or ports are closed/traffic to those parts are blocked on the endpoint(s). I would start with testing the discovery agent(s)/resource broker(s) connectivity to the endpoints in question, starting with testing one endpoint.