Analyze the SQL Server ERROR.log if it contains the following entries:

2015-11-11 13:20:34.79 Logon Error: 17806, Severity: 20, State: 14.
  2015-11-11 13:20:34.79 Logon SSPI handshake failed with error code 0x80090302, 
  state 14 while establishing a connection with integrated security; 
  the connection has been closed. 
  Reason: AcceptSecurityContext failed. 
  The Windows error code indicates the cause of failure. [CLIENT: IP xxx.xxx.xxx.xxx]. 
  2015-11-11 13:20:34.79 Logon Error: 18452, Severity: 14, State: 1. 
  2015-11-11 13:20:34.79 Logon Login failed. 
  The login is from an untrusted domain and cannot be used with Windows authentication. [CLIENT: IP xxx.xxx.xxx.xxx]

The logs above show because DSM does not use NTLMv2 for SQL authentication by default. If you want to use NTLMv2, do the following:

1. Open the dsm.properties file.
2. Add the following line:

   database.SqlServer.useNTLMv2=true

3. Save and close the dsm.properties file.
4. Restart the Deep Security Manager service.
   If the issue persists, you may also need to restart the server.

If the issue still occurs after restarting the server, collect and send the following files to Trend Micro Technical Support:

• server0.log
• SQL Server ERROR.log
• msinfo.nfo of SQL Server and DSM Server