Login failed. The login is from an untrusted domain and cannot be used with Windows authentication.

Question

Login failed. The login is from an untrusted domain and cannot be used with Windows authentication.

DBAgal

Hall of Fame

Points: 3185
More actions
April 20, 2012 at 10:24 am

#254614

Windows 2003 R2 Enterprise SP2 x64
SQL Server 2008 SP2
At first, I thought it was an AD issue. Server guys checked and said no errors in domain controllers. I ran some reports for network errors/issues, didn't see any.
The error lasted for 5-10 minutes before correcting itself.
Saw this error message before the authentication one:
The client was unable to reuse a session with SPID ---, which had been reset for connection pooling. The failure ID is 29. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message.
Any ideas? I keep googling and not finding a definitive causes and resolutions.

Viewing 9 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic. Login to reply

Orlando Colamatteo SSC Guru Points: 182276 More actions · Answer 1

I have seen that happen when a Domain Controller is restarted. If the Domain Controller restarted was the one cached by your application server the authentication errors begin...and unfortunately the app server does not immediately go looking for another DC. As soon as the original DC comes back, or the app server looks to another DC, everything goes back to normal. I would ask the domain admins if they restarted any DCs around that time.

There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato

DBAgal Hall of Fame Points: 3185 More actions · Answer 2

opc.three (4/20/2012)
I have seen that happen when a Domain Controller is restarted. If the Domain Controller restarted was the one cached by your application server the authentication errors begin...and unfortunately the app server does not immediately go looking for another DC. As soon as the original DC comes back, or the app server looks to another DC, everything goes back to normal. I would ask the domain admins if they restarted any DCs around that time.

No, DC restarts either.

I've read that high network traffic might also be a cause...I'm not seeing anything on the sql server side, but maybe communication between app server and sql server was disturbed by high network traffic.

Any other ideas?

DBAgal Hall of Fame Points: 3185 More actions · Answer 3

I saw the same problem again today. Does anyone have any ideas or suggestions?

C64DBA SSC Veteran Points: 249 More actions · Answer 4

Do you run a dev environment on a different domain. If so, look there. You might find a machine has been imaged from production and placed in your dev domain. There may be a job attempting calls against the machine where you are seeing the errors.

DBAgal Hall of Fame Points: 3185 More actions · Answer 5

C64DBA (6/12/2012)
Do you run a dev environment on a different domain. If so, look there. You might find a machine has been imaged from production and placed in your dev domain. There may be a job attempting calls against the machine where you are seeing the errors.

No. Same domain. The problem is intermittent and random, and only lasts for a minute or two. If the situation you described was the cause, I would be constantly seeing error messages, right?

The application uses Windows Authentication and tries to login multiple times per second.

Thanks!