[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 213
  • Last Modified:

Exchange account credentials doesn't work


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
Jaime Campos
Jaime Campos
1 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?
Jaime CamposAuthor Commented:
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.

Featured Post

Prepare for your VMware VCP6-DCV exam.

Josh Coen and Jason Langer have prepared the latest edition of VCP study guide. Both authors have been working in the IT field for more than a decade, and both hold VMware certifications. This 163-page guide covers all 10 of the exam blueprint sections.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now