Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Email very slow - Keeps getting "Stuck"

Status
Not open for further replies.

MiddleWork

IS-IT--Management
Apr 6, 2004
17
0
0
GB
In April our exchange server crashed with a multiple hard disk failure. The server was re-built and we tried to restore using the backups tapes. This however didn’t work very well, as the server wouldn’t replay the log files at a fast enough speed (it would start at around five a second and slow down to one an hour with lots of errors in-between). So we restored to the last full backup (A week ago, happened on a Friday afternoon) and then built a separate/identical server and replayed the log files on there with no problems. These emails were then saved into a PST and made available to each user.

The Server has been up and running with out any problems since then, however in the last few weeks, email has become very slow and can take 5-7 seconds to open an email and when sending, it becomes “stuck” in the outbox until you select it. Email is also arriving in groups and sometimes only arrives after you select the Inbox.

These symptoms are similar to the ones we were experiencing before the server crashed, which is making us concerned that it may happen again (a full backup is being run every night now).

We are using Windows 2000 Server with SP4 and Exchange 2000 with SP3.

Has anyone had/seen these issues before? (We believe there maybe a hardware issue with the server)
 
Have you checked your event viewer logs? Any useful informational messages there?
 
Event log has been checked, but doesn’t mention anything of use.
 
I'm seeing a similar problem with my 2000 Server SP4/Exchange 2000 SP3 install...

Middlework... did you ever figure out what was causing this?

Mark C.
Network Admin - Digital Draw Network
 
Hi Mark - After a bit of detective work, the issue only seemed to happen on machines that had been using the VPN (Checkpoint SecureClient NG-FP3) recently e.g. coming from remote office to main office.

We seemed to be able to fix the issue by removing and then re-adding the SecureClient component on the network adaptor.
 
download microsoft's exchange best practices tool.

it may or may not give you some useful information on exchange
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top