Have you rebooted the web servers? The LSA caches SIDs, so it is possible
that it is just going off a cached value.
It is also possible that the domain controller your web servers are talking
to have not picked up the replication of the name change yet, so the remote
call to do the name translation is still returning the old name.
This should eventually fix itself one way or the other unless you didn't
change the name the way you think you did. For example, you could have
changed the UPN in AD and then logged in with the new UPN but if you didn't
change the sAMAccountName as well, ASP.NET would continue to show the old
sAMAccountName in the username.
Joe K.

Signature
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services Programming"
http://www.directoryprogramming.net
--
> Here is the issue: some user accounts were renamed in our Windows
> 2003-based Active Directory. These users successfully log in with
[quoted text clipped - 10 lines]
>
> TIA!
Usenet User - 18 Mar 2008 17:43 GMT
Rebooting the web server (not just IIS) indeed helped, thank you!
>Have you rebooted the web servers? The LSA caches SIDs, so it is possible
>that it is just going off a cached value.
[quoted text clipped - 10 lines]
>
>Joe K.