Quantcast
Viewing all articles
Browse latest Browse all 3822

TMG 2010 publishing Exchange 2010 OWA cannot change password if user must change password at first logon is set

Hi,

 I have an odd issue whereby if I set "user must change password" on an AD account, the end user cannot logon, they're simply taken back to the OWA login page as if their password is incorrect.

My setup is as follows:

outer TMG -- uses a listener for email.contoso.com and is configured for no authentication.This uses a publishing rule to publish the inner TMG server. This server is not a domain member.

inner TMG - uses a listener for email.contoso.com and is configured for NLTM\kerberos negotiation with forms authentication (Windows Active Directory). This server is a domain member and use a publishing rule to publish the internal CAS. Allow users to change password is selected in the publishing rules.

Exchange 2010 SP1 - uses integrated windows and basic authentication. Has the appropriate registry key configured to allow users to change their AD password on first logon.

I've registered an snp for "http/email.contoso.com mailserver-dc1", all SSL certificates being used are valid and my configuration used to allow users to login and change their password with "user must change password on first login" set in AD.

If I launch a web browser on an internal server and point it to email.contoso.com I'm immediately presented with a generic Windows authentication request (similar to what's seen in ADFS) rather than the standard OWA page. No matter what I do, I cannot login and change my password using the correct URL. However if I point my browser at http://192.168.4.10/owa I'm prompted to login and I can change my password using the sam credentials.

The only recent changes made are:
- Disabling SSL 3.0 and enabling TLS  (http://www.isaserver.org/articles-tutorials/configuration-security/improving-ssl-security-forefront-threat-management-gateway-tmg-2010-published-web-sites.html)
- Replacing the TMG listener certificates so that they now use SHA2 rather than SHA2 (certificates are trusted on each TMG server)

Looking on the outer TMG and the DC logs I can see schannel errors which I believe are related to the problem. TMG monitoring also shows "Failed connection attempt: 1907 The user'spassword must be changed before logging on for the first time"

I've checked that my inner TMG and DC are using the same certificate for server authentication and gone through this guide: http://blogs.technet.com/b/keithab/archive/2012/02/29/setting-up-and-troubleshooting-ldaps-authentication-in-forefront-tmg-2010.aspx

If I try to use ldp.exe on the inner TMG, I get the error in the pic below

Thanks


IT Support/Everything


Image may be NSFW.
Clik here to view.

Viewing all articles
Browse latest Browse all 3822

Trending Articles