Solved

New Exchange 2003 Server - POP3 users hang when receiving random emails

Posted on 2006-07-08
2
321 Views
Last Modified: 2010-03-06
Greetings Experts,

Replaced a Dell PE2600 SBS2000 server with 3 new servers - one is running Exchange 2003.
User accounts and mailboxes were copied over from the SBS2000 server to the PDC and Exchange server.  

The company has two offices connected via a VPN through two identical WatchGuard SOHO tc6.  

Computers in first office where servers are located attach to the domain and use Outlook 2003 with Exchange accounts.  

Computers in the second office are in a workgroup, and also use Outlook 2003 configured with Exchange accounts.  

There are many laptops in the field running Windows XP Pro that use both Outlook 2003 configured with POP3 accounts and OWA.  Same as before server replacement.

All appeared well - users configured with Exchange accounts were sending and receiving emails.  At first it appeared that the POP3 users also were sending/receiving fine, but then all the POP3 users started to time out during receiving.  At first, it appeared that the problem was random "corrupted" emails: a POP3 account for each user was setup (1 at a time) on an in-house computer and when it would stall while receiving, we would go into OWA and move the suspect email out of the Inbox and try again.  Sometimes this would "correct" the problem, other times we would need to move additional emails out of the Inbox.  Most of the "problem" emails were from outside senders, although there also were some from within the company.  We worked late into the night, completing all the POP3 accounts.  However, the next day the same timing-out problem started happening again to the POP3 users - again most of the "problem" emails originated outside the company.

What can be wrong?
0
Comment
Question by:kwallerjr1
2 Comments
 
LVL 104

Accepted Solution

by:
Sembee earned 500 total points
Comment Utility
That is usually an indication of something interfering with the message. Antivirus or antispam applications are the usual cause. They scan the message, changing it slightly and the POP3 system cannot cope.

As your clients are on Windows XP, why don't you drop POP3 and switch over to RPC over HTTPS. Doesn't require a VPN and will give all of your users the full Exchange experience. POP3 I now consider to be the last resort for remote access and I haven't deployed it commercially for over 18 months.

Simon.
0
 

Author Comment

by:kwallerjr1
Comment Utility
Sembee,

The problem was solved with a Hotfix from TrendMicro.  However, I like what I am reading about RPC Over HTTPS.

Thanks for the fast reply.

Cheers.
0

Featured Post

How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

Join & Write a Comment

Suggested Solutions

Resolve DNS query failed errors for Exchange
This process describes the steps required to Import and Export data from and to .pst files using Exchange 2010. We can use these steps to export data from a user to a .pst file, import data back to the same or a different user, or even import data t…
In this video we show how to create an Accepted Domain in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Ac…
how to add IIS SMTP to handle application/Scanner relays into office 365.

743 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

16 Experts available now in Live!

Get 1:1 Help Now