Required Ports for Veeam Certificate-Based Deployment (Windows & Linux)

By Gaurav Tevathiya Principal AI/ML, Cloud & Data Architect

Certificate-based deployment in Veeam requires proper network communication between the Veeam Backup Server, proxy/mount server, and the target machine. If required ports are blocked, deployment, restore operations, or installer communication may fail.

Common Ports (Windows & Linux)

These ports are commonly required for both Windows and Linux targets:

Port / Protocol Purpose TCP 6160 Veeam Installer Service TCP 6162 Veeam Data Mover TCP 443 HTTPS / certificate checks / cloud integration TCP/UDP 53 DNS resolution (if hostname is used)

Note: These ports should be allowed bidirectionally between the Veeam server and the target system.

Windows-Specific Ports

For Windows-based deployments or restore targets, the following additional ports are important:

Port / Protocol Purpose TCP 135 + Dynamic RPC PortsInitial remote communication / service control TCP 445 SMB file copy / installer package transfer TCP 5985 / 5986 WinRM communication (if used)

Why these matter: Windows deployments rely on RPC and SMB for remote service installation, package transfer, and control.

Linux-Specific Ports

For Linux targets, requirements are slightly different:

Port / ProtocolPurposeTCP 22SSH access for initial management / deployment

Important: Linux systems generally do not require SMB (445) or RPC (135) unless there is a specific integration or custom setup.

Best Practice Recommendations

To avoid deployment or restore issues:

• Allow all required ports bidirectionally between Veeam components and target systems.
• Configure firewall rules properly.
• Add Veeam processes and folders to antivirus exclusions.
• Verify DNS resolution if hostnames are used.