Depending on what user id/password we use in soap UI, Windows integrated authentication fails. This usually happens after a password change. Looks like some combinations of User Id/Password/Domain result in invalid NTLM tokens. If we keep changing the password it will eventually work again, sometimes 1, 2 3 or more passwords later. We tried restarting SoapUi, Restar Windows, as well as change the Authenticate Preemptvely setting in Options with no sucess.
Is there a bug in the logic that builds the NTLM token?
Soap UI version 2.0.2 (also experienced with earlier versions), Windows XP SPII and Windows Server 2003, JSE Environment Runtime 5.0.