Link to home
Start Free TrialLog in
Avatar of lanreo
lanreoFlag for Canada

asked on

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.
Avatar of lundnak
lundnak

What userid are your SQL Server services configured to run under?
Avatar of lanreo

ASKER

MSSQLSERVER, MSSQLServerADHelper and SQLSERVERAGENT are all running under the Local System Account
ASKER CERTIFIED SOLUTION
Avatar of lundnak
lundnak

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of lanreo

ASKER

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 !!!
Avatar of lanreo

ASKER

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 ..
Good deal.  I didn't think about checking the client settings.
Avatar of lanreo

ASKER

The hints you gave me led to my finding the solution for my issue