Office 365 woes..

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • sharphead
    Trusted Tech

    250+ Posts
    • Aug 2009
    • 282

    #1

    Office 365 woes..

    I have a customer who would be more clued in than me and had scan to office 365 setup and authenticating through SSL and working fine.

    In the past couple of days it has stopped.

    They have two MX2310u and a MX2301

    I tried changing the SSL encryption level in the security settings and this allowed it to do the SMTP test in the web browser but it still wouldn't scan.

    The certificate has TLS written on it. I was thinking maybe the copiers were too old to support it?

    Currently have the smtp server set to an open one.

    Any thoughts on getting it too authenticate?
  • bilyahn
    Service Manager

    1,000+ Posts
    • Dec 2006
    • 1462

    #2
    Re: Office 365 woes..

    Not sure if this relates but have had a lot of DNS issues lately with Sharps and authentication. Check to make sure your DNS settings are correct and try the authentication again. I try to use google's DNS settins but sometimes I have to work with their network router's settings to get it to work properly. Might even try a Microsoft DNS specific to Office 365?

    Good luck.

    Bil

    Comment

    • OlliK1969
      Trusted Tech

      250+ Posts
      • Nov 2016
      • 309

      #3
      Re: Office 365 woes..

      SMB1 active ??
      Change it to SMB2,

      "Special firmware for SMBv2 client support" from Sharp FTP-Server

      After "ramsoftware-attack", they have it change.

      Comment

      • sharphead
        Trusted Tech

        250+ Posts
        • Aug 2009
        • 282

        #4
        Re: Office 365 woes..

        Thanks for the replies. Randomly the DNS on one was set to google and on the other to their own. I'll look into a Microsoft specific one.

        Good shout on the firmware unfortunately there isn't a firmware for it in the MX2310 section. They are up to date anyway.

        Comment

        • MattL
          Technician

          50+ Posts
          • Apr 2012
          • 97

          #5
          Re: Office 365 woes..

          Under network settings, services, SMTP check the port as I think it needs to be 587 for it to work. Also check the firewall isn't blocking it.

          Now some of the older ones don't support some of the protocols mainly around TLS/secure port and will stop it from working. May need to try it on a standard port 25. I know the C250 didn't support scanning without changing the security level on the mail server which customer didn't want to do for 1 MFD.

          Comment

          • ZOOTECH
            Senior member of CRS

            Site Contributor
            2,500+ Posts
            • Jul 2007
            • 3383

            #6
            Re: Office 365 woes..

            I remember when Office 365 first came out, the reply email address had to have a "<" at the beginning and a ">" at the end - I don't know if this is still true?
            "You can't trust your eyes, if your mind is out of focus" --

            Comment

            • slimslob
              Retired

              Site Contributor
              25,000+ Posts
              • May 2013
              • 36276

              #7
              Re: Office 365 woes..

              Office 365 regular SMTP does require TLS/StartTLS. Merely change the port to 587 will not help if the device does not support TLS. You may need to have the customer's IT Department/Service set up an Office 365 SMTP relay. This will even work with older MFP that do not even support SSL. See Option 3 in the link below.

              How to set up a multifunction device or application to send email using Office 365 - Office 365

              Comment

              • sharphead
                Trusted Tech

                250+ Posts
                • Aug 2009
                • 282

                #8
                Re: Office 365 woes..

                Thanks slim i think this is the solution for the reasons you've outlined

                Comment

                Working...