Outlook 2007 Retry on Terminal Server 2008
- I have a couple Windows 2008 Terminal Servers, both have Office 2007 installed. These servers were working fine two weeks ago, and then started having an error when starting Outlook. And the error happens on both servers, for all users.
When opening Outlook, it displays an error stating that Outlook could not connect to the Exchange server, and you are prompted to Retry, Work Offline, or Cancel. If you click Retry, then Outlook finds the Exchange server.
One thing I noticed that was different, in the Connection Status the Directory server and the Mail server are the same; but only for Outlook on these two Terminal servers. Every other instance of Outlook in the organization has our DC listed for the Directory server, and Exchange as the Exchange server.
So here is what the Terminal Server Outlook looks like:
Server Name Type
Exchange.my.domain DIRECTORY
Exchange.my.domain MAIL
Every other Outlook client in the Org:
Server Name Type
Domain-Controller.my.domain DIRECTORY
Exchange.my.domain MAIL
So I'm assuming that either it's a config setting point to the wrong server for these two servers, which I can't find a place to correct that. Or that for some reason Outlook can't contact the DC and is failing over to Exchange for Directory.
The DNS is correct on these servers, and they are able to reach the DC and Exchange using ping and RDP. So I think I know what the problem is, I just don't know why, and how to fix it.
Thanks in advance!- Edited byJoel T. Wednesday, November 04, 2009 4:37 PMspecify version of outlook
Answers
Hi,
Please try to use DCdiag/Netdiag to check if we have network or DC connection related issue. If you have multiple DCs, then please ensure that all the DC’s are in the same status.
You can run “DCdiag /v” from a command prompt to check it.
Dcdiag Overview
http://technet2.microsoft.com/WindowsServer/en/library/f7396ad6-0baa-4e66-8d18-17f83c5e4e6c1033.mspx?mfr=true
Netdiag Overview
http://technet2.microsoft.com/windowsserver/en/library/cf4926db-87ea-4f7a-9806-0b54e1c00a771033.mspx?mfr=true
Thanks
Allen- Marked As Answer byAllen SongMSFT, ModeratorFriday, November 13, 2009 10:09 AM
All Replies
- I would rather launch command prompt and launch nslook to make sure name to ip and ip to name are working fine
i would also run ipconfig/flushdns and ipconfig/registerdns
finally will try to configure new OL profiles.
Vinod |CCNA|MCSE 2003 +Messaging|MCTS|ITIL V3| Hi,
Please try to use DCdiag/Netdiag to check if we have network or DC connection related issue. If you have multiple DCs, then please ensure that all the DC’s are in the same status.
You can run “DCdiag /v” from a command prompt to check it.
Dcdiag Overview
http://technet2.microsoft.com/WindowsServer/en/library/f7396ad6-0baa-4e66-8d18-17f83c5e4e6c1033.mspx?mfr=true
Netdiag Overview
http://technet2.microsoft.com/windowsserver/en/library/cf4926db-87ea-4f7a-9806-0b54e1c00a771033.mspx?mfr=true
Thanks
Allen- Marked As Answer byAllen SongMSFT, ModeratorFriday, November 13, 2009 10:09 AM


