Scan to Email Problems

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Copier Doc
    Technician
    • Mar 2010
    • 49

    #1

    Scan to Email Problems

    Hi Guys, wondered whether anyone can shed some light on this.
    Installed a new MX2314 & refurb MX2300 to same site & network, scan to email i have always used my own smtp server without problems in the past, but, MX2314 works fine but MX2300, despite same credentuals being entered refuses to co-operate!
    Connection to SMTP states as succeeded but i get the message saying 'connection to server was lost' when trying to send outgoing email?
    I have tried Gmail accounts & Hotmail accounts details also but to no avail.
    Firmware is upto date & i have done 100's of these age of machines with no problem apart from this one, network issue? Why does the 2314 work then? Suggestion appreciated. Thanks in advance.
  • Akitu
    Legendary Frost Spec Tech

    Site Contributor
    2,500+ Posts
    • Oct 2010
    • 2595

    #2
    Re: Scan to Email Problems

    Originally posted by Copier Doc
    Hi Guys, wondered whether anyone can shed some light on this.
    Installed a new MX2314 & refurb MX2300 to same site & network, scan to email i have always used my own smtp server without problems in the past, but, MX2314 works fine but MX2300, despite same credentuals being entered refuses to co-operate!
    Connection to SMTP states as succeeded but i get the message saying 'connection to server was lost' when trying to send outgoing email?
    I have tried Gmail accounts & Hotmail accounts details also but to no avail.
    Firmware is upto date & i have done 100's of these age of machines with no problem apart from this one, network issue? Why does the 2314 work then? Suggestion appreciated. Thanks in advance.
    You say the firmware is up to date, but you can't get Gmail or Hotmail to work, both of which require SSL. I would double check your firmware version on the 2300 to be sure. Does your SMTP server require SSL? Is the firewall blocking the IP address of the 2300? Is there an IP conflict anywhere on the network?

    If all else fails, you could potentially have a faulty NIC on the 2300 and may need to do some swapping.
    Cthulhu for president! Why settle for the lesser evil?

    Comment

    • MHeon71
      Trusted Tech

      Site Contributor
      250+ Posts
      • Oct 2008
      • 489

      #3
      Re: Scan to Email Problems

      I believe Gmail requires SSL and I know some older copiers do not have SSL option.

      Comment

      • glewisme
        Trusted Tech

        100+ Posts
        • Nov 2009
        • 240

        #4
        Re: Scan to Email Problems

        I do believe the newest firmware will allow you to enable SSL, so you can setup scan to email.

        Comment

        • Akitu
          Legendary Frost Spec Tech

          Site Contributor
          2,500+ Posts
          • Oct 2010
          • 2595

          #5
          Re: Scan to Email Problems

          Originally posted by glewisme
          I do believe the newest firmware will allow you to enable SSL, so you can setup scan to email.
          ^ This. F00 is the firmware version, oddly enough Sharp produced an SSL support option for the 2300/2700 but not the 3501/4501. I have custom firmware for SSL support on those models presently, I haven't checked the latest official release to see if it was updated with SSL support however.
          Cthulhu for president! Why settle for the lesser evil?

          Comment

          • Ceechtay
            Trusted Tech

            Site Contributor
            100+ Posts
            • Sep 2011
            • 157

            #6
            Re: Scan to Email Problems

            Also, make certain that the default gateway and subnet mask are correct for the MX-2300. I had exact same message of connection being lost when I fat-fingered the default gateway recently.

            The copier could still do local scanning and I could access the webpage, but anything having to leave the local subnet would fail (since it was sending that traffic to a wrong, non-existent IP address).

            Comment

            Working...