How to adjust the Connection Retry Algorithm for TCP - SQL 2012 Mirroring Principle Timeout

This is our situation, we have SQL Server 2012 in a mirroring state. We get the following errors throughout the day.

• System.Data.SqlClient.SqlException (0x80131904): Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding -System.Data.SqlClient.SqlException (0x80131904): Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. This failure occured while attempting to connect to the Principle

We're positive it's not the code, and this error only occurs while trying to make a connection while our test DB is in a principle mirroring state. We're trying to narrow this down and we found the following blog mircosoft blog

Based on this posting on serverfault tcp timeout, in our test Windows 7 box, we tried to edit the registry setting for TCPMaxConnectRetransmissions. When we went to make the registry change, that value wasn't present so we made a DWord with the value of 10. However, this did not clear up the problem. I'm going to try and adjusted TcpInitialRTT to 1 to see if this will clear up the problem but at this point i'm looking for suggestions on how to handle the TCP connection timeout while mirrored. Turning up the applications connectiontimeout like suggested isn't an ideal situation because we have applications that run every minute that need to produce results faster than a minute. And a longer timeout will default this purpose.