So how did I solve this issue? It is actually mostly straightforward, if you are allowed to do it. I had talked to my company's Check Point administrator, and he informed me you could disable the security policy that is enforced by SecureClient, but that was only because they allowed people to do it. Click on the SecureClient icon in the menu bar, then Tools, then Disable Security Policy.
What does this do? Well the configuration is completely dependent on your company, but mine blocks most inbound connections to your machine, including all the Bonjour stuff. My firewall admin thought you would only have to click DIsable Security Policy once when SecureClient is first loaded, but I have found that I have to click it every time I make a VPN connection as well. That is annoying, and for anyone that doesn't know the Disable Security Policy trick, all Bonjour related functionality is broken. This is actually what most firewall admins want, they want to enforce some kind of control over your machine outside of the corporate network, this is clearly another way to do it. If firewall admins wanted though, they could make sure Bonjour/Rendezvous always work. The following Q&A is in release_notes.pdf distributed with SecureClient (not they still call this Rendezvous):
Q9: How can I use Rendezvous after applying a block inbound desktop security policy? Q9: Block inbound desktop security policy doesn’t allow incoming connections to your desktop machine. Rendezvous requires IP multicast traffic to function properly. To support Rendezvous, add a desktop security rule above the block inbound rule: Source: (IP: 22.214.171.124-126.96.36.199, 188.8.131.52-184.108.40.206) Dest: All_Users@Any Service: Tcp, Udp Action: Accept This will allow the necessary incoming multicast connections for Rendezvous.