When restarting the InTrust server the "Quest InTrust Server" service fails to start with "Cannot Generate SSPI Context" error.
Caused by a delayed/slow initialization of a network interface during system startup.
General troubleshooting can be found in this Microsoft KB article:http://support.microsoft.com/kb/811889
From this MS KB this section proved to be helpful
Change the primary connection type from TCP/IP to Named Pipes on SQL server (2005):
1. On your SQL server open up the "SQL server Configuration Manager".
2. Expand out "SQL Server 2005 Network Configuration" and highlight Protocols for MSSQLSERVER.
3. Set Named Pipes to Enabled
4. Expand out SQL Native Client Configuration
5. Right click and go to properties on Client Protocols
6. There should be two enabled protocols, using the arrows move Named Pipes to the top of the list, hit apply and ok.
After this the Order should be 1 Shared Memory 2 Named Pipes 3 TCP/IP (as long as the numbers are correct the screen order doesn't matter), you will need to restart the "SQL Server (MSSQLSERVER)" service for these changes to take effect.
To prove that InTrust is using named pipes you can open:
SQL server management studio > expand Management > Activity Monitor > Right click and View Processes. You should see a column 5 from the right labelled "Net Library" and these connections should show Named Pipes and some LPC (local loop connections) with no TCP/IP.
If other databases are being hosted on the SQL server other than InTrust please test the changes above within a lab enviroment.