Open specific ports in your network so that the peer-to-peer clients can transfer metadata to the peer-to-peer server. If you have no group policies that block the creation of firewall policies, the peer distribution component installers create the necessary firewall rules.

Table 1. Messaging from Client to Server
Sending Component Receiving Component Protocol Port Description
Peer-to-peer clients Peer-to-peer server UDP 34322 After clients receive small messages, they acknowledge or reply to the server.
Peer-to-peer clients Peer-to-peer server UDP 34323 Clients send small messages to the server.
Peer-to-peer clients Peer-to-peer server UDP 34331 Large replies from clients to the server using Foreground Protocol.
Peer-to-peer clients Peer-to-peer server UDP 34333 Clients send large messages to the server using Foreground Protocol.
Peer-to-peer clients Peer-to-peer server UDP 34339 Large replies from clients to the server using Background Protocol.
Peer-to-peer clients Peer-to-peer server UDP 34341 Clients send large messages to the server using Background Protocol.
Table 2. Messaging from Server to Client
Sending Component Receiving Component Protocol Port Description
Peer-to-peer server Peer-to-peer clients UDP 34324 After the server receives small messages, it acknowledges or replies to clients.
Peer-to-peer server Peer-to-peer clients UDP 34325 Server sends small messages to clients.
Peer-to-peer server Peer-to-peer clients UDP 34335 Large replies from the server to clients using Foreground Protocol.
Peer-to-peer server Peer-to-peer clients UDP 34337 Server sends large messages to clients using Foreground Protocol.
Peer-to-peer server Peer-to-peer clients UDP 34343 Large replies from the server to clients using Background Protocol.
Peer-to-peer server Peer-to-peer clients UDP 34345 Server sends large messages to clients using Background Protocol.
Table 3. Messaging from Client to Client
Sending Component Receiving Component Protocol Port Description
Peer-to-peer clients Peer-to-peer clients
  • Same office
  • Parent offices
  • Child offices
 UDP 34324 After clients receive small messages from another client, acknowledgments and replies are sent to this port.
Peer-to-peer clients Peer-to-peer clients
  • Same office
  • Parent offices
  • Child offices
 UDP 34325 Clients send small messages to other clients.
Peer-to-peer clients Peer-to-peer clients
  • Same office
  • Parent offices
  • Child offices
 UDP 34335 Large replies from clients to clients using Foreground Protocol.
Peer-to-peer clients Peer-to-peer clients
  • Same office
  • Parent offices
  • Child offices
 UDP 34337 Clients send large messages to other clients using Foreground Protocol.
Peer-to-peer clients Peer-to-peer clients
  • Same office
  • Parent offices
  • Child offices
 UDP 34343 Large replies from clients to clients using Background Protocol.
Peer-to-peer clients Peer-to-peer clients
  • Same office
  • Parent offices
  • Child offices
 UDP 34345 Clients send large messages to other clients using Background Protocol.
Table 4. Messaging client to Client Broadcast
Sending Component Receiving Component Protocol Port Description
Peer-to-peer clients Peer-to-peer clients in the same subnet UDP 34329 Clients broadcast requests to other clients
Table 5. Data Transfer from Server to Client
Sending Component Receiving Component Protocol Port Description
Peer-to-peer server Peer-to-peer clients in the Central Office UDP 34760 Server sends content to clients using Foreground Protocol.
Table 6. Data Transfer from Client to Client
Sending Component Receiving Component Protocol Port Description
Peer-to-peer clients Peer-to-peer clients in the same office UDP 34760 Clients send content to other clients in the same logical office using Foreground Protocol.
Peer-to-peer clients Peer-to-peer clients in child offices UDP 34750 Clients send content to clients in child offices using Background Protocol.
Table 7. Data Transfer Control Ports
Sending Component Receiving Component Protocol Port Description
Peer-to-peer clients Peer-to-peer server UDP 34545 Clients send a control signal to the server for any large transfer using Adaptive Protocol.
Peer-to-peer clients Peer-to-peer clients in the same office, in parent offices, and in child offices UDP 34546 Clients send a control signal to other clients for any large transfer using Adaptive Protocol.
Table 8. Data Transfer between VESC, Server, and Database
Sending Component Receiving Component Protocol Port Description
VMware Enterprise Systems Connector (VESC) Peer-to-peer server UDP 34323 VESC sends messages for activation, health checks, application metadata to the peerto- peer server.
Peer-to-peer server VESC UDP 34320 Peer-to-peer server responds to requests from the VESC.