I have an Exchange 2003 Server which I was using for about 2 months... I took it offline to move and 2 weeks later placed it back online, along with my domain controllers. Now when I attempt to resolve a name under Outlook I am prompted for a username/password and when I type the correct credentials in , it is unable to resolve the username/password. What makes this more interesting is that I am able to log onto the computer using a Domain user account, and I even changed the password multiple times on the DC, waiting a good 20 minutes for replication to occur, just in case my DC and Exchange servers weren't talking. I even changed the password of the users (experimenting with 3, all with same error) and had same issue. I have taken computer off domain, and re-added it (3times), I have shut down my DC and EXCH servers, ensuring the DC booted fully first before turning EXCH own, and I have rebooted the client machine more times than I can count... My test machine is using Server 2003 with Outlook 2007, does anyone have any idea what it could be?

Has anything changed regarding DNS?-- Ed Crowley MVP"There are seldom good technological solutions to behavioral problems.". "WilliamK2012" wrote in message news:d26d93af-9707-48b5-9c2d-75cfe684900f... I have an Exchange 2003 Server which I was using for about 2 months... I took it offline to move and 2 weeks later placed it back online, along with my domain controllers. Now when I attempt to resolve a name under Outlook I am prompted for a username/password and when I type the correct credentials in , it is unable to resolve the username/password. What makes this more interesting is that I am able to log onto the computer using a Domain user account, and I even changed the password multiple times on the DC, waiting a good 20 minutes for replication to occur, just in case my DC and Exchange servers weren't talking. I even changed the password of the users (experimenting with 3, all with same error) and had same issue. I have taken computer off domain, and re-added it (3times), I have shut down my DC and EXCH servers, ensuring the DC booted fully first before turning EXCH own, and I have rebooted the client machine more times than I can count... My test machine is using Server 2003 with Outlook 2007, does anyone have any idea what it could be? Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Negative, the DNS server is the same, I did take down the backup DNS server for maintenance but the EXCH Server was never pointed to it in the first place.

I have an update, I installed Outlook on my DC and logged on with my Domain Admin account and was able to connect to Exchange server, the kicker though, I made a fake user, gave him Backup Admin role so he could log onto DC, and he was unable to connect to Exchange.... Now this has me truly stumped...

Hi, Please try to type the name of your Domain Controller instead of your Exchange Server when you try to configure the profile for outlook. Please try to type the IP address of your Exchange Server instead of your Exchange Server when you try to configure the profile for outlook. Please try to run DCdiag from the client computer and then check it will pass all the test. Besides, I recommend you to use ExBPA to have a health scan and then check the report. Please post the error event here. Related information to share with you: Dcdiag Examples http://technet.microsoft.com/en-us/library/cc758753(WS.10).aspx Microsoft Exchange Best Practices Analyzer v2.8 http://www.microsoft.com/downloads/details.aspx?FamilyID=DBAB201F-4BEE-4943-AC22-E2DDBD258DF3&displaylang=en Regards, Xiu