Hello Tony,

For better assistance I would like to suggest you to please submit a support incident with that explanation.

Regards,

Did you get this figured out?

I can think of a few reasons why this might be happening.  
When you access the satellite from those tabs in the Core Console, your computer will attempt to connect to the streamlined satellite using the real name of the server.  Is this the same name that you use when you log into the saellite console from your web browser?  Or do you use a dns alias, the IP address or some other syntax? Take note of the URL that the core attempts to use - and then try to connect manually through a web-browser to make sure the name is resolvable.
Without more information, all I can do is guess, so...in order of likelihood, here are my guesses:
1. Your companies web proxy is intercepting the request. Try configuring IE to "bypass proxy for local addresses" and add the suffix of the satellites real hostname.
2. DNS name resolution cannot resolve the hostname that the Core console attempts to connect to - or it resolves to an incorrect IP address.
3. SSL is enabled but the console is still trying to connect with http to port 3466 which is blocked by the firewall?
4. There is a port number mismatch. Have you changed the default port that the satellite listens on or is it still 3466?

If you've already resolved the issue, would you mind updating this post with the root cause and solution so that others experiencing the issue might find the solution here in the forum? Thanks - and good luck!