Hi, I have a strange issue with some clients identifying and then using distribution points which are located in a different subnet as 'Local' and then trying to download packages from them, even though there is a local DP on their subnet. Looking in the cas.log on several clients I can see the following; Download location found 0 - \\ServerB\directory\0000003C\ ContentAccess 28/02/2011 09:05:03 4220 (0x107C) Download location found 1 - \\ServerA\directory\0000003C\ ContentAccess 28/02/2011 09:05:03 4220 (0x107C) In the LocationServices.log there is the following; Distribution Point='\\ServerB\directory\0000003C\', Locality='LOCAL', DPType='SERVER', Version='6487', Capabilities='<Capabilities SchemaVersion="1.0"/>', Signature='' LocationServices 28/02/2011 09:05:03 3148 (0x0C4C) Distribution Point='\\ServerA\directory\0000003C\', Locality='LOCAL', DPType='SERVER', Version='6487', Capabilities='<Capabilities SchemaVersion="1.0"/>', Signature='' LocationServices 28/02/2011 09:05:03 3148 (0x0C4C) We have one primary site, which has a site code of 000. Then in each branch office we have a secondary site server configured with a proxy management point. Thie secondary site server also acks as a distribution point. Each secondary site has a boundry set to link it to its own active-directory site. ServerA is the primary site server, ServerB is the secondary site server in a remote office. The IP of the client falls within the boundary of the secondary site. The client always seems to pick the server from the remote subnet (the primary server) to download it's package from. I understand that this could be a boundaries issue but I have checked that the subnet's for the sites do not overlap, however neither server/boundaries are configured as protected. According to http://technet.microsoft.com/en-us/library/bb632366.aspx "The order in which clients try to connect to distributions point is the following, first for distribution points marked local (if any) and then for distribution points marked remote: Distribution points on the same IP subnet as the client" So I'm not sure why it's picking up a DP and using a DP from a remote subnet - any help or pointers as to why this is happening would be great Thanks for reading Brian.

Any error on site system status or component ?Joy, Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Thanks for the response. Nope, no errors on either the primary site server or the secondary site server.

"The IP of the client falls within the boundary of the secondary site" I had the same issue, in my case The IP of the client doesn’t fall within the boundary of the secondary site, and was showing the error on distribution manager was unhealthy. 1. I would recommend you to have a look on the boundary setting once again. 3. Check if any firewall problem between secondary client and secondary site server. 2. Check the secondary DP server smspkg$ folder and smssig$ shared folder permissions, give every one full acess. Joy, Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hello - If you don't want the client to download the package from remote DP in my opinion there could be two things you can try. 1. Protect the all the DPs with the local boundaries. 2. Set the advertisement option ~not to run http://technet.microsoft.com/en-us/library/bb633047.aspx Anoop C Nair

Hi Joydeep, thanks for your response. Checking through the boundaries once again I have noticed that boundary is listed in two locations. The primary site server has SubnetB listed as a boundary and so does ServerB which resides in SubnetB. Both are configured as fast links - could this be why the client detects both DP's as local? In that it's boundary appears in both the primary site server and also the secodnary server that resides at the clients site and both are configured as fast? FYI - I have checked the folder permissions on both the SMSPKG$ and SMSSIG$ and Everyone does indeed have full control.

Hi you will always see all the boundaries on the primary as they re replicated up what you have to take notice of that you dont have them specified under both sites. Id suggest that you try move to ip ranges for boundaries instead of subnets to see if that helps. If you cant do AD Sites. As stated earlier I also encourage you to do protected DPs to sure that you dont get any "content roaming" scenarios you dont want to have. Regards Stefan Schörling Blog: Http://www.msfaq.se UG: Http://www.scug.se

Hi, After looking through the boundaries again it seemed one of the IP range boundaries had a typo which made it span multiple subnets, one of the subnets being the remote office. This boundary was associated with the primary site server so I've amended this to be the correct IP subnet range which will hopefully stop the clients in that site detecting the central site as local now. I've also protected each DP to stop these sort of things from happening again. Thanks for the responses. Brian.

Perfect glad it worked out !Regards Stefan Schrling Blog: Http://www.msfaq.se UG: Http://www.scug.se