You have already made sure that the firewall rules are not blocking this? Can you see the request going through the firewall?
BTW, You can no longer get directly to the content site via IE, but now use..
The PatchAnalysis config is still: - http://content.patchlink.com/bladelogic/
As soon as the Patchlink site is back up, I haven't been able to connect with any link, I will ping on my network people to trace my requests and check their ACLs.
Has anyone heard any update on the patch site??
Also, check to see if the proxy server being used requires authentication. I had an issue with this and the only work around is 1. have a linux/unix proxy server or 2. Have them allow the BladeLogic app server a direct connection to the internet to bypass the proxy. I built a linux proxy server.
No, I checked with our comm /network people and no authentication is required. Another question I have is does anything special need to be configured in the IE browser that the appserver is installed on? If I am using a http proxy, does the appserver need to know that in the internet setup? I have SET the proxy address and the port in the appserver admin but it does not seem to be using it.
I had this same problem before the patchlink URL change but at least I was able to access the content through a regular browser session. Now I can't even use that for a test and I cannot ping cdn.patchlink.com, which I read was test for connectivity.
I have requested a hole be punched through our base firewall for the new IP, but port 80 traffic is blocked and rerouted through the proxy server, so... still looking for tips and tricks.
What OS and version is the BladeLogic appserver?
Try this: Connect to the app server and setup a browser to use the same proxy as is configured in blasadmin ( HTTPProxyName:cits-pr.tinker.af.mil & HTTPProxyPort:8080 ). In IE, the setting is in Tools | Internet Options | Connections | LAN Settings | Use a proxy ... Again, this configuration should be done on a browser on the appserver.
Then see if you can browse to the following URL (case sensitive):
If you can access that URL from a web-browser on the appserver without proxy authentication, then we have a BladeLogic challenge, otherwise it is a networking / proxy question.
I did as you suggested and I can browse to the URL with the appserver browser.
I get to the index.xml
I have been trying to use the WGET command, as I did once, but can't hit on the magic combo again so far.
You have given me a new direction to go.
In addition to the above psot from about using a proxy, I also have this issue;
I am trying to use wget since our base uses a proxy which, for some reason, Bladelogic will not either recognize or deal with in the config file for the appserver. After setting the proxy manually, I use "wget -r http://content.patchlink.com/bladelogic/windows/x86/en/" which continues to give me a Forbidden 403. I can download the Index.xml file with no problem using the same format as above but no luck when I try to download the rest. I can browse to the Index.xml URL but that's about it.
BL v7.2 and Win2003
The website that delivers content has been modified to deny the browsing of directories.
http://content.patchlink.com/bladelogic/windows/x86/en/ will not work from a browser, you need to add Index.xml. However, the pacth configuration should still be http://content.patchlink.com/bladelogic/windows/x86/en/
I agree. I can put http://content.patchlink.com/bladelogic/Index.xml on a command line with wget and it will download the Index.xml, no problem. I cannot, however, continue on with a wget command of http://content.patchlink.com/bladelogic/windows/x86/en/ because it will come back with a 403 Forbidden, even though the first command for Index.xml worked correctly. Am I missing something on the second command?
I was fully successful on the command line before the content website was modified.
You are correct, that is the case for everyone. Patchlink has disabled the browse functionality for everything except for index.xml
That I understand. My issue is that I can't download anything from the Patchlink website using WGET other than the Index.xml.
Why am I still getting a '403 Forbidden' when I try to WGET the actual files, as I was able to do before the site was rehosted?
I can get no patch updates through the CM or from a command line using no internet access methods.
OK, maybe the current version of BL doesn't like to play nice with a proxy. Network sniffer never saw atempt to use the proxy even though it's in the config.file
Solved my dilemma by adding an ACL in our base's firewall and all comes through now.
Thanks to all who answered.