That flag has been the cause of more headaches that carter has little pills.
The flag will set if the response to a client query takes more than about half a second. The timing is changeable via a registry entry, and can be disabled as well. Check the Microsoft KB for the article that describes the change in detail. Please let your users know that the flag is telling them that Exchange is processing their request and will take a second or three to return the results. They should be happy that the flag is there, as that tells them they really are talking to the server. You will also get the flag if you do a search against your mailbox or against a public folder, even if you have Full Text Indices built on the message databases. John Matteson Geac Global IT group (404) 239 - 2981 Atlanta, Georgia, USA. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Reasoner, Bob (PHES) Sent: Tuesday, September 14, 2004 2:09 PM To: Exchange Discussions Subject: Outlook "Waiting for Exchange..." dialogs For the last 3 weeks or so all of my clients (ranging through Outlook 2000, XP, and 2003) have started noticing frequent dialog boxes indicating that their client is waiting for the exchange server, synchronizing with the exchange server, or just in general unable to communicate with the exchange server. I can't find any problems with the network itself. The Exchange server is a Dell 2650 Dual processor 2.0 GHz Xeon, Ample space available on boot, log, and store drives, 1Gb RAM. The server is in a Mixed Mode 5.5 admin group and we use Trend AV for Exchange. This server services approximately 500 mailboxes and has 1 Mail store (approx 17 GB, Exchange 2K SP4 Enterprise) 1 public store les than 5 GB. The OS is Win2K SP4 with all hotfixes applied to OS and Exchange. There is a single 5.5 server in the Admin group as well but it doesn't host any mailboxes. This site has connectors to our parent organization, but all the mailboxes are servicing accounts within our local AD subdomain of the Parent forest. We don't have any errors showing up in event viewer, and the only warnings are related to incoming replication of public folder data from our parent's Exchange 5.5 server. Anyone have any tried and true techniques for troubleshooting this type of problem? I have tried changing the ExchangeProvider/RPC_Binding_Order registry Key on some of the clients to "ncalrpc,ncacn_ip_tcp" or reversing those entries to no avail. ________________________________ Bob Reasoner Harris County Public Health & Environmental Services _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&; lang=english To unsubscribe send a blank email to %%email.unsub%% Exchange List admin: [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with. _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&lang=english To unsubscribe send a blank email to [EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with.
