none
POP works via localhost but not from other networked machines RRS feed

  • Question

  • Hello All

    I have three servers in an Exchange 2013 DAG.  Lets call them EX2013-MB1, MB2 and MB3.

    I have configured POP Across the board.  All of a sudden the other day POP stopped working on MB1.  After some troubleshooting, if I launch a telnet session to port 110 from MB1, it connects and works fine.  Any other machine, nothing, connection immediately drops.

    I have the firewall disabled, so it's not the firewall blocking the connection by any means.

    Any ideas?  Below are my Get-PopSettings, and Test-PopConnectivity

    [PS] C:\Windows\system32>Get-PopSettings | FL


    RunspaceId                        : 66d8dee7-2a6e-4fbe-9b20-a15e79da7978
    Name                              : 1
    ProtocolName                      : POP3
    MaxCommandSize                    : 512
    MessageRetrievalSortOrder         : Ascending
    UnencryptedOrTLSBindings          : {0.0.0.0:110}
    SSLBindings                       : {0.0.0.0:995}
    InternalConnectionSettings        : {EX2013-MB1.PRIVATE DOMAIN.com:995:SSL, EX2013-MB1.PRIVATE DOMAIN.com:110:TLS}
    ExternalConnectionSettings        : {}
    X509CertificateName               : EX2013-MB1
    Banner                            : The Microsoft Exchange POP3 service is ready.
    LoginType                         : PlainTextLogin
    AuthenticatedConnectionTimeout    : 00:30:00
    PreAuthenticatedConnectionTimeout : 00:01:00
    MaxConnections                    : 2147483647
    MaxConnectionFromSingleIP         : 2147483647
    MaxConnectionsPerUser             : 16
    MessageRetrievalMimeFormat        : BestBodyFormat
    ProxyTargetPort                   : 9955
    CalendarItemRetrievalOption       : iCalendar
    OwaServerUrl                      :
    EnableExactRFC822Size             : False
    LiveIdBasicAuthReplacement        : False
    SuppressReadReceipt               : False
    ProtocolLogEnabled                : True
    EnforceCertificateErrors          : False
    LogFileLocation                   : C:\Program Files\Microsoft\Exchange Server\V15\Logging\Pop3
    LogFileRollOverSettings           : Daily
    LogPerFileSizeQuota               : 0 B (0 bytes)
    ExtendedProtectionPolicy          : None
    EnableGSSAPIAndNTLMAuth           : True
    Server                            : EX2013-MB1
    AdminDisplayName                  :
    ExchangeVersion                   : 0.10 (14.0.100.0)
    DistinguishedName                 : CN=1,CN=POP3,CN=Protocols,CN=EX2013-MB1,CN=Servers,CN=Exchange Administrative
                                        Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=FH Paschen,CN=Microsoft
                                        Exchange,CN=Services,CN=Configuration,DC=PRIVATE DOMAIN,DC=com
    Identity                          : EX2013-MB1\1
    Guid                              : 83942b2a-5dff-4b63-b33b-234944c2bc46
    ObjectCategory                    : PRIVATE DOMAIN.com/Configuration/Schema/ms-Exch-Protocol-Cfg-POP-Server
    ObjectClass                       : {top, protocolCfg, protocolCfgPOP, protocolCfgPOPServer}
    WhenChanged                       : 7/10/2014 3:28:48 PM
    WhenCreated                       : 12/24/2013 11:04:05 AM
    WhenChangedUTC                    : 7/10/2014 8:28:48 PM
    WhenCreatedUTC                    : 12/24/2013 5:04:05 PM
    OrganizationId                    :
    OriginatingServer                 : FHP-DS8.PRIVATE DOMAIN.com
    IsValid                           : True
    ObjectState                       : Unchanged



    RunspaceId                  : 66d8dee7-2a6e-4fbe-9b20-a15e79da7978
    LocalSite                   : MainOffice
    SecureAccess                : False
    VirtualDirectoryName        :
    Url                         :
    UrlType                     : Unknown
    Port                        : 995
    ConnectionType              : Ssl
    ClientAccessServerShortName : EX2013-MB1
    LocalSiteShortName          : MainOffice
    ClientAccessServer          : EX2013-MB1.PRIVATE_DOMAIN.com
    Scenario                    : Test POP3 Connectivity
    ScenarioDescription         : Connect to server using POP3 protocol, search for the test message, and delete it along
                                  with any messages that are older than 24 hours.
    PerformanceCounterName      : POPConnectivity-Latency
    Result                      : Failure
    Error                       : Microsoft.Exchange.Monitoring.ProtocolException: Authentication failed. The connection
                                  is being closed.
                                  Unable to read data from the transport connection: An established connection was aborted
                                  by the software in your host machine.Server response while making connection:[]. --->
                                  System.IO.IOException: Unable to read data from the transport connection: An established
                                  connection was aborted by the software in your host machine. --->
                                  System.Net.Sockets.SocketException: An established connection was aborted by the
                                  software in your host machine
    UserName                    : extest_08569ee75e264
    StartTime                   : 7/10/2014 4:02:33 PM
    Latency                     : 00:00:00.0359767
    EventType                   : Error
    LatencyInMillisecondsString :
    Identity                    :
    IsValid                     : True
    ObjectState                 : New

    Thursday, July 10, 2014 9:03 PM

