April 7, 2012 at 12:05 am
LOG file
2012-04-07 10:40:29.41 Logon Error: 17806, Severity: 20, State: 2.
2012-04-07 10:40:29.41 Logon SSPI handshake failed with error code 0x8009030c while establishing a connection with integrated security; the connection has been closed. [CLIENT: 192.168.7.32]
2012-04-07 10:40:29.41 Logon Error: 18452, Severity: 14, State: 1.
2012-04-07 10:40:29.41 Logon Login failed for user ''. The user is not associated with a trusted SQL Server connection. [CLIENT: 192.168.7.32]
2012-04-07 10:47:08.98 spid51 Using 'xplog70.dll' version '2005.90.2047' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required.
2012-04-07 10:47:12.01 spid51 Using 'xpstar90.dll' version '2005.90.2047' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
2012-04-07 10:51:15.44 Logon Error: 17806, Severity: 20, State: 2.
2012-04-07 10:51:15.44 Logon SSPI handshake failed with error code 0x8009030c while establishing a connection with integrated security; the connection has been closed. [CLIENT: 192.168.7.32]
2012-04-07 10:51:15.44 Logon Error: 18452, Severity: 14, State: 1.
2012-04-07 10:51:15.44 Logon Login failed for user ''. The user is not associated with a trusted SQL Server connection. [CLIENT: 192.168.7.32]
April 9, 2012 at 3:25 pm
sanj_love89 (4/7/2012)
LOG file2012-04-07 10:40:29.41 Logon Error: 17806, Severity: 20, State: 2.
2012-04-07 10:40:29.41 Logon SSPI handshake failed with error code 0x8009030c while establishing a connection with integrated security; the connection has been closed. [CLIENT: 192.168.7.32]
2012-04-07 10:40:29.41 Logon Error: 18452, Severity: 14, State: 1.
2012-04-07 10:40:29.41 Logon Login failed for user ''. The user is not associated with a trusted SQL Server connection. [CLIENT: 192.168.7.32]
2012-04-07 10:47:08.98 spid51 Using 'xplog70.dll' version '2005.90.2047' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required.
2012-04-07 10:47:12.01 spid51 Using 'xpstar90.dll' version '2005.90.2047' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
2012-04-07 10:51:15.44 Logon Error: 17806, Severity: 20, State: 2.
2012-04-07 10:51:15.44 Logon SSPI handshake failed with error code 0x8009030c while establishing a connection with integrated security; the connection has been closed. [CLIENT: 192.168.7.32]
2012-04-07 10:51:15.44 Logon Error: 18452, Severity: 14, State: 1.
2012-04-07 10:51:15.44 Logon Login failed for user ''. The user is not associated with a trusted SQL Server connection. [CLIENT: 192.168.7.32]
These happen when Windows Authentication fails. What is your question?
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
April 10, 2012 at 10:59 pm
what are the setting to avoid the authetication
or how to allow the windows authetication
Settings for SQL server so i can allow windows authetication and the authentication not failed
Thanxs for answer
April 11, 2012 at 8:30 am
sanj_love89 (4/10/2012)
what are the setting to avoid the autheticationor how to allow the windows authetication
Settings for SQL server so i can allow windows authetication and the authentication not failed
Thanxs for answer
All SQL Servers have Windows Authentication enable by default, and you cannot disable it.
I will need more information before I can help you resolve your issue.
Is it your desire to use Windows Authentication? If so, then it helps if your SQL Server and any clients are part of the same domain. Is that the case?
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
April 11, 2012 at 10:48 pm
how to check weather the client and server is the part of the same domain
in the Manage server utility there is no domain currently available where the SQL server Installed
The Windows Authentication is a requirement of the system
Thanxs for answer
April 12, 2012 at 10:48 am
sanj_love89 (4/11/2012)
how to check weather the client and server is the part of the same domain
For the client operating system follow this article.
For the server, since you've posted in the SQL 2005 Forum I'll assume Server 2003. Right-click "My Computer" and go to Properties. Look in the "Computer Name" tab.
in the Manage server utility there is no domain currently available where the SQL server Installed
Manage Server utility? Are you on Server 2008? If so, please confirm you are on SQL 2005.
The Windows Authentication is a requirement of the system
If Windows Authentication is a requirement then it is best for both computers to be joined to the same domain, or each in separate domains with a trust between them.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
Viewing 6 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply