IT dude can't get scan to email working and has Exchange 2010. He advises there should be no auth info needed, use port 25, we use his email as admin email address and SMTP IS AN IP address. Does anyone have a utility to prove what is causing the failure or a Telnet command to prove that the issue is something in his setup. I had advised him to add the IP address of the copier to the exchange server to allow it to pass through but am not sure if he has done this correctly. Any advice yu guys would use to help issolate what the issue is would be greatly appreciated.
Scan to emal no go after update of Exchange server to 2010
Collapse
X
-
If your exchange server has been updated from 2003 to 2007 or 2010 i think you will have set up the smtp connector on exchange for email scanning or have you already done thisTheory is when you know all and nothing works. Practice is when all works and nobody knows why. In this case we have put together theory and practice: nothing works... and nobody knows why! (Albert Einstein)Comment
-
Make sure the copier is added as a user on the server, the copier has its own name and is editable. At least, this is true of all Konica Minolta machines...cannot speak for the others, though I would not be surprised they had the same feature.
This has been standard fair for exchange servers since 2003."Many years ago I chased a woman for almost two years, only to discover that her tastes were exactly like mine: we both were crazy about girls."
---Groucho Marx
Please do not PM me for questions related to Konica Minolta hardware.
I will not answer requests or questions there.
Please ask in the KM forum for the benefit of others to see the question and give their input.
Comment
-
Exchange 2007 and Exchange 2010 out of the box have greater security than Exchange 2003 and require correct credentials to work. There are ways around this, but you need to way up the pros and cons for each network.
1. Do what Stirton said and create a Machine Account from Exchange.
2. Whitelist the IP Address of the copier so that Exchange knows that everything from the IP is "Safe".
You will also need to make sure that you TLS/SSL are correct as Exchange 2007/2010 will enable these as default.
You can use the following Telnet commands to check connectivity, but it won't prove much on a 2007 / 2010 Exchange as you can't enter in authentication information.
Telnet - SMTP Commands (sending mail using telnet)
Hope this helps.Please don't ask me for firmware or service manuals as refusal often offends.Comment
-
I just had this happen a few weeks ago with some Ricoh gear.
Exchange 2010 requires that the user name must be the full email address for the admin sender's address, and not just the user name. EX: "jsmith@company.com" - not just "jsmith".
The customer's IT told me that this is new in 2010; it wasn't there in 2007 or below.“I think you should treat good friends like a fine wine. That’s why I keep mine locked up in the basement.” - Tim HawkinsComment
-
I just had this happen a few weeks ago with some Ricoh gear.
Exchange 2010 requires that the user name must be the full email address for the admin sender's address, and not just the user name. EX: "jsmith@company.com" - not just "jsmith".
The customer's IT told me that this is new in 2010; it wasn't there in 2007 or below.Yes, I am a nerd.
Gaming PC - check. Raspberry Pi - Check. Custom ROM on phone - check. Thick glasses - check.Comment
Comment