SOLUTION: DPM Service Failed to Start in a Timely Fashion

     After setting up a Microsoft System Center DPM 2012 SP1 server in my main network, I moved it to a remote location. However the DPM service world not start and gave me the errror and related Event Log entries:

DPM failed to communicate with DPMBACK1.mydomain.local.com because of a communication error with the protection agent (ID 53 Details: The service did not respond to the start or control request in a timely fashion (0x8007041D))

Log Name:      Application
Source:        MSDPM
Date:          3/21/2014 4:32:33 PM
Event ID:      976
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:    BACK1.mydomain.local.com
Description:  The description for Event ID 976 from source MSDPM cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:  The DPM job failed because it could not contact the DPM engine.

     After chasing my tail for a couple of days by trying to install the latest rollup packages (I was unable to because this requires the DPM service to be able to start...), troubleshooting SQL Integration Services, triple checking DNS and routing, NIC drivers, NIC teaming settings, replacing VSS dll's as I've seen in man other blogs, trousbleshooting Internet Access (as seen on technet), then out of frustration moving the server back to the main office (DPM started immediately...so the server is okay), etc...I found a simple registry key that fixed all of my problems.  Here's the instructions:

Apply the ServicesPipeTimeout registry setting: This registry setting helps avoid failures when installing DPM and DPM updates or after moving to a new network with more latency.

• Launch Registry Editor (regedit) and navigate to the following key:
• HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
• Click the Edit menu and select New and DWORD (32-bit) Value
• Type ServicesPipeTimeout (case-sensitive) for the name and press Enter
• Right-click the ServicesPipeTimeout DWORD entry that you created and click Modify
• Select Decimal
• Type 300000 in the Value data field and click OK
• Restart the computer

After restarting the server, then I ran the following command to cleanup the DMP database.

dpmsync -sync

SUMMARY: The new network must have had some extra latency...?