users cant connect to sql server "Connection Failed SQL State 08001"

This is an existing installation that was working.  We had this problem on Friday and restarted everything thing and it was ok.  It has happened before on restarts.

I can connect to the sql server by name on sql studio mgr from the same machines.  BUt the MS Access App throws error:

SQLState: '08001
SQL Server Error: -1
[Microsoft][SQL Server Native Client 11.0] SQL Server Network Interfaces: Error Locating Server/Instances Specified[xFFFFFFFF]
Connection Failed:
SQL State: 108001'

Again this was all working this morning and for years before.

error screen shot
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

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.

there are several reasons that could occur

I have an excellent article that would run through the most common instances with step by step fixes.

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
pressMacAuthor Commented:
OK, the server on which the SQL Server resides is a domain controller.

I had already rebooted that.  Then for the second time, i rebooted the other domain controller.

Then everyone was able to login.

However, i would like to identify the problem.  Some sort of named pipe issue i am figuring.

It is working now, but per the above document, i am able to ping the server by ip and name, but not instance.

Vitor MontalvãoMSSQL Senior EngineerCommented:
Domain controller should remain as is and not for others purposes.
Imagine that SQL Server needs to connect to DC but isn't available yet in the time the service starts? It would be never able to be available.
You should think in removing SQL Server from DC server and install it in another machine.
pressMacAuthor Commented:
I never actually figured out solution to the problem aside from multiple re-bootd.  I think the sql server tries to get going to be all the dns is in place or something like that.  For that reason i also award to 250 to Vitor for the suggestion to move the sql server to its own machine.
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 Access

From novice to tech pro — start learning today.