Ports
Our environment is segmented by numerous firewalls.
Can you tell me what ports are required in order for PDQ Deploy to operate?
Is communication initiated as a pull, or a push from the repository?
1
Important Notice: On February 29th, this community was put into read-only mode. All existing posts will remain but customers are unable to add new posts or comment on existing. Please feel to join our Community Discord for any questions and discussions.
Comments
Communication is a push from the computer where the PDQ Deploy console is running as there isn't an agent on the target computer to initiate a pull. In Pro the pushes will be from the server where the Pro service is installed.
It uses SMB to communicate which uses the following ports:
UDP 137
UDP 138
UDP 445
TCP 139
TCP 445
In the Windows Firewall the "File and Printer Sharing" exception is needed.
Is there any way to get around having to add the 'LocalAccountTokenFilterPolicy' to the registry to be able to access Admin$?
Hi Adam,
I have a pro version of PDQ Deploy and I will catch infos of any workstation of a particular VLAN of my network.
I open all the ports you says in this post and I need the exception of the windows firewall, but I can't connect to the device.
With my server where I have the pdq sw I can do a ping to the workstations, but on the SW pdq I can't do a Heartbeat.
Can you help me on resolve the problem?
The most common cause of this is that the computer can be pinged by the short NetBIOS name but not the fully qualified domain name. Inventory will try to ping by the fully qualified domain name if it exists in DNS. What happens when you ping by the full computer name?
I have a problem on the DNS :-)
So how do we get this into a nice script that I can push out to windows 7 machines? I also use the Pro version.