Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Published : September 27, 2005
Depending on your network configuration, you may need to perform firewall configuration to enable communication between DPM, the file servers, and the domain controllers. To help with firewall configuration, Table 4.3 provides details about the protocols and ports used by DPM.
Table 4.3 Protocols and Ports Used by DPM
Protocol |
Port |
Details |
|---|---|---|
DCOM |
135/TCP Dynamic |
The DPM control protocol uses DCOM. DPM issues commands to the file agent by invoking DCOM calls on the agent. The file agent responds by invoking DCOM calls on the DPM server. TCP port 135 is the DCE endpoint resolution point used by DCOM. By default, DCOM assigns ports dynamically from the TCP port range of 1024 through 65535. You can, however, configure this range by using Component Services. For more information, see Using Distributed COM with Firewalls (https://go.microsoft.com/fwlink/?LinkId=46088). |
TCP |
3148/TCP 3149/TCP |
The DPM data channel is based on TCP. Both DPM and the file server initiate connections to enable DPM operations such as synchronization and recovery. DPM communicates with the DPM Agent Coordinator on port 3148 and with the file agent on port 3149. |
DNS |
53/UDP |
Used between DPM and the domain controller, and between the file server and the domain controller, for host name resolution. |
Kerberos |
88/UDP 88/TCP |
Used between DPM and the domain controller, and between the file server and the domain controller, for authentication of the connection endpoint. |
LDAP |
389/TCP 389/UDP |
Used between DPM and the domain controller for Active Directory queries. |
NetBIOS |
137/UD 138/UDP 139/TCP |
Used between DPM and the file server, between DPM and the domain controller, and between the file server and the domain controller, for miscellaneous operations. |