There's not a way I'm seeing to extend a timeout for how long LDMS waits before timing out on this area. If the patches are taking a while to initiate a connection and download when done through a browser, that's likely what LDMS is running into. A work around if it's only a small # of patches is to manually download them via a browser and put them in the patch repository, at which point LDMS will have access to them for patch repair jobs.
Hi, thank you for your input.
I have been meaning to update this thread as issue is resolved.
We needed full access via our Proxy as opposed to whitelist as we go access which was previously setup. I don't manage the proxy so don't know how it is configured.
But in a nutshell it was an issue with our own Proxy and now I am able to download most patches.
What is still an issue is the "skipping manual" patch download, and I seem to have problems when deploying batches of patches to multiple machines at once and half get stuck - but this is another issue and I am looking for some Patching Best practises to try and get a better understanding of what's best suited to our environment.