Jon Whitehouse wrote:
# /usr/sfw/bin/wget --no-check-certificate https://sunsolve.sun.com/patchdiag.xref --09:07:14-- https://sunsolve.sun.com/patchdiag.xref => `patchdiag.xref' Resolving sunsolve.sun.com... 192.18.108.40 Connecting to sunsolve.sun.com|192.18.108.40|:443... failed: Connection refused.
So we can rule out any problems with a SOA account or entitlement issues. Can you re-run the above command with "--debug" added and post the output?
Our firewall is open to allow all connections to *.sun.com so I'm putting all my chips on the certificate being my reason.
Certificates should be ignore when using --no-check-certificate. As for the firewall - with the new SunSolve release, you must allow connections to getupdates2.sun.com and a248.e.akamai.net as well, see:
http://sunsolve.sun.com/search/document.do?assetkey=1-9-240066-1 Martin.
