Another Konica 8 series SMB scanning issue.

[BHM]

Just upgraded a 454 with a new 458 several weeks ago. The 454 never had any scanning issues.


Scanning to a Windows 2012 r2 Server.
Customer claims it will work for a short time and then start failing. Job logs shows server connect error.
I set up a scan to smb folder on a local computer and even when scan to the server fails, scanning to this local computer works fine.
When working to the server it can be slow at times and very fast at other times.
We put in a second test machine (308) and the same thing happens.
We put in a 364 this morning and it is working perfectly.

Can not figure out what out what on the 8 series could be causing erratic server connection errors while the 4 series works fine. At this customer's location, there are probably about 20 of the 4 series machines scanning fine to this server.

[Eresources]

Off the top of my head, things I'd look into:

SMB Version used.
Quick IP Filtering settings on the device.
Firmware Version 3.3 or 4.0?
Windows Updates on server?

[bsm2]

Check
Select an authentication method for SMB transmission according to your environment.
[NTLM v1]/[NTLM v2]/[NTLM v1/v2]: Select this to use the function in the NT domain environment. If you select [NTLM v1/v2], NTLMv1 authentication is performed when NTLMv2 authentication fails.
[Kerberos]: Select this to use the function in the Active Directory domain environment.
[Kerberos/NTLMv2/v1]: Select this to use the function in an environment both the Active Directory domain and NT domain exist. NTLMv2 authentication is performed when Kerberos authentication fails, and NTLMv1 authentication is performed when NTLMv2 authentication fails.
[NTLM v1] is specified by default.

[Brad6784]

Just upgraded a 454 with a new 458 several weeks ago. The 454 never had any scanning issues.


Scanning to a Windows 2012 r2 Server.
Customer claims it will work for a short time and then start failing. Job logs shows server connect error.
I set up a scan to smb folder on a local computer and even when scan to the server fails, scanning to this local computer works fine.
When working to the server it can be slow at times and very fast at other times.
We put in a second test machine (308) and the same thing happens.
We put in a 364 this morning and it is working perfectly.

Can not figure out what out what on the 8 series could be causing erratic server connection errors while the 4 series works fine. At this customer's location, there are probably about 20 of the 4 series machines scanning fine to this server.

I've had similar today, although my machine wasn't scanning to SMB folder at all, upgraded to the latest firmware, worked first try. I had a C258 at the same site worked straight out of the box.

[BHM]

Still fighting...


The 4 series machine works great. Copied every setting I could find from that machine.


NTLM1, SMB2, Dns servers
Same folder path and authentication account.
Upgraded to function 4.0. have not tried 4.1 yet.
Works for about an hour then starts getting timeout errors. While this is happening, it scans to a Win10 folder just fine.
Rebooting works a hour or so.
move machine to another building going through another switch.
Left a box of donuts for it.

[bsm2]

lets go with easy stuff
domain name entered?
are you using name of server? switch to hard ip address that removes dns
start there and see it it's gone

[BHM]

There are two threads on this same issue in case anyone is experiencing dejevue. (sp)


Konica is investigating and the temporary solution is installing base version f/w.