Attachments slow to send in Outlook 2000

[Guest]

Hi all,

I'm trying to send a 10MB attachment in Outlook 2000 and it takes 4 minutes
or so to send, during which time Outlook shows as 'not responding'. This
seems really slow, as it only takes a few seconds to open the attachments
from the Inbox.
What could be causing this?

Cheers,

Timboi

 

[Diane Poremsky [MVP]]

How fast you can open them from your inbox is immaterial - they are already
downloaded at that point. Outlook needs time to send messages out - how fast
is your connection to the mail server? It'll send a lot faster on a 100mbit
LAN than it will on a 36,000 dialup.

Do you use an antivirus scanner with email scanning enabled?

--
Diane Poremsky [MVP - Outlook]
Author, Teach Yourself Outlook 2003 in 24 Hours
Coauthor, OneNote 2003 for Windows (Visual QuickStart Guide)
Author, Google and Other Search Engines (Visual QuickStart Guide)



Join OneNote Tips mailing list: http://www.onenote-tips.net/

 

[middlesbrough]

How fast you can open them from your inbox is immaterial - they are already
downloaded at that point. Outlook needs time to send messages out - how fast
is your connection to the mail server? It'll send a lot faster on a 100mbit
LAN than it will on a 36,000 dialup.

Do you use an antivirus scanner with email scanning enabled?

--
Diane Poremsky [MVP - Outlook]
Author, Teach Yourself Outlook 2003 in 24 Hours
Coauthor, OneNote 2003 for Windows (Visual QuickStart Guide)
Author, Google and Other Search Engines (Visual QuickStart Guide)



Join OneNote Tips mailing list: http://www.onenote-tips.net/

Diane,

Thanks for your reply. We're on a 100MB LAN (it's actually up to 1GB/s
but I'm on a 100MB switch).
What I've noticed now is that it only happens with new email messages.
Messages that are forwarded (with the original attachments) don't have
this latency issue. We use Trend ScanMail on the exchange server (5.5)
and we have Trend Officescan on desktop (but no mail scanning enabled).

Cheers,

Timboi

 

[middlesbrough]

It ended up being a duplexing mismatch; 3Com NIC set to 100/Full had
compatibility issues with a Cisco switch that was et the auto-neg (for
some reason the switch was negotiating to 100/Half).
All very silly, really.

cheers,

Timboi