Logout

Alt-N Discussion Groups > Outlook Connector Discussion Groups > Outlook Connector Support > Sometimes can't connect

 [F] Alt-N Discussion Groups  / Outlook Connector Discussion Groups  / Outlook Connector Support  /

Sometimes can't connect

[Zwaan, Jacques van der]
Jacques van der…
Newbie
Newbie
Posts: 13
Jacques van der Zwaan - 07:55am, Jun 11 2020

I am experiencing the following under Outlook 2016 with OC 6.5.1 (23 bit).

It happens a lot when Outlook is started, the message apears that OC can not connect to the server, with the option to retry or cancel. When I click on retry (sometimes I need to press it 2 times), it works.

People are sometimes waiting a long time while nothing is happening, this is because the OC message pops up under the Outlook starting screen.

Is there a reason why this is happening and how can I solve it?

  All MessagesOldest ItemsOlder ItemsNewer ItemsNewest Items

David C - Jun 15, 2020 7:09 pm (#1 Total: 2)  

 

Photo of Author
David C
Guru
Guru
Posts: 1418
One can use the Microsoft "telnet" command to test network connectivity.

The following knowledge base articles describes how to connect to MDaemon's SMTP service and send an email. You can also use Microsoft's "telnet" command to connect to other MDaemon services (IMAP, POP3, HTTP, etc.)



KB 409 Using the Telnet client to open a SMTP session and/or send a message

https://www.altn.com/Support/KnowledgeBase/KnowledgeBaseResults?Number=409



Install the Microsoft telnet client on all of your end-user workstations find the host name or IP address and network port that Outlook/MDaemon connector is configured to use to connect to your copy of MDaemon. When next the issue you describe occurs, open a command prompt and issue a telnet command to connect to the host name or IP address on the same network port as Outlook/MDaemon Connector.

When you do this, does telnet appear to connect to something, or do you get a warning that the connection timed out?



Is this an MDaemon Connector issue, or does something similar happen when using the IMAP email protocol?

On the workstation of the affected end-user, create a new Outlook mail profile that will use the IMAP email protocol to connect the email account of the affected user. One does not have to delete the existing mail profile. We are merely creating a new Outlook mail profile for testing.

Open Outlook using the new Outlook/IMAP mail profile.

Does the issue you describe occur when using the new Outlook mail profile rather than the Outlook/MDaemon Connector profile?

[Last Editor: David C, Jun 15, 2020 7:14 pm. Total Edits: 2]

David C - Jun 15, 2020 7:12 pm (#2 Total: 2)  

 

Photo of Author
David C
Guru
Guru
Posts: 1418
You stated:

) "It happens a lot when Outlook is started, the message apears that OC can not connect to the server, with the option to retry or cancel. When I click on retry (sometimes I need to press it 2 times), it works."



First check your MDaemon logs to see what they show is happening when the issue occurs.

Open your MDaemon "System" log (default location: "/MDaemon/Logs/MDaemon-yyyy-mm-dd-System.log") and look for entries that say "IMAP server too busy", "SMTP server too busy", or "POP3 server too busy". The presense of such entries means that the number of inbound counnections for a particular protocol exceeds the number that you have configured your copy of MDaemon to allow. You will have to increase to so that that warning goes away.

View the following page from the MDaemon online "Help" file to see the default maximum numbers of "IMAP", "POP3", and "SMTP" sessions that your copy of MDaemon is currently configured to allow. Modify the settings if needed.



MDaemon Connector piggybacks on the SMTP and IMAP protocols for communicating with the MDaemon server.

When you open Outlook/MDaemon Connector, it attempts to connect to the IMAP service to synchronize the contents of your Outlook folders with the corresponding folders on the server. When this issue occurs, do the following:

1) Make a note of the date/time that the issue occurred

2) Make a note of the IP address of the computer on which the issue occurred as it would appear in the MDaemon log files. If the affected end-user workstation is on the same network as MDaemon and it it connecting to MDaemon using a LAN IP address, you can open a command prompt and issue the command "ipconfig" to see the LAN IP address. If the computer is connecting to MDaemon via the internet and an internet IP address, go to the URL "http://icanhazip.com/" to see the internet IP address of the affected workstation.

3)Open your IMAP log file (default location: "/MDaemon/Logs/MDaemon-yyyy-mm-dd-IMAP.log") and around the date/time that the issue you describe occurred, look for a connection from the IP address of the affected workstation. This will look similar to the following:

  • Mon 2020-06-15 18:03:32.358: 05: [317570] Accepting IMAP connection from 10.20.40.35:64149 to 10.20.40.35:143

    Do you see such a connection at all? If so, on which network port is the connection being made? Network port 143 (Non-SSL IMAP port)? Network port 993 (SSL IMAP port)? Are your end-user attempting to establish TLS connections on network port 143?

    Do you see any errors when the connection is made?



    Perform the steps above on your MDaemon Connector log file as well.

    1) Open your MDaemon Connector log file (default location: "/MDaemon/Logs/MDaemon-yyyy-mm-dd-MDaemon-Connector.log") and around the date/time that the issue you describe occurred, look for a connection from the IP address of the affected workstation. This will look similar to the following:

  • Mon 2020-06-15 18:03:32.358: 05: [317570] Accepting IMAP connection from 10.20.40.35:64149 to 10.20.40.35:143

    2) Do you see such a connection at all? If so, on which network port is the connection being made? Network port 143 (Non-SSL IMAP port)? Network port 993 (SSL IMAP port)? Are your end-user attempting to establish TLS connections on network port 143?

    3) Do you see any errors when the connection is made.

    You have to check both of these logs because if the inbound IMAP connection does not successfully identify itself as being from an account that is authorized to use MDaemon Connector (which means that the end-user must first successfully connect to the IMAP service and authenticate) then the connection activity will be stored in the "IMAP" log file rather than the "MDaemon Connector" log file.





    One can use the Microsoft "telnet" command to test network connectivity.

    The following knowledge base articles describes how to connect to MDaemon'



  •   All MessagesOldest ItemsOlder ItemsNewer ItemsNewest Items



     Content:

    Read New | Search

     Guest:

    Email to Admin



    You are visiting as a Guest user.