Skip to main content
Skip table of contents

Error 3: "Could not connect to server"

MYOB Exo Payroll is able to send payslips to the employees via email. These emails are sent via the company's mail server.

When emailing payslips, the Summary Slip report may show an 'Error 3 Could not connect to server' message for the employees who are being emailed. This message is caused when access to the port on the email server is being blocked so the report is unable to send the email payslips.

Port 25 is normally used by the mail server for the sending of emails. If access to this port is being blocked for any reason, the 'Error 3' message will occur and the emailing of the payslips will not happen. If mail-server is "Relaying" payslips and Username, Password, and Use SSL/TLS are all blank, ensure "Port:" is also blank and has not been set to 25.

Below are suggestions for what can be done to eliminate the 'Error 3' message and allow the emailing of the payslips to occur.

It is recommended to have IT Support perform the following if there is any confusion.

  • In a Dos Command Prompt screen on the pc, run a telnet command to port 25 on the mail server, e.g. telnet akmailserver 25. If the telnet command is unsuccessful, then access to the port needs to be arranged.
  • If there is an anti-virus program running on the pc, such as Nortons Anti-virus, this program could be blocking the access to the port on the mail server. Disable the anti-virus program, or setup an exception in the anti-virus program, when doing the emailing of the payslips.
  • A firewall could be blocking the access to the port on the mail server. As with the anti-virus program when doing the emailing of the payslips, disable the firewall or setup an exception in the firewall program.

Need more help? You can open the online help by pressing F1 on your keyboard while in your software.

You can also find more help resources on the MYOB Exo Employer Services Education Centre for Australia or New Zealand.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.