PDQ Deploy and PDQ Inventory require both console and target computers have certain firewall ports open.
In addition, use of the Central Server feature will require an additional open port on the PDQ console running in Server Mode.
Firewall ports and exceptions are covered in the following:
The ports outlined in this KB are in addition to the normal ports open for such things as LDAP (TCP 389)/AD, Kerberos, DNS, etc. It is strongly recommended you do not disable or otherwise modify the firewall to block or impede the proper functioning of those ports.
The following open ports are required on the Windows Firewall (or any other firewall) for proper functionality of both PDQ Deploy and PDQ Inventory. If you can manage remote computers using standard Windows administration tools you should be set since we use the same SMB protocol:
PDQ Server and Target Machines
- TCP 445 (SMB)
Central Server Ports
- TCP 6336 (default for PDQ Deploy Central Server, may be changed to a different unused port)
- TCP 7337 (default for PDQ Inventory Central Server, may be changed to a different unused port)
Legacy Ports for PDQ Server and Target Machines
- TCP 137 (Only required for legacy SMB)
- UDP 137 (Only required for legacy SMB)
- UDP 138 (Only required for legacy SMB)
- TCP 139 (Only required for legacy SMB)
In light of recent ransomware attacks, it is important to note PDQ Deploy utilizes the version of SMB available in your network. In most cases, this will be the latest version, SMBv3, and will exclude SMBv1, which is the vulnerable version of SMB. SMBv1, is used by Windows XP and Windows Server 2003x, both of which are no longer supported by PDQ Deploy.
In Group Policy (recommended), the settings to open the ports above and ICMP are located in Computer Configuration > Administrative Templates > Network > Network Connections > Windows Defender Firewall > Domain Profile
Alternatively, you may also define port exceptions in Computer Configuration > Windows Settings > Security Settings > Windows Firewall with Advanced Security, but that is not the Group Policy location described in the examples below.
- Windows Defender Firewall: Allow inbound file and printer sharing exception
This setting opens UDP ports 137 and 138, and TCP ports 139 and 445. TCP 445 specifically is required for the IPC$ and ADMIN$ shares to be available, and the others are legacy SMB ports. Administrative access to these shares is required. (If using a local account to deploy/scan target computers, please see this article for additional configuration settings).
- Windows Defender Firewall: Allow ICMP exceptions
This rule allows a target computer to respond to ping requests. Ping is used by PDQ Deploy and PDQ Inventory to determine the Online status of a computer.
In the end, you should have something that looks like this (some additional objects have also been enabled):
- If you are enabling these rules on computers that are not members of an Active Directory (AD) domain then use: Computer Configuration > Administrative Templates > Network > Network Connections > Windows Defender Firewall > Standard Profile
- If the target machine is not a member of an AD domain, you may need to disable Remote UAC restrictions. Click here for instructions.
- PDQ products ping the Fully Qualified Domain Name (FQDN) of a target or console machine to determine if it is online.
Central Server can automatically create a Windows Firewall rule on the PDQ console running in Server Mode. The following is from the initial setup and is also available post-install via Options > Central Server, Change Settings. This is the window in PDQ Deploy (Inventory is nearly identical).
This is equivalent to the following command (PDQ Deploy):
netsh advfirewall firewall add rule name="PDQ Deploy" dir=in action=allow program="C:\Program Files (x86)\Admin Arsenal\PDQ Deploy\PDQDeployService.exe" enable=yes localport=6336 remoteport=6336 protocol=tcp profile=any
PDQ Deploy and PDQ Inventory access the internet to perform regular tasks such as update the Package Library, Collection Library, Tools Library, and System Variables (used in collections). In addition to these regular connections, PDQ products periodically check for program updates, package updates, license expiration information, and for notifications from PDQ.com (For example, webcast notices, beta notices, etc.).
In order for these connections to function properly, PDQ products will require access to the following external sites:
You can test these connections by using Google Chrome or IE/Edge (friendly error messages turned off):
- Go to https://aafiles.blob.core.windows.net - you should get an XML error page.
- Go to https://pdqlibrary1.blob.core.windows.net - you should get an XML error page.
- Go to https://secure.adminarsenal.com/Subscription/PackageLibrary - you should get a large XML document there outlining the Package Library.
- Go to https://secure.pdq.com/Subscription/PackageLibrary - you should get the same large XML document there outlining the Package Library from the previous test.
- Go to https://cfcdn.pdq.com - you should get an XML error page.
- Go to https://download.pdq.com/ - you should get an XML error page.
- Go to https://library.pdq.com - you should receive a "Welcome to Alexandria..." message.
- Go to https://secure.pdq.com/ or https://secure.adminarsenal.com/ - you should be redirected to the PDQ.com homepage.
Also ensure that you are not blocking any Cloudflare IP ranges as this will prevent successful connections to the Library content as well. These ranges may be found in the link below and are updated periodically.
Is PDQ blocking the traffic coming from my network?
Although rare, it is possible for requests coming from your network to be blocked by our firewall. If you go to one of the above URLs and get a screen that looks like this (see below), your traffic has been flagged as potentially malicious and has been blocked. If this happens to you, please open a support ticket and we can help!