I ran into the same issue. I noticed I had an extra network interface enabled under the Network tab so I turned it off and NTLM started working. I'm not sure if it was the setting or just changing something on the network setting in general reset something, but it worked.....kinda. Now I had ramdom users getting "authentication required" prompts on random pages. A refresh loads the page, but it is still frustrating. Seems 220.127.116.11 is buggy to me. I open a ticket and will post back if I get any answers.
Thanks for the update let me know if you find out anymore, network interfaces didn't work for me still trying to get NTLM working
I just set up a 18.104.22.168 Build 8022 and tried NTLM Authentication (native). It worked well out of the box, so if if fails for you there maybe something that is required for the authentication to work. I would definitely like to understand what this is to determine if the release has a bug or it is just an update issue or similar.
Did you already file support cases for your NTLM issues? Can you send me the ticket numbers (private message) or anything you have discovered that is required to have NTLM working again?
I did mention it in a ticket but it just started working and I haven't had anymore issues. We use ISA server as well and decided to utilize the ISA plugin to forward the authenticated users, groups and IP information to the MWG as ISA's next hop proxy. Now that this is up and running, I've disabled NTLM from the MWG box all together.
I recreated the NTLM Authentication and redefined the rules and it is working again so not sure what the problem was