Score:0

IIS windows authentication loop

ru flag

We star to move from windows server 12 to 19, the server is already working and we set our balancer to only use the new two nodes. The serves are register under our intranet AD ou cert. the sites use windows authentication so the iis handle it and the browser request and authenticate the users of the same ou without a problem, also works if the user use a VDI resgister on the ou callcenter. But when a user of the ou carwash try to loggin to the site, the browser never authenticate the user, and get stuck requesting over and over the credentials.

I review some similar question about modify the register but the old server not have any of this entries. The only different y found was the allowusernullsession disable in the 2019 server, in the old one do not exists.

I setup the iis by export and import the iis configuration from the old server to new one.

The user us FQDN to access the server, also tried using ou\username, username only, [email protected]

Enable the fail request logging and the user name is get correctly but the iis response 401

We already write the password in notepad to copy&paste, and fails, but works on the old server.

The applicationpool use it’s own domain user. Any advice?

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.