Delay in opening attachments

[thartpence]

I am extremely new to exchange, (taking classes on it soon) but I am trying to find out what may be causing our attachments over our LAN to open so slowly. It seems to be enterprise wide as users on my frame links are complaining aout it as well. If it was just our frame users, I can understand it as they are on 256K. The part that troubles me most is that this is happening on our local system as well. Are there any good resources other than M$'s website that will give me a good starting point to troubleshoot this?
Any suggestions are appreciated.

Tim

 

[clyd3c0]

I am having this same issue. I can't seem to figure out why this is happening. Did you have any success in resolving this? Any help would be much appreciated.

 

[mucous]

I may be totally wrong on this one, but we recently upgraded our network to all new equipment. Everything was zinging right along. In an effort to try tweaking things, I set the server nics and client nics to 100Mb full duplex instead of auto negotiate. After I made the change, our database began running like a turtle missing three legs. I switch back to auto on the nics and all is well. I know databases and exchange are two different beasts, but maybe your answer lies in there somewhere. Made any network changes lately? Our new network is all Dell, BTW...

 

[clyd3c0]

We had our database on a local RAID of our exchange server and thinking that possibly that might be the problem, we moved the private and the public databases to a SAN drive and the problem is still there. We haven't made any changes to the network. The wierd thing is that this doesn't happen to all users. But I can't narrow down to any one thing, especially since it happens to users on my LAN and over the WAN.

One thing that just came to mind is that we are running HP/COMPAQ DL 380 SERVER with 2 GB Nics. We are actually teaming the NICS and I'm wondering if that might be causing any problems. I will do some testing and report back. Thanks for reply back.

 

[xmsre]

On the client side, you might try Q300904 and Q290025

John
MOSMWNMTK