It was found that the Browser made use of a Proxy Server.
In this case the Admin Console also needs to be setup to use the proxy server.
1/ Ensure that the webgtw probe has been deployed to the Primary Hub. This is where the wasp probe hosting the admin console webapp runs.
2/ Configure the webgtw probe to specify the proxy server/port/credentials
See Configuring webgtw Step 3. http://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/it-operations-management/ca-unified-infrastructure-management-probes/GA/alphabetical-probe-articles/webgtw-web-gateway/v8-0-webgtw-ac-deployment-and-configuration.html
3/ Open the Primary Hub wasp probe in Raw Configure..
Expand section webapps -> adminconsoleapp -> custom -> uncrypted
and edit the webgtw_address
Specify the full path to the webgtw probe (Domain/Hub/robot/probe) and save
4/ Deactivate/Activate the webgtw probe. Once that has a port/pid deactivate/activate the Primary Hub wasp.
Check/Confirm if Admin Console now has connectivity to the web archive.