locked
Microsoft Exchange Imap4 service stopped RRS feed

  • Question

  • hi 

    I have Exchange 2013 

    2 Mailbox Servers and 2 CAS servers

    i have two problems 

    1- I changed the Value of the <Time-out settings> from default to 3600 and the <Unauthenticated time-out >to 120

    then i restart the cas server when i go to the IMAP4 windows service I can't start the service as below

    2- on the second server i don't change any thing but when i am trying to telnet the CAS server <telnet CAS server  143> 

    I did not receive any thing  and when i run the command netstat on the CAS server  i Found all the connection state to port 143 from any destination is <Time_Wait>

    FYI

     


    Mahmoud


    Thursday, November 12, 2015 11:31 AM

Answers

  • For some reason, you have a receive connector bound to port 143.  Remove that binding.

    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!

    • Proposed as answer by Ed CrowleyMVP Monday, November 16, 2015 8:31 AM
    • Marked as answer by Mahmoud Adel_ Tuesday, November 17, 2015 6:00 AM
    Monday, November 16, 2015 8:31 AM
  • This is because ImapProxy and PopProxy is Inactive when you check by this command Get-ServerComponentstate -Identity CAS-Server-Name,

    you can active it by this command : 

    Set-ServerComponentState -Identity CAS-Server-Name -Component imapproxy -Requester HealthAPI -State Active

    and

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

    BR,,


    Sunday, December 22, 2019 1:50 PM

