Troubleshooting DPM Agent problems can be tricky so heres a collection of ways to troubleshoot it.
- Technet Article for Troubleshooting DPM Agent
- Article on DPM Across TMG / WAN
- Quote from Steve Light:
DPM need to communicate via RPC/DCOM. Let’s test various connectivity between the DPM server and protected server. We’ll need to test basic connectivity, SMB, RPC, and WMI/DCOM.
The commands below need to be run from an administrative command prompt. It is a good idea to test from both the DPM server and the protected server. For testing the account used must be an administrative account on both servers.
Basic connectivity is tested by using ping. If ICMP traffic is blocked ping commands will fail but that is OK.
ping <protected server name>Next test SMB (file sharing).
net view \\<protected server name>Now test RPC and connectivity to Service Control Manager (SCM). This displays a list of services on the remote server when successful.
Sc \\<protected server name> queryLastly test WMI/DCOM. When successful this command lists some basic information about the remote server.
Wmic /node:”<protected server name>” OS list briefIf any of the tests after ping fail that may be where the problem is.
/Steve
- Another Suggestion from Marc Raynolds
The error you are getting on the protected server indicates that the agent cannot make an RPC connection to the DPM Server. Can you verify the protected server can communicate with the DPM Server onTCP port 135? You can test this using the telnet command “telnet <dpm server name> 135″ or download and use the PortQuery tool
- Another way to test DCOM here
- If its in a workgroup then this may be the solution
- If its a firewall issue you need to check that these ports are open (Sauce)
| Protocol | Port | Details |
|---|---|---|
| DCOM | 135/TCPDynamic | 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(http://go.microsoft.com/fwlink/?LinkId=46088). |
| TCP | 3148/TCP3149/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 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/TCP389/UDP | Used between DPM and the domain controller for Active Directory queries. |
| NetBIOS | 137/UDP138/UDP139/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. |
