IIS using unexpected (incorrect) Integrated Windows Login

This has just recently become a major problem for me because I created an app that uses the Windows login to access my intranet web tool. For some reason, it was accessing an admin account that I also use instead of my logged in user.

I found this really strange because I never put in the password. I tried to clear my cookies and rebooted my machine, yet somehow it retains my admin account.

I spent an hour figuring this out eventually giving up and worked on something else. Then somehow which seems almost randomly, I thought about checking the credential manager.

Solution

I use the credential manager to manage my user and password for different network solutions. At my place, they use a different login to access these resources for security purposes. I find it such a pain because a few applications are not designed for this scenario. I put in the network folder, user, and password so I thought this couldn't be the solution but I had nothing else to try.

I did notice on closer inspection that it changes the network path \\servername to just servername. I just removed the one related to my tool and suddenly my tool was working as expected again.

Buggish: Microsoft Web Outlook Cannot Send Message Error

 To no one's surprise, Microsoft has probably one of the worst user experiences.

Trying to send an email. Takes forever and returns an error that says something like "There was an error, please click here for more details." And the more detail returns:  "This message can't be sent right now. Please try again later."

Great, Microsoft, great.

I eventually figured it out. The issue was that I was tagging a private group. It was a group set up in my outlook with a bunch of people that I send to normally. This is separate from Active Directory because I don't have access and I hate dealing with admin support.

Buggish: MS Teams (Login issue)

I just used MS Teams yesterday with no issues for work. I come back today and now I get an error "We weren't able to connect. Sign in and we'll try again." on MS Edge. On most days, refreshing if web or reloading if Windows app will resolve this issue... but today it is not letting me in. Usually one or two attempts will bypass this.

It is not the same error with the Windows app version where I get that my corporate device is not compliant with corporate compliance. Go figure... it was working yesterday and nothing has been installed. And like the web, usually reloading will resolve this in 1-3 attempts... but today a no go.

And now I get a "We've run into an issue. Oops, something went wrong! Restart" error. Seems to be flipping between this error and the one above today.

On top of all that, MS Teams works almost perfectly on Google Chrome. It is again quite amusing to see that I also get the "... weren't able to connect..." error on Chrome but I can just continue to message and receive messages.

After 30 minutes of just refreshing the page, Teams on Edge started working. Also I did in that time was messaging people on Google Chrome, repeatedly refreshing Edge and repeatedly restarting the Windows app.