Situation:
1. PBIRS is on Azure in IaaS tier.
2. It is necessary to connect to a VPN to access the PBIRS
3. When connecting via VPN using real hostname, we can connect via port :80 and port :443
4. On F5 we created a pool, and pulled a VIP to a subnet that does not require VPN.
5. Also create a friendly name for the service. Different than actual hostname. Easier.
6. When connecting through F5/friendly name, we can connect via port :80
7. We cannot, however, connect via :443 through the F5
We are eventually going to shut port :80 off, but obviously not until we can connect via :443.
Any idea of what is going on here? F5 engineer swears everything is good on here side. Is there a configuration item somewhere in the PBIRS that would rerquire the friendly name to be "registered" in some manner? For that matter, do i need a server certificate that uses the friendly name?
Any thoughts or clues would be gratly appreciated.
