Upgrade task sequence skipping locations and failing

I have good clients that work and clients that don't in the same deployment collection. Both clients can browse the http location using edge. Both clients are using the same boundary group. The TS deployment is set to download content locally before starting. A good client lists the files in the log and does not skip http location. A bad client does not even list the files from the location and just skips. The only difference with the clients is that they are in different IP ranges or ad site but in the same boundary group. It makes no sense why one client would skip and the other does not skip. Could there be any network internal routing rule preventing the clients outside my known network? Other os operating system packages work on other networks from the same DP so there should be no reason why this location does not when it is the same DP smspkg$ location.