Unable to download Wireshark Patches WIRES34-201221 and WIRES32-201221


Article ID: 207230


Updated On:


Patch Management Solution Management Platform (Formerly known as Notification Server) Patch Management Solution for Windows


We are unable to download Wireshark Patches (WIRES34-201221 and WIRES32-201221) using the Altiris console.  Customer checked with firewall team if any port is blocking the download from the Altiris Console but everything is fine from their end. We are able to access the download link via browser from our computers and the SMP. 

We were able to use the PSPing command (included with Sysinternals PSTools) to validate customer has access to 2.na.dl.wireshark.org, and can download the files from a Browser when logged into the SMP with the Application Identification account.
Previous URL was www.wireshark.org.  New URL is 2.na.dl.wireshark.org.  Previous updates were staged just fine on this SMP.


From the SMP Logs we found that the download failed for: https://2.na.dl.wireshark.org/win64/Wireshark-win64-3.2.10.exe

Error message: The request was aborted: Could not create SSL/TLS secure channel.


Patch Management 8.x


While the URL is the only thing that has changed programmatically, we suspect that this issue is environmental as our testing has shown that these packages are able to be downloaded and staged in most environments.  If you have other information that would help us resolve this issue for our customers, please contact support.

Workaround. Create a Software Package by Importing the Wireshark files as a new Software Package; then create a Managed Software Policy to deploy the Software Package, and finally create a Target of vulnerable systems.

Steps to complete the Workaround:

  1. Download the files to any computer
    1. The specific URL can be found in the SMP Logs for the patch you are trying to download, alternatively Google may be helpful
  2. Copy the file over to the SMP
  3. Use the Import Method to create a new Software Package
    1. See Page 39 of KB 175693 (Software Management Best Practices) for additional information and instructions
  4. Create a Managed Software Delivery Policy to deploy the package to targeted systems.
    1. See Page 77 of KB 175693 for additional instructions
  5. Create a Target of systems to deploy
    1. Pages 78 and 71 of KB 175693