Good information, Phil.
But it begs another question ... if your Patch Manager server does not have Internet access .... how are you synchronizing the Patch Manager 3rd party updates catalog?
And just to clarify... both the Package field and the Download URL field must have valid values. The Package field will display only the installer filename; the Download URL should normally contain the URL of the vendor's official repository of that installer file. For a package that has a directly downloadable file, that would be the same URL that is populated in the "I do not have the package content" option's Download URL field. However, if you're working from a disconnected server, or with a locally generated binary file, then the Download URL can also specify a UNC pathname.
Yes, I was avoiding the detail for the sake of the lesson learned.
My infrastructure team (bless them) have very strict ideas about their servers and the internet.
I was able to get approval for synching and for downloading from certain sites which have rules set in our proxy.
The pain of trying to get other sites approved is so great that I think its easier to just download them to my PC and then manually attach the file to the patch.
Yes, I have observed this behavior also, but from a Patch Manager server that is connected. If I have to edit the package from Solarwinds to point to our network location, I had to change the location in both boxes. I am using drive mapping to specify location rather that UNC pathing.