Just something I have found in my own situation.

This is more likely to be caused by changes in Windows 2008 rather than any changes to SQL server.

My scenario is...

I've come across a similar issue which I have found is caused by changes in the security of Windows 2008 (specifically the API calls used to perform domain lookups). Given...

I know this post is pretty old but it was most likely due to a security update for Kill Bits released by MS and then fixed with a subsequent security...