ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Exchange 2013 Receive connector for Scan 2 Email

    IT Discussion
    4
    8
    673
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • G I JonesG
      G I Jones
      last edited by

      Trying to setup scan to email on some new xerox machines we got.

      Got everything working right, but it won't send to outside email addresses such as gmail.

      Did a little research and found that I need to setup a new receive connector to allow this.

      So I try making one with like so:

      • Name: Scan2email
      • Server: EXCHANGESERV.contoso.com
      • Role: Hub Transport
      • Type: Custom
      • Network Adapter Bindings: IP of EXCHANGESERV NIC
      • Port: 25
      • Remote Network Settings: IP of Xerox Machine on network

      I get the error message:
      "The Values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "EXCHANGESERV\Default Frontend EXCHANGESERV". Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings."

      So is it saying that I need to use a different port for each connector?

      The "Default Frontend EXCHANGESERV" receive connector is inclusive of all IP ranges, as it was set that way from the guy we paid to do it. I'm wondering how to move forward.

      1 Reply Last reply Reply Quote 0
      • jt1001001J
        jt1001001
        last edited by jt1001001

        We did a second ip on our Exchange server for all connectors like this; don't know if you can do that in your situation?

        G I JonesG 1 Reply Last reply Reply Quote 0
        • G I JonesG
          G I Jones
          last edited by

          Eh, I figured it out.

          Had to select FrontEnd Transport, and leave the all available IP instead of changing it to the EXCHANGESERV NIC.

          1 Reply Last reply Reply Quote 0
          • G I JonesG
            G I Jones @jt1001001
            last edited by

            @jt1001001 currently using a single NIC, but I think I got it. I’ll know tomorrow when I’m at work and can physically work with the xerox machines. Appreciate the reply.

            1 Reply Last reply Reply Quote 0
            • DashrenderD
              Dashrender
              last edited by

              Did it work?

              G I JonesG 1 Reply Last reply Reply Quote 0
              • dbeatoD
                dbeato
                last edited by

                To be able to send external users too, you need to do this in the Powershell:

                Get-ReceiveConnector -Identity "Scan relay" | Add-ADPermission -User "NT AUTHORITY\ANONYMOUS LOGON" -ExtendedRights "Ms-Exch-SMTP-Accept-Any-Recipient"
                
                1 Reply Last reply Reply Quote 0
                • dbeatoD
                  dbeato
                  last edited by

                  @G-I-Jones said in Exchange 2013 Receive connector for Scan 2 Email:

                  gs and RemoteIPRanges parameters conflict with the settings on Receive connector "EXCHANGESERV\Default Frontend EXCHANGESERV". Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings."

                  only one receive connector is needed.

                  1 Reply Last reply Reply Quote 0
                  • G I JonesG
                    G I Jones @Dashrender
                    last edited by

                    @Dashrender Yea, it worked.

                    1 Reply Last reply Reply Quote 0
                    • 1 / 1
                    • First post
                      Last post