Intermittent Scan to email funcitonality
-
Can you post a screenshot of the HP's SMTP settings?
-
We haven't seen that yet, so that'd be helpful.
-
Some HP printers print through an HP service.. any chance that's the case here, it's not actually sending email directly from the device, but instead it's coming through HP's cloud? and there might be a problem there?
-
@Dashrender said:
Some HP printers print through an HP service.. any chance that's the case here, it's not actually sending email directly from the device, but instead it's coming through HP's cloud? and there might be a problem there?
I hadn't thought of that. That's a very good idea.
-
@ajstringham said:
Can you post a screenshot of the HP's SMTP settings?
The first screenshots show the summary.
sending to 10.202.1.14
no SSL
authentication required.incoming screenshots.
-
@ajstringham said:
Use authentication for all of them. You said you have to go back and forth between auth and anon to get it to work. It sounds like a permissions issue, of some sort, to me. With what I know now, it's something on Exchange doing this. I'm just not familiar enough with Exchange on-premise to be of much use there.
I always use authentication for all devices unless I absolutely have to do anon. As a test I tried anon and it would also still fail. Switching back and forth did not make it work. It works intermittently on both methods.
-
As requested obviously I use a real email before I click test.
-
Put the @domain.com after the username. That's probably what's screwing it up.
-
@ajstringham said:
Put the @domain.com after the username. That's probably what's screwing it up.
Not on exchange 2010 it is not. All devices that do basic auth work on the username.
Recall that the one unit I have in the main office works every time, while programmed identically.
Additionally, the NAS and Gestetner at the branches also work perfectly with only the username.
-
@JaredBusch said:
@ajstringham said:
Put the @domain.com after the username. That's probably what's screwing it up.
Not on exchange 2010 it is not. All devices that do basic auth work on the username.
Recall that the one unit I have in the main office works every time, while programmed identically.
Additionally, the NAS and Gestetner at the branches also work perfectly with only the username.
All the same model printer?
-
@ajstringham said:
All the same model printer?
Same model, same firmware, same everything except on site not across the OpenVPN tunnel.
-
@JaredBusch said:
@ajstringham said:
All the same model printer?
Same model, same firmware, same everything except on site not across the OpenVPN tunnel.
That's just really weird. I'm out of ideas. Maybe @scottalanmiller can add something...
-
@ajstringham said:
That's just really weird. I'm out of ideas.
You are not the only one. I am so frustrated. Let alone how my users are feeling.
-
@JaredBusch said:
@ajstringham said:
That's just really weird. I'm out of ideas.
You are not the only one. I am so frustrated. Let alone how my users are feeling.
Is there a reason they can't scan to FTP? At least in the interim?
-
@ajstringham said:
Is there a reason they can't scan to FTP? At least in the interim?
Because, users.
Scan to network folder has worked fine this entire time.
-
@JaredBusch said:
@ajstringham said:
Is there a reason they can't scan to FTP? At least in the interim?
Because, users.
Scan to network folder has worked fine this entire time.
So basically they are just lazy? It's not freaking hard! Heck, if you must, map network drives via GPO for them. Done.
-
@JaredBusch said:
@ajstringham said:
Is there a reason they can't scan to FTP? At least in the interim?
Because, users.
Scan to network folder has worked fine this entire time.
I can get down with this problem. I have scan to issues all the time. though usually it's scan to folder with canon ir10xx series MFCs that I have problems with.
You've done your due diligence here for sure. you've checked your exchange logs to see if that's what's killing the sends? maybe "too much data" from a certain address? any exchange updates/patches in the recent past?
-
@Hubtech said:
@JaredBusch said:
@ajstringham said:
Is there a reason they can't scan to FTP? At least in the interim?
Because, users.
Scan to network folder has worked fine this entire time.
I can get down with this problem. I have scan to issues all the time. though usually it's scan to folder with canon ir10xx series MFCs that I have problems with.
You've done your due diligence here for sure. you've checked your exchange logs to see if that's what's killing the sends? maybe "too much data" from a certain address? any exchange updates/patches in the recent past?
That's a good point. How many pages are they trying to scan? Although if you can't even establish a test connection, that's a moot point...hmm....
-
@ajstringham said:
That's a good point. How many pages are they trying to scan? Although if you can't even establish a test connection, that's a moot point...hmm....
Number of pages is not relevant because the "test email" from the GUI fails also. That is a tiny text only email. That said 1 page or 5, does not matter, when it works it works.
-
The Gestetner pictured above has been in use all day today at the branch office that has it. It has not failed once.
The users have intermittently tried the HP all day also. It has worked 1 time.