All replies

  • 1.  On whose advice did you change those settings?

    2.  What is the result when you enter the telnet command?


    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!

    Friday, November 13, 2015 12:41 AM
  • Hi Mahmoud,

    Do your have restart Exchange server to confirm?
    Also ensure all Exchange service works well, especial Microsoft Exchange Active Directory Topology service.

    If this issue persists, help collect event log for further troubleshooting.


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Allen Wang
    TechNet Community Support

    Friday, November 13, 2015 9:35 AM
  • Hi Ed Crowley

    I changed the value on one of the CAS Servers on IMAP4 settings

    for the telnet result , <telnet cas server 143> its showing that it will open a balnk screen then after few seconds its closed and when I Found all the connection state to port 143 from any destination is <Time_Wait>


    Mahmoud

    Sunday, November 15, 2015 6:11 AM
  • Hi Allen

    yes I restart the server many times

    also all exchange services are running

    BR


    Mahmoud

    Sunday, November 15, 2015 6:16 AM
  • If you telnet to port 143 and the screen goes blank, that tells you that the server is listening on that port and IMAP is presumed to be working.

    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!

    Sunday, November 15, 2015 7:01 AM
  • the connection may take few seconds and then its closed 

    have a look on below sessions that state<time_wait> 

    any connection i tries to connect on port 143 their state is time_wait

    do you have idea what this mean 

    


    Mahmoud

    Sunday, November 15, 2015 7:17 AM
  • Hi 

    Any update please , have any one idea on this problem

    Regards


    Mahmoud

    Monday, November 16, 2015 6:05 AM
  • hi 

    I can start the service for IMAP4 only if i stopped the microsoft exchange frontend transport service


    Mahmoud

    Monday, November 16, 2015 7:40 AM
  • Enter the following command but enter the name of the server that you're having trouble with IMAP on.

    Get-ReceiveConnector -Server IMAP_Server_Name | FL Name,Bindings

    Get-SendConnector -Server IMAP_Server_Name | FL Name,Port


    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!

    Monday, November 16, 2015 7:47 AM
  • hi 

    the first command give me the Receive connectors 

    the second one I think its wrong <Get-SendConnector>

    I can start the service for IMAP4 only if i stopped the microsoft exchange frontend transport service

    Still i have the problem 


    Mahmoud

    Monday, November 16, 2015 7:54 AM
  • If you don't share the results, I can't help you.  Please post the complete unadulterated results.

    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!

    Monday, November 16, 2015 8:07 AM
  • thanks for your support 

    for the second command Get-SendConnector> I get Error

    please note If I stopped the exchange frontend transport service I can start the IMAP4 service


    Mahmoud

    Monday, November 16, 2015 8:13 AM
  • For some reason, you have a receive connector bound to port 143.  Remove that binding.

    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!

    • Proposed as answer by Ed CrowleyMVP Monday, November 16, 2015 8:31 AM
    • Marked as answer by Mahmoud Adel_ Tuesday, November 17, 2015 6:00 AM
    Monday, November 16, 2015 8:31 AM
  • thank you , the service working fine now 

    but now when i try to telnet the port 143 and port 25 on that server it showing it will open the session but after few seconds its closed as below and giving stat time_wait while the successful session state is established 

    and I find the below results using netsat when trying to connect


    Mahmoud

    Monday, November 16, 2015 9:00 AM
  • I don't know anything about that.  Have you tried connecting with a client?

    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!

    Monday, November 16, 2015 9:01 AM
  • I tried connect from different clients and servers  

    Mahmoud

    Monday, November 16, 2015 9:03 AM
  • The correct command for the send connectors should be:

    Get-SendConnector | FL Name,Port,SourceTransportServers
    Please enter that command, copy the text from the window and post it, please don't post a picture.

    On the sending side, have the client connect to SMTP TLS on port 587, the client submission port.

    Are both the frontend and backend IMAP services running?  The backend services are on the mailbox servers.


    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!



    Monday, November 16, 2015 9:13 AM
  • I receive this error 


    [PS] C:\>Get-SendConnector -Server spt-cas-ryv001 | FL Name,Port
    Creating a new session for implicit remoting of "Get-SendConnector" command...
    A parameter cannot be found that matches parameter name 'Server'.
        + CategoryInfo          : InvalidArgument: (:) [Get-SendConnector], ParameterBindingException
        + FullyQualifiedErrorId : NamedParameterNotFound,Get-SendConnector
        + PSComputerName        : spt-mbx-ryv001.saptco.local

    how could i verfiy  both the frontend and backend IMAP services running?


    Mahmoud

    Monday, November 16, 2015 9:32 AM
  • I run this command 

    Get-SendConnector | FL Name,Port


    Name : To Internet
    Port : 25

    Name : Service Relay Send Connector
    Port : 25


    Mahmoud

    Monday, November 16, 2015 9:41 AM
  • hi 

    do you think that the netsat state <Time_Wait> is a firewall problem

    because now i have the same issue on port 25 on one of the CAS servers 


    Mahmoud



    Monday, November 16, 2015 10:52 AM
  • Look in the Services MMC on all servers.

    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!

    Monday, November 16, 2015 5:24 PM
  • thanks ED for your support 

    Get-SendConnector | FL Name,Port,SourceTransportServers


    Name                   : To Internet
    Port                   : 25
    SourceTransportServers : {SPT-MBX-RYV002, SPT-MBX-RYV001}

    Name                   : Service Manager Relay Send Connector
    Port                   : 25
    SourceTransportServers : {SPT-MBX-RYV002, SPT-MBX-RYV001}


    Mahmoud


    Tuesday, November 17, 2015 6:05 AM
  • The send connectors look correct.  They aren't used by a client, just checking for port usage.

    Are you saying you can't connect to receive mail or send mail?

    For sending, you should be connecting the client to TLS port 587, the client submission port.


    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!

    Tuesday, November 17, 2015 7:27 AM
  • my problem now when I try to open a connection to port 25 on CAS1 from any other VLAN or same VLAN the session closed after about two seconds (empty screen)

    while when running the below command from CAS1 server to CAS1 on port 25 

    the SMTP service appears to working fine and I recived the <Microsoft SMTP MAIL Service ready>

    so I can telnet port  25 on CAS1 from the same server(CAS1) only while I can't telent port 25  from other VLAN or same VLAN

    as this a network issue ?


    Mahmoud

    Tuesday, November 17, 2015 12:10 PM
  • If your receive connector doesn't have anything for RemoteIPRanges, you have a network problem.

    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!


    Tuesday, November 17, 2015 8:56 PM
  • what do you mean <receive connector doesn't have anything for RemoteIPRanges>

    because I already have as the settings in the default Default Frontend for CAS1 as below 

    ::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff

    0.0.0.0-255.255.255.255




    Mahmoud

    Wednesday, November 18, 2015 6:13 AM
  • That means that all IPs are allowed to connect.  If you had a restriction, the client wouldn't be allowed to connect.  So that's not your problem.

    Now twice I've suggested that you connect using SMTP TLS on port 587.  Is there any particular reason you're ignoring my advice and attempting to connect using port 25?  The client submission connector on port 587 was provided specifically to make it easy for clients to connect without you having to fuss with receive connectors.


    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!


    Wednesday, November 18, 2015 6:37 AM
  • This is because ImapProxy and PopProxy is Inactive when you check by this command Get-ServerComponentstate -Identity CAS-Server-Name,

    you can active it by this command : 

    Set-ServerComponentState -Identity CAS-Server-Name -Component imapproxy -Requester HealthAPI -State Active

    and

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

    BR,,


    Sunday, December 22, 2019 1:50 PM