General discussion


Sending Attachments with Exchange on WAN

By Tim.Doyle ·
I have an Exchange 5.5 (SP4) server (NT4 SP6a) running at my main office, one sattelite office is connected to the main via a 768k frac-T line, the other 9 offices are connected via 384k frac-T lines. All offices have trouble sending email attachments (obviously the greater bandwidth office has less trouble). If I send a 7k attachment the system will basically freeze solid for about 2 minutes (the delays last longer the bigger the attachment) the high BW office it takes seconds, at the main office its vitually instantaneous. It seems to me that Outlook (I run 97, 2k and XP) should move the messgae to the Outbox and then send it in the backgroupd, but is this possibly the whole problem in the first place? I do not use Personal Folders (per MS TID recommending against the use of personal folders while using Exchange) so logically the outbox is on the server itself...this may be where my problem lies but I'm not entirely sure.

I need a fresh perspective here. Does anyone know of a way to make the Outbox local but leave the rest of the folders on the server? Am I barking up the wrong tree?

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

Sending Attachments with Exchange on WAN

by [_Rick_> In reply to Sending Attachments with ...

Try using OST instead of a PST. The OST will maintain a scynchronized copy of the mail account locally. Using the OST allows the end users to remain connected to their mail account in the even the WAN or the server is unavailable.

Use Outlook 2000 or better for OST synchronization, it provides better flexibility. The largest downside to using OSTs is space locally, you have some control over this with O2K in that you can prevent large messages from being synchronized.

Another option instead of using Outlook with RPC communications is to use Outlook Web Access. Before going the OWA route I'd first investigate the possibility of using OSTs at the remote desktops.

Hope this helps.


Related Discussions

Related Forums