Forum Discussion
mikeshimkus_111
Mar 01, 2012Historic F5 Account
Hi Joe,
Strictly speaking, you don't need to use the same cert for the serverssl profile that you do for clientssl/SharePoint server. You can use the default cert for serverssl since it's never used to authenticate a client; we only need to to guarantee that the BIGIP opens an encrypted "client" connection to the back end server. However that shouldn't be causing this problem, either.
I assume that since it works using a Performance virtual that you have correctly configured Alternate Access Mappings in SharePoint central admin. Remove any http, OneConnect, and persistence profiles assigned to the standard virtual server one by one to try and pinpoint the problem. I would also have a look at IIS logs or packet captures if possible, they may hold a clue to what's going on.
Mike