Answers

  • >>>WhenChanged                       : 7/10/2014 3:28:48 PM
    >>>WhenCreated                       : 12/24/2013 11:04:05 AM

    Hi,

    From the PopSettings information, I found that you recently modified pop3 settings.

    Did you try to recover the settings and check if the issue persist?

    What's the result if you launch a telnet session to port 110 from other networked machine?

    In addition, you should check if the user have the permission to access pop3.

    Hope this helps!

    Thanks.


    Allen Li
    TechNet Community Support

    Friday, July 11, 2014 2:56 AM
    Moderator

All replies

  • >>>WhenChanged                       : 7/10/2014 3:28:48 PM
    >>>WhenCreated                       : 12/24/2013 11:04:05 AM

    Hi,

    From the PopSettings information, I found that you recently modified pop3 settings.

    Did you try to recover the settings and check if the issue persist?

    What's the result if you launch a telnet session to port 110 from other networked machine?

    In addition, you should check if the user have the permission to access pop3.

    Hope this helps!

    Thanks.


    Allen Li
    TechNet Community Support

    Friday, July 11, 2014 2:56 AM
    Moderator
  • Hi,

    Any update?

    Thanks.


    Niko Cheng
    TechNet Community Support

    Monday, July 14, 2014 2:40 AM
    Moderator
  • Any updates?  I am having this EXACT same issue!  I have 2 boxes in a DAG, and after a period of time, POP3 decides on my 2nd box that it will no longer accept connections.  Locally on the box, I am able to telnet to port 110 without issue.  Firewall is disabled.

    Monday, July 21, 2014 1:47 PM
  • Well, I found the source of my problem, but don't understand why ...

    Get-ServerComponentstate -Identity CHIEXC02

    Found that the PopProxy Component was inactive, looking in Event logs, found it was bumped to inactive by HealthAPI.

    Set-ServerComponentState -Identity CHIEXC02 -Component PopProxy -Requester HealthAPI -State Active

    Kicked the component active again, and now POP3 responds from the external IPs.

    Having said that, I really want to understand what caused HealthAPI to kick it to Inactive, and why it doesn't kick itself back to active?  Obviously it's a healthcheck that failed.  Now I need to understand WHY.

    • Proposed as answer by Jason Sherry Tuesday, August 19, 2014 10:06 PM
    Monday, July 21, 2014 3:02 PM
  • Just ran into the same issue on a new setup of Exchange 2013. Like you I don't know why this happened, but setting it to Active fixed the issue for me too.

    I blogged about it here and hope this helps others find the issue.

    http://blog.jasonsherry.net/2014/08/19/exchange-2013-pop3-service-drops-connections-fix/


    Jason Sherry | Blog | Twitter: @JasonSherry
    Microsoft Infrastructure Architect, MCSE: M, MCTIP, Microsoft Exchange MVP


    Tuesday, August 19, 2014 10:11 PM
  • Ran into this same issue but with ImapProxy being Inactive.

    Spent hours checking everything but this, so a big thank you for this post.

    Scary thing was that I couldn't find any error logs anywhere, let alone any that would've of pointed towards checking the Component State!

    Thanks again.

    Friday, October 3, 2014 2:19 AM
  • Just wanted to say "I love you" :)

    Been busting my head with this for 3 hours now and your post saved my day :)

    Thanks for sharing.

    Monday, October 13, 2014 9:49 AM
  • I have the same issue but with IMAP4 (993) service.

    Get-ServerComponentState -Identitty <name exchange server>

    Set-ServerComponentState -Idenntity <name exchange server> -Component ImapProxy -Requestor HealthAPI -Satate Active

    resolve problem


    Truly, Valery Tyurin


    Friday, March 13, 2015 11:35 AM
  • Hi,

    Thank you for your help, we have the same problem.

    Is anybody here find the reason of this drop?

    It's quite something.... I cannot believe it simply drops without any reason...

    If anybody have the cause, I take it....

    Kind Regards.


    • Edited by Sontae Wednesday, October 7, 2015 2:02 PM
    Wednesday, October 7, 2015 2:02 PM
  • Yes, this was the same for me...but on a brand new Exchange 2016 server.

    It was the same for IMAP also.

    Thanks for providing this information back to the community.

    Mark

    Tuesday, January 19, 2016 6:17 AM
  • I found this solution:

    The issue was that the “State” of the PopProxy component was set to Inactive:

    [PS] D:\>Get-ServerComponentstate -Identity SRVDENEX01

    Server Component State
    —— ——— —–
    SRVDENEX01.company.com ServerWideOffline Active
    SRVDENEX01.company.com HubTransport Active
    SRVDENEX01.company.com FrontendTransport Active
    SRVDENEX01.company.com Monitoring Active
    SRVDENEX01.company.com RecoveryActionsEnabled Active
    SRVDENEX01.company.com AutoDiscoverProxy Active
    SRVDENEX01.company.com ActiveSyncProxy Active
    SRVDENEX01.company.com EcpProxy Active
    SRVDENEX01.company.com EwsProxy Active
    SRVDENEX01.company.com ImapProxy Active
    SRVDENEX01.company.com OabProxy Active
    SRVDENEX01.company.com OwaProxy Active
    SRVDENEX01.company.com PopProxy Inactive
    SRVDENEX01.company.com PushNotificationsProxy Active
    SRVDENEX01.company.com RpsProxy Active
    SRVDENEX01.company.com RwsProxy Active
    SRVDENEX01.company.com RpcProxy Active
    SRVDENEX01.company.com UMCallRouter Active
    SRVDENEX01.company.com XropProxy Active
    SRVDENEX01.company.com HttpProxyAvailabilityGroup Active
    SRVDENEX01.company.com ForwardSyncDaemon Active
    SRVDENEX01.company.com ProvisioningRps Active
    SRVDENEX01.company.com MapiProxy Active
    SRVDENEX01.company.com EdgeTransport Active
    SRVDENEX01.company.com HighAvailability Active
    SRVDENEX01.company.com SharedCache Active

    A quick call to Set-ServerComponentState to mark this component Active fixed the issue:

    Set-ServerComponentState -Identity SRVDENEX01 -Component PopProxy -Requester HealthAPI -State Active

    After doing this POP started responding as expected, using any valid hostname or IP address.


    Tuesday, January 19, 2016 10:56 AM
  • The set  active command only brings it up for some time, my server keeps going inactive a couple of days.  It's strange there is no fix from Micrsoft for years. It seems an apparent bug. Even for Exchange 2016.  Can we make the voice a little louder and invite Microsoft to involve?  

    Regards

    Wednesday, October 12, 2016 9:07 AM
  • This worked for me too, POP3 has been up and running fine for 3 years, then this kicked to inactive.  Setting it back to active and walah POP services restored.

    Did you ever find out why it flipped over to inactive?

    Friday, March 24, 2017 3:25 PM