Good topic, I've had to troubleshoot one of these before.

I'd like to add one more possible cause.

The SQL Server in Q was a test server on a physically seperate LAN.

The DOM Admins had called it "SLQ1".

They later renamed it to "SQL1", but renaming an object in AD is not foolproof nor as simpel as in NT, there are lots of places where it stays the same.

I'd trawled the KB and Google, I checked NTLM settings and timezones, no joy.

The clue lay in the Windows Event Log, lots of Kerberos ticket errors, and this pointed to duplicate object names on teh LAN. Renaming the server back to "SLQ1" fixed it.

The SID was the same for SLQ1 and SQL1 thus coudl not be resolved.

To rename the object they should have dropped it from AD, renamed it, changed the SID and then added back to AD.

Cheers

Shawn