• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 521
  • Last Modified:

SQL connection failing after changing windows built in domain administrators account

I disabled the built in domain administrator account in Active directory and now users cannot connect to a very important the SQL server application.  The application tries to establish a server connection on port 38113 and fails.  When I run the application locally on the server it fails with the error:
"socket connection failed (error code 10061)"
If I re-enable the ID and reboot the server, it works again...If I then disable the ID after that reboot, it continues to work untill the server is rebooted again, then it stops working.  I suspect a connection string needs to be modified somewhere but I don't know where and how to change it.
0
lanreo
Asked:
lanreo
  • 4
  • 3
1 Solution
 
lundnakCommented:
What userid are your SQL Server services configured to run under?
0
 
lanreoAuthor Commented:
MSSQLSERVER, MSSQLServerADHelper and SQLSERVERAGENT are all running under the Local System Account
0
 
lundnakCommented:
Local system gets its privileges from BuiltIn\Administrators.  I would recommend creating domain user to run the services as.

Following the steps in this blog.

http://www.sqldbadiaries.com/2011/02/02/restirct-access-to-local-system-administrators-on-sql-server/
0
Get 10% Off Your First Squarespace Website

Ready to showcase your work, publish content or promote your business online? With Squarespace’s award-winning templates and 24/7 customer service, getting started is simple. Head to Squarespace.com and use offer code ‘EXPERTS’ to get 10% off your first purchase.

 
lanreoAuthor Commented:
I've done all the steps in the blog above except removing the "Builtin\Administrators" group from Systems admin role in SQL, I even rebooted the server and I still have the same problem, the client application still does not connect.  I have a feeling there's a file somewhere on the server where it's hardcoded to use a certain "domain\userid" to connect.....please help !!!
0
 
lanreoAuthor Commented:
I figured out the problem; the SQL client application was running under a service account that was using the disabled ID....I changed that ID and all worked fine, thanks for your help all the same ..
0
 
lundnakCommented:
Good deal.  I didn't think about checking the client settings.
0
 
lanreoAuthor Commented:
The hints you gave me led to my finding the solution for my issue
0
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.

Join & Write a Comment

Featured Post

Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now