Migrate, Protect, and Forge network port requirements

  • 7920341
  • 11-Aug-2005
  • 05-May-2016


PlateSpin Migrate
PlateSpin Protect
PlateSpin Forge

Note : The list of ports are common for all versions of the above mentioned products.


The following ports are used during the discovery process:

22                TCP       SSH Port used when discovering Linux servers, Citrix XenServers, and VMware ESX 2.5/3.0 servers. (SSH is not required when discovering ESX 3.5, 4, or ESXi servers.)
443              TCP       SSL Port used to connect to the VI3 webservices when discovering ESXi servers.
135/445      TCP       For DCOM/RPC communication as PlateSpin utilizes WMI when discovering Windows based servers so that no manual configuration is required

**WMI (RPC/DCOM) may use TCP ports 135 and 445 as well as random/dynamically assigned ports above 1024. If problems occur during the discovery process, another alternative is to temporarily place the server in a DMZ (or temporarily open the firewall) for the discovery process only.

Microsoft has published technical articles on how to limit the port range for DCOM and RPC:
Using Distributed COM with Firewalls:

How to configure RPC dynamic port allocation to work with firewalls:

DCOM Does Not Work over Network Address Translation-Based Firewall

** Please be advised that the above has not been certified by PlateSpin.

After the servers have been discovered, the following ports are used during the conversion:

80       TCP - For HTTP communication between the PlateSpin Server and the source/target machines.
443     TCP - For HTTPS communication ( for version 11.x and above) between the PlateSpin Server and the source/target machines.  This is also the default port for the VMware Infrastructure 3 Web service.
3725   TCP - Default File Transfer port used between the source and target machine (For File based and VSS-BBT file transfers)
SMB (TCP 139, TCP 445, UDP 137,UDP 138) - File Transfer of the Take Control folder (i386) and files from the Platespin server to the source server.
135/445 TCP - For DCOM/RPC communication as PlateSpin utilizes WMI when taking control and rebooting the source server

**WMI (RPC/DCOM) may use TCP ports 135 and 445 as well as random/dynamically assigned ports above 1024.

Block-Based Specific Ports (Legacy - applies to Portability Suite 8.1.3/Forge 2.5 and below):

  • 9999 TCP - Required during block-level data transfer for initial communication between source and target.

  • 137-139/445 TCP – For Named Pipe communication between the source and the target. Along with the ports, File & Printer Sharing (see Q20979 ) & Client for Microsoft Networks (see Q21155 ).
  • 10000-100025 TCP - After the initial handshaking is done, another TCP connection from source to target is initiated. The source machine will use port 10000 + X (where X = drive letter ‘A’ to ‘X’), for example, the port for drive C is 10002, D will use TCP port 10003, etc. There is one TCP connection for every drive being mirrored.
  • ICMP (Ping) is also used between source and target servers.

For additional server discovery troubleshooting, see TID 7920291.