After Administrator Password Change Cannot Authenticate OWA Outside

Good morning everyone,

We recently had to change our Administrator password on the domain as well as the local servers. Shortly after doing this, we noticed that users could not authenticate through OWA from the outside. Inside the network, everything authenticates correctly. I realize that this is a brief description, and i apologize, however nothing else was changed. The password change has effected nothing else, other than the authentication through OWA from the outside.

On a side note, if the old admin password is reentered, everything goes back to working correctly. Thanks in advance for any responses/help!

Exchange 2010 on Windows Server 2008 R2 Enterprise SP1, IIS7


-Andy & Kathy
JDL_TechAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

George SasIT EngineerCommented:
Try to use this tool and see if you have any services /scheduled tasks runing as the Domain Administrator.

http://www.cjwdev.co.uk/Software/ServiceCredMan/Info.html

Your problem is most surely there.
0
JDL_TechAuthor Commented:
Hey Geo,

Thanks for the reply. We have gone through all services, as well as ran a script that searches all tasks and services on the network that are tied to the admin user. None are related to Exchange or any other server that would affect our authentication.
0
George SasIT EngineerCommented:
OK. What error you get when you try to authenticate ?

Please take look on the IIS server at the application pools and see if any of them runs as the admin.

Also look on the security events on the servers right after you try to log in and see what failed auth you have there.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

JDL_TechAuthor Commented:
Hey Geo,

When trying to authenticate, we are getting a Failed to Authenticate from phones, and then just a generic Bad Username or Password for regular OWA site.

No application pools in IIS are set to run as admin.

Here is the error we're receiving within the events:

An account failed to log on.

Subject:
      Security ID:            SYSTEM
      Account Name:            *****
      Account Domain:            *****
      Logon ID:            0x3e7

Logon Type:                  8

Account For Which Logon Failed:
      Security ID:            NULL SID
      Account Name:            *****
      Account Domain:              *****

Failure Information:
      Failure Reason:            Unknown user name or bad password.
      Status:                  0xc000006d
      Sub Status:            0xc000006a

Process Information:
      Caller Process ID:      0x2c48
      Caller Process Name:      C:\Windows\System32\inetsrv\w3wp.exe

Network Information:
      Workstation Name:      *****
      Source Network Address:      *****
      Source Port:            13447

Detailed Authentication Information:
      Logon Process:            Advapi  
      Authentication Package:      Negotiate
      Transited Services:      -
      Package Name (NTLM only):      -
      Key Length:            0

This event is generated when a logon request fails. It is generated on the computer where access was attempted.

The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.

The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).

The Process Information fields indicate which account and process on the system requested the logon.

The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.

The authentication information fields provide detailed information about this specific logon request.
      - Transited services indicate which intermediate services have participated in this logon request.
      - Package name indicates which sub-protocol was used among the NTLM protocols.
      - Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
0
George SasIT EngineerCommented:
How is your exchange configured ?
One server with all roles ? Separate ?
Firewall in the front ?

Try to add an entry on your internal DNS to point to the internal IP address of the cas server so you access the EXTERNAL url of owa as internal URL. See what happens.

As far as I can see it is the IIS that sends the request in with bad username / pass.
Can you log into owa with domain admin ?

Try to reset OWA directory :
http://technet.microsoft.com/en-us/library/ff629372%28v=exchg.141%29.aspx
0
JDL_TechAuthor Commented:
Hey Geo,

So, I have no reason as to why it is now working, but it is now working. Yesterday i changed the password back so it would work over night and then this morning changed it back to the new password again. It is now working, and nothing was done differently than the past 2 days. I appreciate the all your responses!
0
George SasIT EngineerCommented:
Ah, maybe it was a replication problem :)
If you have multiple DC's and the Exchange server tried to get the credential on the server that did not got the replication yet.
Glad you got it working.
0
JDL_TechAuthor Commented:
We were thinking the same thing. Next on the list i suppose! Thanks again.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.