PAM Device Discovery throws error (nmap)
search cancel

PAM Device Discovery throws error (nmap)


Article ID: 258481


Updated On:


CA Privileged Access Manager (PAM)


Trying to leverage Device Discovery embedded in PAM platform.

Following the directions from this URL:

I configured a scan to look for windows 2019 servers in two subnets - and

The only other configuration I added was Access Methods where I selected RDP (3389)

When I run the scan and navigate to Discovery Jobs it simply returns error under Status.

How can I find what the error might be?


Release : 4.x


There are several possible reasons for the network scan to fail.

1. a timeout due to slow network connectivity

2. firewall preventing access




Troubleshooting the specific reasons for the failure can be difficult based on what is returned but you can replicate the responses that PAM receives by issuing the same Linux command we use to search the network.

nmap -T4 -A -oX - -p 22,3389

Additionally you can try smaller network segments as this process can take an extremely long period of time.