clients suddenly don't install sms packages

I have a group of clients that suddenly won't install packages.  They are all in the same general vicinity, so I checked boundaries.  I noticed that it hadn't been updated (they had recently been resubnetted and got put into a new AD site), so I updated the boundaries with that new AD site, but that didn't seem to help.  They are getting the 10035 message, indicating it isn't running it yet and may need to download.  The execmgr.log is littered with the "content available igonring update with no DPs for content request ID" messages, and the CAS.log is getting the "no matching DP location found" message.  Therefore, it's not finding the DP, but the DP is updated with the package, as other machines are getting it from the same DP.  Therefore, I assumed it was an out of boundary/remote dp location issue, so I set the advertisement to download if no local DP was available, but the DP has always been available, but now suddenly it's not.  The download from remote DP option didn't make a difference.  This is occuring on about 30 machines.  I have run out of ideas.  Can anyone offer any suggestions?  Thanks.

wanted to add some more info.  went to one of the clients today and tried a repair.  no luck.  uninstalled and reinstalled the client, and the smscliui.log generated errors about not being able to find the site.  when i try to auto find the site, it fails.  finally entered the site and stuff started populating the logs, etc., could find the mp, and such, but when I send an advertisement, it STILL can't find the DPs.  I scanned sites trying to find things, and it all points to the boundaries, but I have checked and re-checked and re-checked again, and the boundary settings look good.  it is this one ad site that having the issue, though.  I looked in AD sites and services and the subnet matches up with the ad site information, so it's not that.  I was tempted to put the subnet into the list of protected DPs to see if that would help, but if the subnet matches the site, that would be redundant.  I thought it might also be a timing issue, as that site was not previously added to the list of protected DPs, and the boundary list in the primary (it's a fairly new site), but it has been two weeks.  it should be finding DPs by now.

The follwoing SCCM 2007 link might be useful... just a thought. Not sure if this will applicable for SMS 2003.

http://blogs.technet.com/configmgrteam/archive/2009/12/21/known-issue-supernets-in-active-directory-sites-used-as-site-boundaries.aspx

http://blogs.technet.com/configurationmgr/archive/2010/03/22/clarification-on-issues-resulting-from-the-use-of-supernets-in-configmgr-2007.aspx

I'm having the same issue. Did you find the resolution?
Thanks!