Re: slow internal e-mail
From: Reed Wiedower (rwiedower_at_peyser.com)
Date: 01/05/05
- Next message: Reed Wiedower: "Bad Mail"
- Previous message: Dan: "Re: forwarding email to more than one user"
- Next in thread: Pat Cai [MSFT]: "Re: slow internal e-mail"
- Reply: Pat Cai [MSFT]: "Re: slow internal e-mail"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 5 Jan 2005 11:20:55 -0500
1) The only issue with Windows updates is that there are currently two
security patches I'm having trouble installing on the server.
- Security Update for Windows 2000 (KB885836)
- Security Update for Windows 2000 (KB885835)
2) Since the timestamp is less than one minute, there isn't a way to
determine which step takes the longest, correct? The tracking log says
everything takes place during the same minutes.
3) There is no file-based virus protection on the Exchange server. There is
a message based virus protection package that hooks into exchange directly,
but it hasn't been altered in any way.
4) I don't have exchange enterprise, so I cannot create a new mailbox store.
eol,
Reed
"Pat Cai [MSFT]" <v-patcai@online.microsoft.com> wrote in message
news:sS8NzI05EHA.764@cpmsftngxa10.phx.gbl...
> Hi Reed,
>
> Thanks for your update.
>
> I need to confirm with you that whether you have applied any Windows
> updates or Exchange updates recently. If so, while the server becoming
> more
> secure, it takes more time to process its transactions. Based on my
> experience, 30 seconds for sending internal message is not a bad behavior
> and in fact, the some operation in my test machine sometimes would take
> much longer than 30 seconds even though I only have two users in the
> environment.
>
> You may send the message track log to me at v-patcai@microsoft.com so that
> I could narrow down which step takes the unreasonable time. Or you can
> just
> capture a screenshot on the track log and send it to me. Make sure that
> each process step and its time cost is listed.
>
> For the firewall, I suggest temporarily stop it monitoring Exchange
> related
> folders, such as the disk M: (Exchange backend storage) and the Exchange
> installation folder. It would not cause the server attacked by virus if we
> still monitor the network package flowing and other system folders..
>
> Another test step we can try is to create a new Exchange mailbox store.
> The
> issue may be caused by the inconsistent Exchange database after the server
> working for a period of time. So it would take more time to read/write
> information to database.
>
> Note: Only Exchange enterprise edition supports multiple mailbox stores.
>
> To do so:
>
> 1. Open ESM, right-click on the first storage group and select new mailbox
> store
> 2. Open ADUC, create new users A and B and put their mailboxes in the new
> created mailbox store
> 3. Sending message from A to B, what is the result?
>
> Please try the above steps and let me know the result at your earliest
> convenience. I look forward to your reply!
>
> Regards,
>
> Pat Cai
> Microsoft Online Partner Support
>
> Get Secure! - www.microsoft.com/security
> =====================================================
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
- Next message: Reed Wiedower: "Bad Mail"
- Previous message: Dan: "Re: forwarding email to more than one user"
- Next in thread: Pat Cai [MSFT]: "Re: slow internal e-mail"
- Reply: Pat Cai [MSFT]: "Re: slow internal e-mail"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
