Ok so fixing this is obviously frustrating.  Really simple. Once you get back in as the sysadmin user.  Add another secondary sysadmin.  Give them all the rights and stop using this useless account.  

Problems seem to only occur during re-syncing between the host server and the fail-over server.  Three symptoms.  

1.  Time out and disconnects

2.  Apparent loss of admin passwords and the account acts totally locked out

3.  Popup windows (e.g. virus quarantine) allowing you to see the txt or header kicks back with a login screen.  Most of the time this is fixed by doing a refresh on the spool management page.   

 

I don't have any idea why this is such a problem and would love to know if anyone else can replicate the problem.  After adding secondary Admins have not had any trouble since.

And to add further to this idiocy I got locked out of my secondary account.  Logged in as admin - successfully to my shock and amazement.  Changed the password on my secondary account successfully, which by the way has NO place to enter a recovery email address.  Made sure to add the IP network to restrict access to my internal network only.  Saved again.  Logged out.  And still told me that my username and password were wrong.  Rinse and repeat.  The IP network restriction did not show up.  Carefully repeated.  Still would not let me log in.  Had to DELETE the secondary admin account and recreate at just to log in.  

Just wanted to provide an update on this thread... After reviewing this more with the Support Department, it was found that the administrator account logout was caused by the App Pool recycling too frequently. With that change, the issue has been resolved and are now working as expected.