Scanning to office 365

Collapse
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • engineers
    Technician

    50+ Posts
    • Feb 2008
    • 51
    #1

    Scanning to office 365

    Hi guys,
    I recently installed a load of machines into a new customer, they were actually migrating to brand new servers while I was on site. Their mail server changed to office 365 one.
    I managed to get scan to email working on 2x MPC3504ex machines, but with the same details I cannot for the life of me get it to work on a SP3610sf. Here are the details:
    Server name- smtp.office365.com
    Port- 587
    Authentication- On
    Auth username/email- scans365@customersname.com
    Password- ****** (trust me I triple checked this and it is right)
    Encryption- Auto (I think I did try on and off also)
    SSL- Set to active on web image monitor
    All ip/gateway/subnet and dns are correct
    sender name set to ON and its email is also scans365@customernsame.com as I know that is a big deal on office 365

    As I mentioned earlier these details are exactly the same as the 2 Bigger mfps that currently work. I have spoken to their IT and they tried everything they can but naturally in the end they said the server is obviously fine so it must be the Ricoh.
    The only option I have left is to try new firmware although that has brought me another problem because I have not seen firmware like this before (we don't really sell SP before now) It only has 3 firmware types and when extracted only 1 had the .fwu file and the others had loads of zipped folders with something called FirmwareUpdater inside, what is that?
    Also it does print fine and can scan to folders on the server fine and been tried in 2 different ports just for added detail.
    Anyone know anything I can try or has anyone else been stuck at this same problem where 1 machine works but the other doesn't?
    Thanks
    Tags: None
    • TonerMunkeh
      Professional Moron

      2,500+ Posts
      • Apr 2008
      • 3865
      #2
      Re: Scanning to office 365

      The Kibo controllers aren't capable of true SSL authentication. Use the customer's SMTP MX record as a scanning server with no authentication. Only problem is they can only scan to addresses within their domain.
      It's 106 miles to Chicago. We've got a full tank of gas, half a pack of cigarettes, it's dark and we're wearing sunglasses.

      Hit it.

        Comment

        • engineers
          Technician

          50+ Posts
          • Feb 2008
          • 51
          #3
          Re: Scanning to office 365

          So firmware will achieve nothing then. Ok I think it should be fine for them to only scan to themselves and not external.
          Is this MX record something their IT will have to provide or is it a generic term that I can find out for myself?
          Thanks for the reply

            Comment

            • TonerMunkeh
              Professional Moron

              2,500+ Posts
              • Apr 2008
              • 3865
              #4
              Re: Scanning to office 365

              Use https://mxtoolbox.com/ and input their domain name. It will tell you what their MX record is.
              It's 106 miles to Chicago. We've got a full tank of gas, half a pack of cigarettes, it's dark and we're wearing sunglasses.

              Hit it.

                Comment

                • engineers
                  Technician

                  50+ Posts
                  • Feb 2008
                  • 51
                  #5
                  Re: Scanning to office 365

                  Thanks for that, it doesn't actually find it though. Maybe because of recent server migration?
                  I'll just have to wrangle it out of their IT company

                    Comment

                    • bsm2
                      IT Manager

                      25,000+ Posts
                      • Feb 2008
                      • 29585
                      #6
                      Re: Scanning to office 365

                      check the date and time on machine if incorrect may cause problem

                        Comment

                        • engineers
                          Technician

                          50+ Posts
                          • Feb 2008
                          • 51
                          #7
                          Re: Scanning to office 365

                          Thanks TonerMunkeh. Their IT gave me MX records and followed your instructions and worked perfectly.
                          I call that case closed

                            Comment

                            • slimslob
                              Retired

                              Site Contributor
                              25,000+ Posts
                              • May 2013
                              • 37047
                              #8
                              Re: Scanning to office 365

                              Originally posted by TonerMunkeh
                              The Kibo controllers aren't capable of true SSL authentication. Use the customer's SMTP MX record as a scanning server with no authentication. Only problem is they can only scan to addresses within their domain.
                              For those wanting more information, attached a power point tech reference on the difference between the GW, KIBO and PR controllers. See SMTP notes on slide 12. Office 365 requires SMTP over TLS. Had to convert it to a PDF. KIBOCtrl_GWvsKIBOvsTyPR_TRv1.0.pdf

                                Comment

                                Previous template Next
                                Working...