How to fix these events: "Even ID: 17806, Event ID: 18452"?

aaltayeb
aaltayeb used Ask the Experts™
on
I had these problems before maybe there months ago, I didn't care for them. Now I'm tried to fix it but without any luck. Can you help me?
Find below the event number with the description of Event ID:

Source: MSSQL$SQLEXPRESS, Event ID: 17806.
SSPI handshake failed with error code 0x8009030c while establishing a connection with integrated security; the connection has been closed. [CLIENT: 192.168.1.10] .

Source: MSSQL$SQLEXPRESS, Event ID: 18452.
Login failed for user ''. The user is not associated with a trusted SQL Server connection. [CLIENT: 192.168.1.10]
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Top Expert 2013

Commented:
Sounds like you have a service or application running on  192.168.1.10 that is accessing the database with account for which the password was changed or expired.

Author

Commented:
So, what should I do?
Top Expert 2013

Commented:
If that is a possibility you need to figure out which account. You may find information in the event log records of the machine with address 192.168.1.10. See if there are any errors relating to denied permission.
Exploring ASP.NET Core: Fundamentals

Learn to build web apps and services, IoT apps, and mobile backends by covering the fundamentals of ASP.NET Core and  exploring the core foundations for app libraries.

Author

Commented:
What is SSPI handshake? From where I can fix it? What is the default login user? Can you guide me to the default account if I don't change anything?
Top Expert 2013
Commented:
SSPI has to do with SQL authentication. I am afraid I am of little help with SQL, though the following may be of some help:
http://sqlforums.windowsitpro.com/web/forum/messageview.aspx?catid=60&threadid=84680&highlight_key=y&keyword1=sspi

If not, you should have in the event log "SSPI handshake failed with error code ________". What is the error code?

Author

Commented:
It didn't fix the problem.
Top Expert 2013

Commented:
Is there an error in the event logs; "SSPI handshake failed with error code ________". If so what is the error code?

Author

Commented:
error code 0x8009030c
Top Expert 2013

Commented:
Sorry I should have noticed 0x8009030c from the original question.

If the Setspn utility utility from the link didn't work the only other thought I would have is I noticed in one post that this error can occur if the connecting computer, 192.168.1.10, has a computer name (NetBIOS name) longer than 15 characters.

Author

Commented:
From where should I change it? Can you explain moor please?
Top Expert 2013

Commented:
If you right click on my computer and choose properties, then the computer name tab, you will see the "full computer name" such as computer1.local If the first part, computer1, is longer than 15 characters they are suggesting you change it. To do so click the change button. Make sure this will not affect other functions within your network that may be using the existing name for connections.

Author

Commented:
I checked the name and I found that is only 6 characters.

Today I checked the problem and the problem was disappeared after I put TCP Port: 1433 to SQL Server 2005 Network Configuration under Protocols for MSSQLSERVER. However, now, I face a lot of new problems.
Thank you for helping and I will give one of your solutions as the "accept as a solution".

Author

Commented:
I found the solution by my own. And it gives new problems.
Top Expert 2013

Commented:
Yes 1433 would have to be open. Sorry I didn't mention that but I would have thought the service wasn't working at all if that were the problem.
Thanks aaltayeb. Glad to hear you were able to resolve.
Cheers!
--Rob

Commented:
didn't fix my problem

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial