Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. XCON: POP3 Clients That Are Connected Over RAS May Disconnect After 10 Minutes in a Front-End and Back-End Server Environment

XCON: POP3 Clients That Are Connected Over RAS May Disconnect After 10 Minutes in a Front-End and Back-End Server Environment

View products that this article applies to.

This article was previously published under Q315902

↑ Back to the top

Symptoms

When a Post Office Protocol version 3 (POP3) client connects to the front-end server over a dial-up connection, the client may disconnect after 10 minutes, regardless of the time-out value that is specified on the front-end server. The POP3 client may receive the following error message:
Your server has unexpectedly terminated the connection. Possible causes for this include server problems, network problems, or a long period of inactivity. Account: 'user', Server: 'server1', Protocol: POP3, Port: 110, Secure(SSL): No, Socket Error: 10053, Error Number: 0x800CCC0F

↑ Back to the top

Cause

This problem can occur in Exchange 2000 Server Service Pack 2 (SP2) if the code does not read the metabase value correctly.

↑ Back to the top

Resolution

To resolve this problem, obtain the latest service pack for Microsoft Exchange 2000 Server. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
301378� XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack
The English version of this fix should have the following file attributes or later:

Component: front end and back end

Collapse this tableExpand this table
File nameVersion
Febecfg.dll6.0.5770.30
Iisproto.dll6.0.5770.30
Imap4fe.dll6.0.5770.30
Imap4svc.dll6.0.5770.30
Pop3fe.dll6.0.5770.30
Pop3svc.dll6.0.5770.30

NOTE: Because of file dependencies, this update requires Microsoft Exchange 2000 Server Service Pack 2.

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server. This problem was first corrected in Microsoft Exchange 2000 Server Service Pack 3.

↑ Back to the top

More information

After you apply this fix, increase the time-out value in accordance with your company needs. This time-out value does not affect a truly inactive client because the back-end server (which has time-out value of 10 minutes) times out a truly inactive client connection.

↑ Back to the top

Keywords: KB315902, kbfix, kbexchange2000sp3fix, kbexchange2000presp3fix, kberrmsg, kbbug

↑ Back to the top

Article Info
Article ID : 315902
Revision : 4
Created on : 2/19/2007
Published on : 2/19/2007
Exists online : False
Views : 252