Let me know if you can help, I am looking for a solution without a major
upgrade or rebuild.

I setup a secondary site with IIS on one of my Domain Controllers in
Johannesburg.  The SMS Advanced clients do not talk to this server JOH-File1
as a local distribution point but instead go back to my primary server
cam-sms1 as a remote distribution point to get their packages and
advertisement distribution accoring to the locationServices.log and network
tracing we have done. this occurs on all the clients assigned to that DP / AD
site IP range and Local boundrys 10.110.1.0.   Just started happening over
the past few weeks.   Because of a slow link  to the site the bandwidth on
the AD site is maxed out when packages are deployed either from the DP (all
remote from the primary SMS server in Boston)or downloaded and installed to
the clients at that site.  No Advertisements  run from the Local Distribution
as in other sites we have setup worldwide.

I have tried a clean uninstall re-install of the site using the same site
code and still not working.  I have made sure IIS 6.0 on Server 2003 has BITS
and Webdev turned on with active server pages.  Checking the
locationServices.log for the clients and they do not see the local JOH-File1
Distribution point only the primary site server as a distribution point
cam-sms1  as remote.  

I watch the DataTransferlService.log and the packages download from only the
primary site.  This behavior is the same on the Joh-file1 server itself when
a package is sent to it as a client -  the advanced client of the DP seems to
work properly.

On the secondary child site joh-file1 the dismgr.log  has the packages
loading to it no errors after teh reinstall

On my SMS Primary server the settings for the site JOH-file1 secondary site
are correct and just like the other 12 sites that work.  Software
distribution is checked with an administrator account assigned.  The Site  
boundaries for the secondary site Joh-file1 are set properly for the IP range
that the clients are using.    There is a need for Roaming boundaries for the
site and they are designated as Local Roaming boundaries.  Site properties
for Joh-file1 has the Distribution point role checked with BITS Enabled.  The
system is set as a Management Point and that had installed properly.  

I have tried making the site a protected distribution point and still the
clients do not use it.  All the advanced clients assigned to the JOH site
including the server itself go back to the primary server for software
distribution.

What other logs can I check?   Why is this site not acting like a
Distribution Point?

What can I do to fix this?