asked on

Lanier LD630C Scan to Email Fails

I have recently installed Exchange 2013 and have it operational. We have a Lanier LD630C that we use the scan to email function on. If we send an email to an address from within our domain, they receive the email. If we email someone outside the domain it populates the error:

Connection with the destination has failed. Check the status and connection. To check the current status press [Scanned Files Status].

When I click on "Scanned Files Status" it says "Status: Error".

We also have a McAfee SAAS email filter. I have talked to McAfee and we tried a few things and they don't think that the problem is with their spam filter.

Any help would be greatly appreciated!

Jon Covalt

It sounds to me like the Exchange server is refusing the IP address of the printer when sending it out through it's external Send Connector. Check to see if the printer's IP address is included in the range of machines allowed to use that connector. (Or you could just create a send connector for the printer, if you have some reason to isolate it to its own send connector to the Internet.)

ASKER CERTIFIED SOLUTION

Simon Butler (Sembee)

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

SOLUTION

Gareth Gudger

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

ollybuba

ASKER

Adding the receive connector didn't seem to help. Do I need to add a new host record like it states?

Simon Butler (Sembee)

You shouldn't need a new host record or anything like that.
I would enable logging on the new receive connector so you can see whether
a. The scanner/printer is actually connecting.
b. It is coming from the right IP address (as seen by Exchange).

Don't forget to restart the transport service after enabling logging but before your testing.

Simon.

ollybuba

ASKER

I've looked in these locations and I can't find a file that has a date and time stamp relative to when I attempt to send an email through the copier.

Receive connector protocol log files for the Transport service on Mailbox servers %ExchangeInstallPath%TransportRoles\Logs\Hub\ProtocolLog\SmtpReceive

Receive connector protocol log files for the Mailbox Transport service on Mailbox servers %ExchangeInstallPath%TransportRoles\Logs\Mailbox\ProtocolLog\SmtpReceive

Receive connector protocol log files for the Front End Transport service on Client Access servers %ExchangeInstallPath%TransportRoles\Logs\FrontEnd\ProtocolLog\SmtpReceive

Gareth Gudger

These logs may only be refreshing every day. Go through the current log and see if you can locate the date and time in the log itself. I am wondering if your scan is too big for the receive connector.

ollybuba

ASKER

2014-05-29T13:45:17.815Z,EXServer\Printer External Relay EXServer,08D14469A55E6D94,16,10.0.10.19:25,10.0.10.201:65339,>,250 2.1.0 Sender OK,
2014-05-29T13:45:17.815Z,EXServer\Printer External Relay EXSERVER,08D14469A55E6D94,17,10.0.10.19:25,10.0.10.201:65339,<,RCPT TO:<emailaddress@gmail.com>,
2014-05-29T13:45:17.815Z,EXSERVER\Printer External Relay EXSERVER,08D14469A55E6D94,18,10.0.10.19:25,10.0.10.201:65339,*,Tarpit for '0.00:00:05',
2014-05-29T13:45:22.831Z,EXSERVER\Printer External Relay EXSERVER,08D14469A55E6D94,19,10.0.10.19:25,10.0.10.201:65339,>,550 5.7.1 Unable to relay,
2014-05-29T13:45:22.831Z,EXSERVER\Printer External Relay EXSERVER,08D14469A55E6D94,20,10.0.10.19:25,10.0.10.201:65339,<,QUIT,
2014-05-29T13:45:22.831Z,EXSERVER\Printer External Relay EXSERVER,08D14469A55E6D94,21,10.0.10.19:25,10.0.10.201:65339,>,221 2.0.0 Service closing transmission channel,

ollybuba

ASKER

It was a relay problem. I ran this script and it made it work.

Get-ReceiveConnector -Identity "your Relay" | Add-ADPermission -User "NT AUTHORITY\ANONYMOUS LOGON" -ExtendedRights "Ms-Exch-SMTP-Accept-Any-Recipient"

Gareth Gudger

Yep. That SMTP log definitely confirmed that. Glad you got it working!