none
Outlook 2007 asks for password when using Exchange 2007

    Question

  •  

    Hi All,

    Hope this is the right forum.


    Hoping for some help, recently any time a user opens Outlook 2007 it provides a popup box asking for the username and password for the user, when they enter it, the box just reappears.

    The Username is in the format SERVERNAME\USERNAME I have tried playing with it entering USERNAME and DOMAIN\USERNAME without any success In Event Log on the server the following is logged.






    An account failed to log on.
    Subject:
    Security ID: SYSTEM
    Account Name: SERVER$
    Account Domain: DOMAIN
    Logon ID: 0x3e7
    Logon Type: 3
    Account For Which Logon Failed:
    Security ID: NULL SID
    Account Name: SERVER$
    Account Domain:
    Failure Information:
    Failure Reason: Unknown user name or bad password.
    Status: 0xc000006d
    Sub Status: 0xc0000064
    Process Information:
    Caller Process ID: 0x13ac
    Caller Process Name: C:\Program Files\Microsoft\Exchange Server\Bin\Microsoft.Exchange.Search.ExSearch.exe
    Network Information:
    Workstation Name: SERVER
    Source Network Address: -
    Source Port: -
    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.





    Any thoughts? If we use OWA from the same computer it usually works fine, occassionally it also fails but a restart of the server fixes the issue.

    Friday, August 15, 2008 9:13 AM

