Authentication errors on failover cluster

Question

Authentication errors on failover cluster

Lori-138565

Ten Centuries

Points: 1340
More actions
September 9, 2008 at 1:16 pm

#123505

We have a SQL Server 2005 failover cluster and about every 30 seconds the following error appears in the SQL Server log : 'Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.1.110.52]'. The client in this case is the passive node of the failover cluster. We rebooted the passive node and the errors continued to generate even while that node was rebooting.
There doesn't seem to be any performance issues, but I'm unsure why this error is being generated. Any ideas would be appreciated.
Thanks,
Lori

Viewing 6 posts - 1 through 5 (of 5 total)

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

Lori-138565 Ten Centuries Points: 1340 More actions · Answer 1

We're still experiencing these errors and I can't find anything online that explains them. If anyone else has experience with this, I'd appreciate it.

Thanks,

Lori

David Benoit SSC-Dedicated Points: 34562 More actions · Answer 2

Have you tried to find out what that client is that is referenced in the error? Seems like you should be able to get back to the machine that is trying to connect via the IP listed.

Let us know.

David

@SQLTentmaker

“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot

Lori-138565 Ten Centuries Points: 1340 More actions · Answer 3

The IP address of the client is the passive node of the failover cluster. That's what's making this confusing.

Thanks,

Lori

MANU-J. SSC-Dedicated Points: 31126 More actions · Answer 4

Please read about it with workaround on:

http://blogs.msdn.com/sql_protocols/archive/2006/12/02/understanding-kerberos-and-ntlm-authentication-in-sql-server-connections.aspx

HTH

MJ

Lori-138565 Ten Centuries Points: 1340 More actions · Answer 5

Thanks - I've seen that article and our sys engineer is looking into the spn issue. I still don't know why the passive node would be trying to access the virtual server - MSCS handles the heartbeat, no SQL Server. I'll let you know if that solves the issue, though.

Thanks,

Lori