Had a similar problem some months ago with renamed Windows accounts.

http://www.sqlservercentral.com/Forums/Topic1328455-1550-3.aspx#bm1352733

After banging our heads against the proverbial wall for a week, we stumbled upon the solution: re-boot the SQL Server.