All replies

  • Hi,

     

    I have th same exact problem currently and am investigating. Just adding to the weight of your request, hoping for somebody to give us a clue.

     

    Regards,

    Emmanuel

     

    Monday, August 18, 2008 7:45 AM
  • Hi,

     

    Would you please provide further information regarding the issue?

     

    1.      Whether does the issue only occur on a specific user?

    2.      If the issue only occurs on a user, whether he is able to logon his mailbox on another good Outlook client by creating a new profile.

    3.      How the Outlook connects to Exchange? MAPI or RPC over HTTP (Outlook Anywhere)?

    4.      The Exchange Server installed Windows Server 2008 or Server 2003?

     

    In addition, please run EXBPA to check whether any related issues.

     

    Mike

     

     

    Monday, August 18, 2008 10:02 AM
  •  

    Hi Mike,

     

    Thanks for the response.

     

    1) Issue is with all users

    2) Recreating the profile sometimes works for a day or two then issue returns, other times it does not work at all.

    3) We have users connecting with RPC from remote locations, and from inside the network using the MAPI connection. No Difference in who has issue.

    4) Server 2008 with all updates.

     

    EXBPA finds no issues.

     

    Hope this helps.

    Monday, August 18, 2008 11:52 AM
  • Hi,

     

    Firstly, regarding the event which you posted, it seems a known product issue which will be fixed in Exchange 2007 SP1 Rollup4. For reference:

     

    http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3632827&SiteID=17

     

    Thus, I think that the event does not relate to the Outlook Logon issue.

     

    Base on the current situation, please attempt the following method to troubleshoot the issue:

     

    1.      Please configure an Outlook 2003 Service Pack 2 client (please uncheck Cached Mode) and check whether we are able to access the mailbox successfully

    2.      On problem Outlook 2007 client, after typing the username and password, when the box is encountered, please ignore it (do not click Cancel). Then, hold down the CTRL key on your keyboard and click the Outlook icon in the notification area of the Windows taskbar, also known as the notification area. Click Connection Status, please post the result here.

     

    Mike

    Tuesday, August 19, 2008 7:25 AM
  •  

    Hi Mike,

     

    Well it took a few hours but the 2003 version did the same as the 2007 version. When I check connection status it shows as established, If I then enter a password it changes briefly to disconnected then established again as the password box reappears.

    Wednesday, August 20, 2008 8:34 PM
  • Mike,

     

    did you solve the problem?

    I have a kind of the same problem.

    we upgrade to outlook 2007 from 2003. then the login screen display SERVERNAME\USERNAME  again and again.

    We have a exchange 2007 server.

     

    how do i solve it?

     

    thanx in advance!

     

     

    Friday, September 05, 2008 5:47 PM
  • I turned off the IIS7 kernel mode windows authentication to resolve the pompting on my server.

     

    Here's the command that needs to be run on the CAS boxes ->

    %Windows%\inetsrv\appcmd.exe set config /sectionTongue Tiedystem.webServ

    er/security/authentication/windowsAuthentication /useKernelMode:false

     

    I found the solution at:

    http://msexchangeteam.com/comments/449053.aspx

    Wednesday, September 10, 2008 9:46 PM
  • Hi,

     

    I have the exact same problem with clients on the domain. The username is  pre-populated in the format.

     

    SERVERNAME\UserName.

     

    Obviously users just try and enter their passwords and the connection fails because they don't have local accounts on the server. If I get them to ammend the login to.

     

    DOMAINNAME\UserName

     

    And then enter their password the login works fine.

     

    It would be great if the login used in-built authetication (like it is meant to!) or at least if the login dialogue in outlook was popualated with the correct details....

     

    F.

    • Proposed as answer by I.T. Admin Thursday, November 10, 2011 4:26 PM
    Monday, December 01, 2008 4:20 PM
  • I am getting this same issue at 1 site. we think it started after an update was applied to the server, have exchange server 2007.
    this issue is only affecting outlook 2007 clients previous versions do not have this issue.
    the exchange server is connected and they do still recieve emails so i have no idea why this login prompt is appearing.
    i have tried changing the logon network security but niether setting helped in event viewer looks like there's a mixture of kerbos and htlm requests being sent so may possibly need the security been set to only send ntml from the server just looking into the group policy to see if it helps
    Tuesday, February 16, 2010 11:50 AM
  • Having the same problem here .
    Exchange 2007 SP2 . clients Outlook 2007 .

    On the client computer no errors are logged .
    If the user click on cancel outlook works ( is connected )  and users get their email
    thanks
    Stefano
    Thursday, February 18, 2010 9:22 AM
  • I've had this exact same problem and found that my clients couldn't ping the exchange server using it's fully qualified domain name - an ipconfig /registerdns on the exchange box sorted the issue, even though nslookup appeared to be resolving the FQDN properly on the clients.
    • Proposed as answer by Bob T Bobbins Thursday, March 24, 2011 10:43 AM
    Thursday, March 24, 2011 10:43 AM
  • There are a couple of reasons why this could be happening, I have outlined them in my blog post here: http://demazter.wordpress.com/2010/02/09/outlook-continually-prompting-for-username-and-password-2/

    Another potential cause is the authentication setting used on Outlook & exchange, if they do not match then the same problem will be caused when using RPC-HTTPS or Outlook Anywhere, see my blog post here: http://demazter.wordpress.com/2010/11/09/outlook-prompting-for-username-and-password-when-using-exchange-2010/

    Whilst a 3rd part SSL Certificate is not a requirement, it can save a lot of problems when using RPC-HTTPS, and for the sake of $89 for a signed certificate from http://www.exchangecertificates.com is it really worth the hassle?


    demazter

    http://demazter.wordpress.com
    http://www.demazter.co.uk

     

    Monday, March 28, 2011 7:34 AM
  • Finally!!!

    I found a sollution for my problem with SBS 2008/Exchange 2007/Outlook 2007 authentication system, both over RPC and regular. Just keeps asking for password! Tried a million things just like the others, no joy. Went into IIS Manager, opened SBS Web Applications, Select Owa, double click SSL settings, check Accept instead of ignore or require, and Apply. I repeated for Remote, Rpc, RpcWithCert. leave Autodiscover on Ignore in order to make it continue to work.

    Add Basic Authentication on RPC and RPC with Cert.

    Restarted Web Publishing and IIS Admin, and YES!!! Finally I got rid of Outlook 2007 continously asking for password! Joy Joy Joy!!!

    • Proposed as answer by STG4ME Wednesday, April 27, 2011 3:06 PM
    Monday, March 28, 2011 10:48 PM
  • Hi Stefano

    Have you sort this problem I have same problem

    Outlook 2007 and every morning its asking me the username/password.

    Could you help me no that please

    Regards

    Farhan

    Thursday, July 14, 2011 10:10 AM
  • Thank you very much Fraser, this solved my problem 100%.

     

    It was all because the exchange didn't have local accounts setup. When I authenticated through the servername as you suggested, it went right through and connected.

     

    Thanks again!

    Thursday, November 10, 2011 4:27 PM
  • Joen1 - your solution is simple to apply and worked also for me.

    THANK YOU

    Monday, February 06, 2012 1:25 PM
  • Hello Joen1, I was receiving a constant prompt of username and password without being able to pass through that point.

    After applying your suggestions I now have a different behavour, I now am able to open Outlooks and connect them automatically to the domain server (also de Exchange) but after a while the "need password" anoying thing appears again together with a password prompt.

    Any ideas on what this might happen or how to solve it?

    Thanks a lot for your help!

    Thursday, March 08, 2012 2:49 AM