Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
[Discovery - Shazzam] Shazzam not returning/running ports information intermittently (like WMI, ssh, snmp) - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • [Discovery - Shazzam] Shazzam not returning/running ports information intermittently (like WMI, ssh, snmp)
KB0745497

[Discovery - Shazzam] Shazzam not returning/running ports information intermittently (like WMI, ssh, snmp)


2829 Views Last updated : Jun 10, 2025 public Copy Permalink
KB Summary by Now Assist

Issue

Shazzam not returning/running ports information intermittently (like WMI, ssh, snmp)

Symptoms

During the discovery of large scale IP ranges, intermittently we might see that the Shazzam is not returning or missing some ports information like WMI (135), 22 etc.

Release

All

Cause

Sometimes if these MID servers are on slower networks, sometimes the port probes that are being sent out don't get returned in a timely manner (based on our default settings), and therefore don't get reported back to the instance.

Resolution

Method #1:

Use Discovery Behaviors to limit what port probes are used for certain scans. For example, if you are scanning Windows servers only in that IP range then set up Discovery Schedule to use behavior with "WMI only". So with this, it will send only WMI port probe to these target servers, which will help with the performance.


Method #2:

Use the Shazzam probe parameters (some specific) that you can add/modify that can help with the performance. 

One example to consider is to modify the parameter "shazzam_chunk_size" to use a smaller number such as "25 or 50 or some lesser based on your requirement" (default is "100"), this will help in slowing down sending and retrieving port probe results so that you get more results if some of these port probes take longer to return. Although this will slow down the Shazzam probe and take Discovery a little longer to run, you should get more consistent results. 

Another example, we can try increasing the value of the "GenericTCP_waitForConnectMS" parameter in the "Shazzam" probe. 
Currently, the default value is "1000" (1000ms = 1 second), however you can increase this value to a number like "5000" (5000 ms = 5 Secs) or "10000" (10000ms = 10 seconds) and see if this helps as well. 

 

Related Links

  • Discovery Behaviors
  • Shazzam probe parameters

The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

Attachments

Attachments

No attachments found

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.