Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'
This is almost always a Kerberos issue, due to an error somewhere along the way of setting up the SPNs.  See: Login failed for user &#39;NT AUTHORITY\ANONYMOUS LOGON&#39;. Reason: Token-based server access validation failed

One easy to make, but harder to find, problem is to have duplicate SPNs on your network.

If that might be your problem, read the following post to help you find the duplicate: http://blogs.msdn.com/b/psssql/archive/2009/02/13/searching-for-duplicate-spn-s-got-a-little-easier.aspx

A code snippet from that link:

setspn -q MSSQLSvc/mymachine.mydomain.com:1433 
CN=MYMACHINE,OU=Workstations,DC=mydomain,DC=com 
        MSSQLSvc/mymachine.mydomain.com:1433 
        HOST/MYMACHINE 
        HOST/MYMACHINE.MYDOMAIN.COM