Yes everything was working fine until a couple days ago when an upgrade was applied to Symantec BackupExec, which has its database (BEDB) on this SQL instance.
Recently we had the same thing happen in our SQL 2005 Cluster. If you attempt to connect to this instance via SSMS with windows auth, you get this error: