Dear Mr. Q, What version of Outlook and Exchange? The answer can different depending on versions.[1]
The short answer to your question is that Exchange refers the clients to a DC to use for name resolution and that is cached on the client until it fails... then the Exchange server is contacted directly and referred again to an available DC. I'll stop while we all ponder the load balancing implications of adding new DCs to an existing and established E2K org based on this behavior.[2] I'll continue to stop while we ponder the implication of directory lookup traffic to non-local DCs based on the Exchange referral behavior.[3] [1] Actually based on the description of the problem one can logically assume the server was E2K and the client was O2K or later, but too much information is always better than [2] solution covered in the archives, deja and TechNet. [3] IBID -----Original Message----- From: The Geek Q [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 03, 2001 9:54 PM To: Exchange Discussions Subject: HOW Outlook connects to Exchange I have a little issue. First I'll give you the problem, then what info I hope to find. I removed a 2K DC w/ Exchange off the domain now the 2nd Exchange box is the only mail server, also another DC. When clients try to connect using Outlook 2K they have to wait for 15-20 secs then get the "no Exchange server found" error. When they click "retry" wham it's instantly there! Now my question is how does Outlook know where/look for the Exchange server? I thought I read it was DNS for 2K, WINS for 9x. Is it a AD property? Nothing has helped so far. Any Ideas. _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED]
