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 documented in my blog

http://matticus-au.blogspot.com/2009/08/windows-2008-and-xplogininfo.html

Hope this helps someone else who comes across similar issues in the future.

Matt