Exchange account credentials doesn't work

Posted on 2011-10-10
Last Modified: 2012-05-12

I have Exchange 2007 and all existing email is working fine. I have added a new employee within ADUC and filled in email account and user info. I then went to Exchange Management Console and added a new email account and account was added successfully. I'm doing this procedure the same way I have always done it. Now, when I go to users outlook and select add New Email Account, I notice it Auto Account Setup and I hit next. When I hit next it successfully Esablishes network connection, successfully searches email server settings, however when it gets to Log on server a box pops up asking for credentials. I put in the credentials and it doesn't do anything except ask me for credentials again.


Jaime Campos
Question by:nimdatx
    LVL 14

    Accepted Solution

    How long ago were these objects created? Is it possible its a replication issue and you just need to give the various DCs and MSs time to replicate?
    LVL 1

    Author Comment

    No it's been a while.

    I checked the Exchange Event Viewer and this is what I saw....

    Process STORE.EXE (PID=4564). Exchange Active Directory Provider
    failed to obtain an IP address for DS server fileserver.RAPA.local, error 11001
    (WSAHOST_NOT_FOUND (Host was not found)).  This host will not be used as a DS server
    by Exchange Active Directory Provider.  

    Process STORE.EXE (PID=4564). Exchange Active Directory Provider is unable to connect to the
    Domain Controller fileserver.RAPA.local although its service location (SRV) resource record
    was found in the DNS
     The query was for the SRV record for _ldap._tcp.dc._msdcs.RAPA.local
     The following domain controllers were identified by the query:

     Common causes of this error include:
     - Host (A) records that map the name of the domain controller to its IP addresses are
    missing or contain incorrect addresses.
     - Domain controllers registered in DNS are not connected to the network or are not running.
     For information about correcting this problem,   type in the command line:
    hh tcpip.chm::/sag_DNS_tro_dcLocator_messageHa.htm

    Now, Fileserver was an old DNS/DC server. It's still on the network, but I thought Exchange was using Fileserver2, which is our new DC/DNS.

    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    Highfive + Dolby Voice = No More Audio Complaints!

    Poor audio quality is one of the top reasons people don’t use video conferencing. Get the crispest, clearest audio powered by Dolby Voice in every meeting. Highfive and Dolby Voice deliver the best video conferencing and audio experience for every meeting and every room.

    Set up iPhone and iPad email signatures to always send in high-quality HTML with this step-by step guide.
    ADCs have gained traction within the last decade, largely due to increased demand for legacy load balancing appliances to handle more advanced application delivery requirements and improve application performance.
    In this video we show how to create an Accepted Domain in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Ac…
    This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…

    759 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    10 Experts available now in Live!

    Get 1:1 Help Now