SQL Server Connection Error- Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. (Microsoft SQL Server, Error: -2)

HI,

I am facing an issue on SQL Server, i am getting this error: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. (Microsoft SQL Server, Error: -2). But error is not coming everytime i connect. It gives me error sometime.

I have enabled all services added exception on firewall, disabled firewall.
Os is windows server 2008 r2, and SQL server 2208 r2 is database.

Server gives me following error:

Error: 18456, Severity: 14, State: 8.

Error: 18456, Severity: 14, State: 5.: Login failed for user 'sa'. Reason: Password did not match that for the login provided.
LVL 6
Mandeep SinghDatabase AdministratorAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

teebonProduct ManagerCommented:
Hi Mandeep,

Where did you receive this error, in an application connecting to SQL Server or from SQL Server Management Studio?
0
Mandeep SinghDatabase AdministratorAuthor Commented:
sq server managment studio and i am seeing this in sql server log.
0
teebonProduct ManagerCommented:
Hi Mandeep,

You are connecting locally? Any other users accessing this SQL Server?
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

Mandeep SinghDatabase AdministratorAuthor Commented:
i am connecting it through locally & remotely. It gives error on both.

also what i see is when i try to connect using IP, its throws error, but by . it works fine.
0
Vitor MontalvãoMSSQL Senior EngineerCommented:
Sounds like you didn't set the SPN for that SQL Server instance.
I wrote an article in my blog about that. Check if it can help you.
0
Mandeep SinghDatabase AdministratorAuthor Commented:
Hi Vitor,

this is default instance and single instance on that machine, then so SPN helps me. What i understand about SPN is :  client uniquely identifies an instance of a service. If you install multiple instances of a service on computers throughout a forest, each instance must have its own SPN.
0
Vitor MontalvãoMSSQL Senior EngineerCommented:
If you install multiple instances of a service on computers throughout a forest, each instance must have its own SPN.
That's right. Check the SPN and if not exist just create it. Should work after.
0
Mandeep SinghDatabase AdministratorAuthor Commented:
Do the services run as Local System , then it works fine.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Mandeep SinghDatabase AdministratorAuthor Commented:
none
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2008

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.