Re: problems with outlook 2003 and secure pop3
- From: "Harondel J. Sibble" <help@xxxxxxxxx>
- To: exchangelist@xxxxxxxxxxxxx
- Date: Mon, 19 Dec 2005 14:30:28 -0800
Forgot to post the endusers comments.
I tried cranking up the diagnostic logging to level 5, but didn't see
anything odd, I see the connection, the check of uidl's and the download of
messages.
> Hi Harondel- Here are further details of the problem I described to you
> yesterday.
>
> Yesterday Outlook would "stall" at 150Kb of 155Kb (for example) and I
> would not receive all of OR any of my messages. I would receive the
> following error message:
>
> "Task 'mailserver.company.tld - Receiving' reported error (0x8004210A):
> 'The operation timed out waiting for a response from the receiving (POP)
> server. If you continue to receive this message, contact your server
> administrator or Internet service provider (ISP)."
>
> Today the problem is slightly different. I get "Send/receive status 50%"
> and then "33%" and then back to "50%", but I no longer receive any emails
> at all. The same error message appears:
>
> "Task 'mailserver.company.tld - Receiving' reported error (0x8004210A):
> 'The operation timed out waiting for a response from the receiving (POP)
> server. If you continue to receive this message, contact your server
> administrator or Internet service provider (ISP)."
>
> I went into the office today to try Outlook there and the same thing
> happened. (Both office and home are Bell Sympatico DSL.)
>
> I tried dialup (Radiant) and the same thing happened.
>
> I can still send using Outlook.
>
> Web access to Outlook still works okay.
>
> The last time Outlook worked both at home and the office was Friday. The
> only thing I did between last using Outlook on Friday and encountering the
> problems on Saturday was that I ran "disk cleanup" and "disk defrag"
> Friday night.
>
> Below is a description of a similar sounding problem that I found on
> Google.
>
> I will let you digest this and will call you later this weekend.
>
>
> QUESTION POSED ON: 20 APR 2005
>
> I have Exchange Server 2003 SP1. The OS is Windows 2003 with its latest
> update. The server has four stores for four e-mail domains. The clients
> are connected as POP3/SMTP accounts, not Exchange ones. The problem is
> that, with some users, the e-mail stops at receiving the first message in
> Microsoft Outlook 2003 SP3 (all clients have that). The e-mail just stops
> at receiving message 1 of XX. The problem is happening with small and big
> e-mails. If the user uses Outlook Web Access, he/she can see all e-mails
> without any problem. Another problem that happens is that some of users
> are receiving duplicates of the e-mails whenever they click the
> Send/Receive button. Till now, the only solution I could think of was to
> move the mailbox to another store. When I did that, it would be OK
> temporarily. But the problem still keeps happening again and again.
>
> After it takes too much time trying to receive the first e-mail (some
> start receiving and then stop; the number varies from user to user), the
> user receive the following error message in Outlook:
>
> "Task 'mail.xxxx.xx - Receiving' reported error (0x8004210A): 'The
> operation timed out waiting for a response from the receiving (POP)
> server. If you continue to receive this message, contact your server
> administrator or Internet service provider (ISP)."
>
> I turned off all the computers and tested for one user and it is the same.
> As I told before, it is happening for certain user accounts, not for one
> person this time and for someone else the next time. The antivirus is
> Trend Micro Server Protect and Trend Micro Scan Mail for MS Exchange. I
> have tested these products before and I had never have had any problems.
>
> I have tried downloading the e-mails using different computers for the
> account and different Internet connections, but the result is the same.
> Please help.
>
> QUESTION ANSWERED BY: Archive
>
> This could be a number of issues. One could be a routing or firewall
> configuration issue, and, depending on how the client routes to the given
> Exchange server, one path may have port 25 blocked. A retry may choose an
> alternate route and succeed.
>
> Another reason might be networking issues. Any number of issues could be
> present, including out-of-spec cables, too many hubs, duplex issues,
> (e.g., the client computers are not reliably negotiating the same duplex
> mode as your IP switch). To troubleshoot, check the System and Application
> Event logs for network interface related messages. Also, open a command
> prompt on one of the machines, run a "netstat -s" and note the number of
> retransmitted packets. Run your Send/Receive and re-issue the "netstat
> -s"; if there is a significant delta, suspect your network configuration.
>
> Another diagnostic approach is to log the conversation for a while on the
> POP3 virtual server. To enable logging, reference the Microsoft Knowledge
> Base article 299778. Please take heed of the warnings for exhausting
> system resources and enable logging for a controlled period of time. This
> also requires restarting the inetinfo.exe service after resetting the
> logging through the registry changes (or an Exchange server reboot).
>
--
Harondel J. Sibble
Sibble Computer Consulting
Creating solutions for the small business and home computer user.
help@xxxxxxxxx (use pgp keyid 0x3AD5C11D) http://www.pdscc.com
(604) 739-3709 (voice/fax) (604) 686-2253 (pager)
Other related posts:
