SharePoint SSL handshake good but TCP RST with no content
I'm using SharePoint 2013 iApps setup for SSL offload. Using Wireshark on a tcpdump from browsing to a FQDN shows the SSL handshake finishing and a single application data packet followed by a TCP RST. The handshake is also validated using openssl s_client. After the handshake, I've tried a simple GET and a host specific GET (per the iApp monitor string). Both return errno=104. Fidder shows a raised exception 'Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host'. I believe both openssl and Fidder errors refer to the TCP RST. An alternate IIS iApp is setup in the same Partition/VLAN/Route Domain. It uses non-SharePoint web servers but in the same subnet. It is browsed by the same web browser and succeeds. This VIP resolves to web server peers from the same client. Is this typical of a SharePoint server with incorrect bindings or AAMs? Or, is there a network issue to debug? What is the best way to validate networking to SharePoint when bindings/AAMs are suspect?
Having to upgrade from v10 to v11 manually?
Hello everybody, I need to replace an old BIG-IP 1500 platform with a stronger and newer one, and now I’m facing a weird situation: The old one cannot be run with v11, the new one not with v10. Sticking to the askf5 best practice articles, I couldn’t find anything for such a situation. In DevCentral I found the /usr/libexec/bigpipe daol command and gave it a try: Well, I had to delete nearly all of the HA-configuration and a lot of other stuff because of error messages. After that, it proceeded some steps further but then ran into a segmentation fault. :-( So, is there any other way I could do a migration automatically? Converting it manually would be a life’s work… Thank you very much for your contributions!
