Hi, I'm configuring a new exchange server 2007 for my company and today I tried to connect to my exchange server from a workstation using outlook 2007. At the begining outlook asked for my credentials and accepted my username and password. When I went forward outlook keeps on asking for my credentials again and again without accepting them. I am able to resolve and ping both exchange and domain controller from the workstation. I run the exchange best practice analyzer but found no errors.Please helpThank youBesnik Seitaj

Hi, I would ask you to check couple of things. What are all the roles have you installed on the server? 1. Try re-creating OL profile and especially see for check name if it resolves. 2. Create one more test account and configure OL and check from exchange server open command shell and type in below Test-Mapiconnectivity Vinod |CCNA|MCSE 2003 +Messaging|MCTS|ITIL V3|

If its OL 2007 and if already the user is loged in domain .Mostly the autodiscover will configure the account automatically....

Try to post the Exact error code

Hi, Thank you for your replies. The exchange server has three roles installed: Hub Transport, Mailbox, and Client Access role. This server is not a domain controller but a member server of my .local domain. I've configured only one domain controller.and the exchange server I used is without service pack 1.I tried creating several testing accounts and the check name resolves them but when clicking next and when opening outlook I'm being asked again for credentials and this time it won't accept my credentials.Some times I get this error: The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action.I also tested the mapi connectivity and everything was ok. In reply to Abuthaheer: My workstation is not part of the domain and I don't want it to be. I have not configured Autodiscover yet.

Hi,How does the Outlook client connect Exchange server?RPC or Outlook Anywhere?If it's Outlook Anywhere, did you try the online testing tool as below:http://www.testexchangeconnectivity.com/After that, please post the log on the forum.Additionally, please check whether the Integrated Windows authentication and Basic authentication have been checked on the Autodiscover virtual directory under IIS.If not, please check them. Moreover, ensure "Integrated Windows Authentication" is checked on the EWS virtual directory, then restart IIS and check this issue.ThanksAllen

Would suggest restarting the server if possible.....

Have you tried OWA !!!

Hi,How does the Outlook client connect Exchange server?RPC or Outlook Anywhere?If it's Outlook Anywhere, did you try the online testing tool as below:http://www.testexchangeconnectivity.com/After that, please post the log on the forum.Additionally, please check whether the Integrated Windows authentication and Basic authentication have been checked on the Autodiscover virtual directory under IIS.If not, please check them. Moreover, ensure "Integrated Windows Authentication" is checked on the EWS virtual directory, then restart IIS and check this issue.ThanksAllen Hello!I have the same problem as described by Besnik Seitaj. Cannot connect with Outlook 2007 to Exchange 2007. It was possible before because several PCs can work with this constelation. Unfortunately it's not working any longer and I have no idea why. BTW - took over this LAN and have very little Exchange knowledge.BTW - OWA works fine and server was already started several times.Googled a lot but found nothing helpful. Any help is appreciated.Thanks,Harry

Hello again!Solved my problem on my own by following every hint I could get over the last weekend ;-)For anybody who might be interested:The mentioned error message seems not to be as specific as it looks. Due to a firmware upgrade on the firewalls the Exchange server could no longer find the GC. That did not harm the general functionality of the Exchange Server. But if somebodywant's to connect initially to his/her mailbox the provided user information gets checked against the GC. As this was not possible the process was stopped. The error message blamed the connection between Outlook-PC and Exchange Server but this route was totally fine.My conclusion: If you get this error message, check the event logs of your Exchange server. The error might be somewhere else than mentioned ;-)Best regards,Harry