Discovery is running very slow

[SAI VENKATESH]

Hi Everyone,

When we are doing discovery it is taking so much time to validate one ip it is taking 43 minutes approx. not sure why.

And also other than that no other schedule is running.

Any inputs?

Thanks and regards

Sai venkatesh

[pavani_paluri]

Hi @SAI VENKATESH ,

You can do quick troubleshooting steps as below

From the MID Server, run:

ping <IP>
tracert <IP>
telnet <IP> 22

(or 135/445 for Windows)

Reduce credential timeout to ~30–60 seconds.

Run a Quick Discovery (Discovery → Quick → Single IP) with debug logging.

Check ECC Queue for long-running probes (shazzam, WMI Class, SSH Probe, etc.).

Look at Discovery Pattern logs if it’s pattern-based.

In most cases, this ends up being either wrong credentials cycling through with long timeouts or firewall dropping traffic without response.

Mark it helpful if this helps you to understand. Accept solution if this give you the answer you're looking for

Kind Regards,

Pavani P

[Prahlad Kumar]

Hello @SAI VENKATESH

Quick Diagnostic Test

To identify the scope, run these tests manually from the server that is performing the discovery:

1. Ping Test: ping <target_ip>

   · Should respond in milliseconds.

2. TCP Port Test: Use Test-NetConnection <target_ip> -Port 445 (PowerShell) or telnet <target_ip> 445 (Command Prompt). A responsive port will connect or fail quickly. A non-responsive port (dropped by firewall) will hang until it times out.

3. SNMP Test: Use a tool like snmpget. For example: snmpget -v2c -c public <target_ip> .1.3.6.1.2.1.1.5.0

   · This should return quickly, either with a result or an error.

If any of these manual tests hang for a long time, you've found your problem.

Next Steps:

Step What to Check Why It's Important

1 Protocol Timeouts in the scan policy A mistakenly high timeout (e.g., 100+ seconds) is the #1 suspect.

2 Credential Sets (SNMP, WMI) A long list of invalid credentials forces the scanner to try each one, waiting for each to timeout.

3 Number of Ports being scanned Scanning thousands of ports instead of dozens will slow things down immensely.

4 Enable Debug Logging The logs will show you the exact step (ICMP, SNMP, WMI) where the delay is occurring.

5 Concurrent Host Setting Ensure the scanner isn't processing just one IP at a time.

Start with the timeout settings and debug logs. This will most likely lead you directly to the root cause.

Thanks

Prahlad Kumar

[Bhuvan]

@SAI VENKATESH 

Refer below knowledge articles to troubleshoot

Discovery Slowness 

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1646026

ServiceNow Instance Slowness

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0517241

As per community guidelines, you can accept more than one answer as accepted solution. If my response helped to answer your query, please mark it helpful & accept the solution.

Thanks,

Bhuvan

[Bhuvan]

@SAI VENKATESH 

Did you get a chance to review this as I believe the information provided should answer your question

If my response helped to guide you or answer your query, please mark it helpful & accept the solution.

Thanks,

Bhuvan