Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SQL Stopped Accepting Connections

Status
Not open for further replies.

qsac

Programmer
Jan 22, 2002
242
US
RE: SQL 2005 on Windows 2003

Just had a really weird issue, so reaching out if anyone has seen this before.

Have a SQL server on a domain, using Domain Accts to run the services. I had to move the Domain Controllers to another Colo room. When I turned them off, the SQL server stopped taking SQL connections. SQL did not restart, it was just showing Login Failures. As soon as the DC was back online, all was good. Again, i never restarted SQL or anything.

The login requests were SQL Users, not domain users.

All was working good before the move, all is still working good after the move.

Any Thoughts?

Q
 
I would assume that it failed the logins because it couldn't validate the domain password policy against the domain controller.

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

My Blog
 
Denny

that has to be it. thanks so much.

I never knew that it would check the policy at every login. To me that is overkill. it should only be checked on password change. But what do i know.

Thanks for the help
Q
 
It has to check the policy for password expiration at each login.

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

My Blog
 
It might also be a difference between Server access and SQL Server access.

The domain controller controls access to the SERVER. Since it was offline it could not verify that the user had access to the server. Once it was back on, it could confirm the user had access to the server and then passed the SQL Server login through.

Example. My servers are part of ABC domain. If the domain controller can't confirm that a user is part of that domain, it won't allow them to connect to the server. That means they can't connect to the SQL Server instance even using SQL Server authentication.

-SQLBill

The following is part of my signature block and is only intended to be informational.
Posting advice: FAQ481-4875
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top