iR2535i cannot scan to email
When trying to send an email, the session times out after a minute and prints an TX error page (ND 0753). I've looked up the error and it just doesn't make sense. The users can print to the printer, copy, fax, scan, but not scan to e-mail.
Background:
The printer is on a TCP/IP network and it communicates with our Exchange server (2007). The printer is configured by DCHP. The users print via a Windows print server, and scan to our exchange server
A typical setup includes inputting the Server IP in the printer and using Hub Transport on the Exchange server. We typically leave all major setting blank, and only input reference data like the Host name, device location, and etc. We also add all of the users to an address book. We really don't change much. We do not require authentication, all Exchange does is forward the incoming mail to the correct user or user listed in the address book.
Update: We used "Network Monitor" to capture traffic to the Exchange server. In "blue" you will notice the client was not authenticated. TLS is involved in the authentication of the traffic, and we are figuring it has something to do with CA (certificate authority). However, unlike the other image runners we have, this little sucker came without a "default key"; how fortunate.
6366 2:45:22 PM 10/21/2011 56.0144993 edgetransport.exe RYPES04 172.19.8.145 SMTP SMTP:Rsp 530 5.7.1 Client was not authenticated, 40 bytes {TCP:364, IPv4:112}
How would I get a default key? I can't generate one with this particular model, there's not "generate" button.
ca.jpg
Background:
The printer is on a TCP/IP network and it communicates with our Exchange server (2007). The printer is configured by DCHP. The users print via a Windows print server, and scan to our exchange server
A typical setup includes inputting the Server IP in the printer and using Hub Transport on the Exchange server. We typically leave all major setting blank, and only input reference data like the Host name, device location, and etc. We also add all of the users to an address book. We really don't change much. We do not require authentication, all Exchange does is forward the incoming mail to the correct user or user listed in the address book.
Update: We used "Network Monitor" to capture traffic to the Exchange server. In "blue" you will notice the client was not authenticated. TLS is involved in the authentication of the traffic, and we are figuring it has something to do with CA (certificate authority). However, unlike the other image runners we have, this little sucker came without a "default key"; how fortunate.
6366 2:45:22 PM 10/21/2011 56.0144993 edgetransport.exe RYPES04 172.19.8.145 SMTP SMTP:Rsp 530 5.7.1 Client was not authenticated, 40 bytes {TCP:364, IPv4:112}
How would I get a default key? I can't generate one with this particular model, there's not "generate" button.
ca.jpg
Comment