CTM job (*) suspended

I'm trying to deploy Software Updates; specifically The 2007 Microsoft Office Suite Service Pack 2 to two laptops. They begin to download the package but stop at 85% and 87% respectively. I get an error message in the ContentTransferManager.log that says CTM job {B026F67E-C001-4FF2-827E-0A1BCDF151E9} suspended ContentTransferManager 7/22/2009 10:53:22 AM 3084 (0x0C0C). I can't find any information on this.
 
The crazy thing is that it worked fine on Friday and nothing that I'm aware of has changed since then.
 
Does anyone have any idea why I'm getting this and/or how to resolve it?
 
Thank you! Renee

http://social.technet.microsoft.com/Forums/en-US/configmgrswdist/thread/3b820c64-5748-4162-898a-9984fafbdea9

Thank you for your response, however, I have seen that link and nothing in it pertains to my issue. Any other thoughts?

I have the same problem.  This is working for me but need a better solution:
On the BDP, check the log ContentTransferManager.log
Find all the CTM job * suspended messages like this one:
CTM job {8D7502F9-552F-4B31-84A0-D6BAB8DBB3B6} suspended
Then filter the log for “Queued location request” and match that CTM job to a request ID like this one:  Queued location request '{1321A0A9-96D0-4623-BBF2-C5DBF52E4967}' for CTM job '{8D7502F9-552F-4B31-84A0-D6BAB8DBB3B6}'.
Then filter the job for that Request ID to get the package number, like this one:  Created and Sent Location Request '{1321A0A9-96D0-4623-BBF2-C5DBF52E4967}' for package CNT0049B
Then find the package and the server that put it onto the BDP and remove the BDP as a Distribution Point for that package.  Do this for every package that is suspended.  Wait however long is necessary for replication in your hierarch.  Then RDP to that system again, open the SCCM Client and initiate the “Branch Distribution Point Maintenance Task”.  Wait several minutes for the ContentTransferManager.log to log anything (you will see it first in PolicyEvaluator.log).  If no more suspended jobs then your free to add the package to the DP again… and again, wait for replication then initiate the Branch DP Maintenance Task and you should see it download correctly.
This consumes a lot of time but it works.
Also, make sure your IP Boundaries are correct and make sure your parent sites in the hierarchy have the correct package version.

Is it a BDP ? Is the DP in the boundary?

Yes, BDP.
I took out the subnet that I found and put in an IP Range since the company supernets.. regular subnets don't work in this case...
I've been chaning subnets to IP Ranges since MMS 2010 - we just have a LOT of them.
In AD they may have the range as /20 but within the layer 3 network switch they are routing vlans and they supernetted it.. or at one time it was a /24 but later revised to /20...
 
BDP's are nice when they work but I've got several of them that were goofed up at various times.
I think I have a working patern but my oh my it's tedious and time consuming...
 

yea there are couple of artilces on this site about staying away from adsites as bounderies. Yes BDP's suck. Replaced all of  mine (25) with DP server shares. At least those I can see what's wrong if/when they break.