Discussion Locked

MS Exchange Server

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Currently Running MS Exchange 5.5 on two systems with two different DB's. It has been running fine for years. now all of a sudden individuals who maintain there inbox open but minimized on thier desktop, where it use to automatically download the email when arrived at server and show the mail icon. now it is sometimes taking half hour plus before it does it, and in many instances the individual would have to maximize the inbox and check mail before it would download. This has happened on over seven systems now so i know it is not isolated to a few individual inbox options.
is there a function at the server that needs to be invoked? time limit? etc..?
thanks

7 replies

by kenderkn

Chris, I have had a similar problem in exchange but the answer wasnt in exchange itself. I found that my DNS servers MX record had been changed by a new admin trainee..once he did that the clients using rpc's to access exchange to do the updates oftheir inboxes were taking an inordinatly long time to resolve to the exchange server. on one of the WS's with the problem try using rpcping (exchange resource kit) to verify the speed of the calls. you also might try checking the dns and wins databases. and one more thing...just general good preactice is manually compacting and reapiring you excahnge databases using edbutil. hope this helps

by tgotschall

Chris,
I have seen this problem when mail was set to be delivered to personal folders instead of the mailbox. Make sure this is not the case by checking the client profile. If it is, try changing one client and see if the situation improves.

by curlergirl

Did you recently add or change any mail services - ISP, local server, etc? This can cause workstations, particularly WIN95, to have problems connecting to the server. One thing you might try is using a local HOSTS file to cache the Exchange ServerIP address locally on the workstations rather than depending on DNS. Also - the comment about doing an offline defrag of your Exchange database is a good one - except that the tool used by Exchange 5.5 is called eseutil.exe, not edbutil.exe. Hope this helps!

This discussion is closed to new replies.