Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We have a web based application on IIS6 that matches profiles to usernames based on what is returned via the authentication process. One of the user's usenames was changed in AD (and in the application as well to match). However, when they sign in now via Windows Authentication they are authenticated but not authorized since it seems that the old username is still coming back. When using Forms authentication the user has no problems logging in. We can not use Forms auth as a permanent solution.

Any idea if the username (samAccountName) is cached somewhere in the network, or on the local security authority on the server? Is there a way to clear this? Any other ideas as to what the issue may be?

share|improve this question

It's cached on the local IIS machine, but I don't remember where.

I can tell you that it's cached in a location that survives Worker Process recycles, though, so you'll either need to try IISReset (I never usually recommend that, but there you go), or reboot the box.

share|improve this answer
Thanks for that. I did recommend already to reboot the server. Unfortunately, it is a system critical server with many apps running there. So I was hoping to run some sort of command that would clear the appropriate cache. – Tim Aug 18 '11 at 17:00

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.