![]() |
|
#1
|
|||
|
|||
|
It looks like there still may be a problem with NOD32 and Exchange. Exchange came to an almost complete stop like the other day at 3pm Pacific. I turned off AMON, DMON and XMON and in a min or so, the users could access outlook again. Later turned on AMON and noticed Outlook lagging a little. As soon as I turned on XMON, with in a min or so, outlook got stuck in deep mud. I did try to turn on and off Background scanning in Xmon, but it had no effect. DMON had about the same reaction also. I've already excluded the files from 2 days ago that brought down Exchange.
Any suggestions? |
|
#2
|
||||
|
||||
|
Hi BBQFireGod, welcome to Wilders.
What version of XMON are you using? Cheers ![]()
__________________
"Illegitimis non carborundum"
translation: "Don't let the bastards grind you down" U.S. General Joseph W. "Vinegar Joe" Stilwell (1883-1946) Two Photographers |
|
#3
|
|||
|
|||
|
Turning off background scanning is recommended. You don't need to re-scan the whole Exchange store after every update, only when a particular email is fetched by a MUA. Note that it takes approx. 1 minute for changes in XMON configuration to take effect.
|
|
#4
|
|||
|
|||
|
I'm using XMON for MS Exchange. When I turn on XMON with background, it make exchange unaccessible from Outlook. Any ideas why it worked then all of a sudden stopped with background running on XMON?
(Thanks for the welcome BlackSpear.) Quote:
|
| « Previous Thread | Next Thread » |
| Thread Tools | Search this Thread |
|
|