[RESOLVED] IIS (or Internet Explorer) using wrong user for authentication

At my work I have 2 logins, my main login "mike", and another one that we use to login into servers to manage applications, user "tech_mike"

On my machine I am logged in as "mike", I published the web-application to the server (through FTP). I RDP into the server using "tech_mike", and setup the application in IIS (create app, disable basic authentication and set windows authentication for the app)

Now when I want to test the application from my computer (user logged in "mike"), in the browser I type the link to the app http://server/app_name and it tells me that I am not authorized. In the logs I can see that it is trying to login as "tech_mike", even though the user that I am logged in from my computer is "mike".

If I try to open the app on my local machine (local IIS), it is using the correct user "mike"

If someone else (another developer, he has "tech_user" account also) opens the app on the server: http://server/app_name then he is able to login because it takes the correct user that is logged in into windows (not the "tech_user" account).

It seems only I have this problem because I connected through RDP (using different user) to setup the application in IIS on the server.

This is happening on all apps on the server that are using Windows Authentication, IIS (I think) somehow replaces my user "mike" with "tech_mike"

What am I doing wrong? how can I fix this?

Have you checked the security users in you application root folder?
It may not have i_usrs or network or...
I would have started there first, see if it works.
Else, maybe web.config settings will try to log as admin?...

It's been a year, and I finally figured it out!

The problem is that windows stores the login information in the Windows Vault:
Attachment 134225
I had to blank out part of the server names and part of ID names for security reasons obviously...

I clicked on "Remove from vault" on all of them, and the problem is FIXED!!

Now when I open any web application on any of those servers, it sees my logged in user instead of the user that I use to RDP into the servers.