KM C550 BizHub scan to SMB failed, deleted due to login error?

[Natedog]

KM C550 BizHub scan to SMB failed, deleted due to login error? I have several users setup to scan to email and to SMB (shared folders on filerserver), one of the SMBs stopped working the other day and I have tried everything that I can think of and it still fails and gives the same error. Other users (myself included) can scan to email and to our own SMB folders on the server.

The particular SMB account with the problem is a folder on the server that several people in the dept have access to. They scan to this shared folder and then reach it via a mapped drive (while logged into thier computer as themself.) The SMB is a user account that is used as an external email contact. I have double-checked the security and permissions on the SMB account and the person's account who is doing the scannning and everything looks ok. I reset the copier (turned on/off), rebooted the user's pc, reset the password for the scan to SMB account (via web IP access to Konica copier), checked that neither user account was locked out, SMB scan to user account password is (and always was) set to never expire, even deleted and recreated the scan to SMB account on the copier! Searched and have found nothing on the net (including Konica's site) that has helped yet.

A couple weeks ago I had to reset this user's network password because it had expired, but then it has worked fine for about one month until now.

Any suggestions?

[Natedog]

OK, I even added a second similar named scan to SMB account and set it up with same userid and it got same error when scanning. Changed the userid to myself (with my password) and it worked fine, so I then changed it back to the original user without entering any password (who had the scan problem) and it worked. The next day it was broken again, so I entered the user's current network password into the SMB setup with her userid and it works fine now. Only thing that I can think of is that somehow the Konica got stuck on the user's old password and to get it unstuck it needed a different userid (and password) entered in. HTH

[random]

user needs to setup as

workgroup\user with workgroup being the name of the workgroup or domain.

[Natedog]

user needs to setup as

workgroupuser with workgroup being the name of the workgroup or domain.

In the setup on the KM I have the Host Address, File Path (for scan to store directly to it), Userid, and Password and this works for all users scan to smb. All users are members of the network domain. Please elaborate on your explanation.

[KonicaNet]

Konica controllers do not use the workgroup (or domain)/user method. Only the username. Your NVRAM might be going, or need to be cleared if it keeps happending.

[TheOwl]

I have had similar issues with these devices, but I have been able to solve all my issues by changing a setting on the machine through the Web Interface.

Logon as Admin - Network - SMB - Client - NTLM

Make sure that your NTLM version is set to v1/v2. This makes sure that the machine will authenticate to both local usernames and AD usernames.

Also, when recreating usernames, make sure that 'User must change Password at next logon' isn't ticked because this will also stop the machine from logging in correctly.

Also, try using FQ usernames in the machine. IE:

copier@example.internal or what ever your internal domain is as some can be .internal, some might be .com and so on.

If you have a separate account for the copier, check the security logs on your server as they will give login and log out audits. Macke sure that the machine is deffinately trying to logon correctly.

[jake714]

I've seen this one also. Double check the event viewer and the pc under Application to confirm there on no issues with locating the domain controllers. The source is AutoEnrollment error.

[Natedog]

Konica controllers do not use the workgroup (or domain)/user method. Only the username...

Correct and hope the NVRAM isn't going....pretty new machine. :eek: It is still working, knock on wood.

The Owl, good suggestions. I'll check the NTLM setting.

[acepump]

OK, I even added a second similar named scan to SMB account and set it up with same userid and it got same error when scanning. Changed the userid to myself (with my password) and it worked fine, so I then changed it back to the original user without entering any password (who had the scan problem) and it worked. The next day it was broken again, so I entered the user's current network password into the SMB setup with her userid and it works fine now. Only thing that I can think of is that somehow the Konica got stuck on the user's old password and to get it unstuck it needed a different userid (and password) entered in. HTH
Natedog, I was so lucky to find your post 4 years after. I got the same frustration as you after trying everything in the networking field to make two users to get rid of the Login Error message. The rest of the domain users were able to scan without any problem. As you suggested the problem was gone by login in as the problem users during the SMB setup. After getting my two users up and and running I followed TheOwl suggestion to set up NTLM setting to v1/v2 to avoid future issues. THANK YOU !!

[Natedog]

Natedog, I was so lucky to find your post 4 years after. I got the same frustration as you after trying everything in the networking field to make two users to get rid of the Login Error message. The rest of the domain users were able to scan without any problem. As you suggested the problem was gone by login in as the problem users during the SMB setup. After getting my two users up and and running I followed TheOwl suggestion to set up NTLM setting to v1/v2 to avoid future issues. THANK YOU !!

Excellent, glad you found this thread and it helped you out! It bugs me when people post questions, find an answer and then don't update how they fixed it...lol.

[grizinthebigsky]

Thank you for the information. This worked perfectly after many failed attempts and choice expletives.

Kudos!

[SafeForPandas]

So glad I found this thread even though it is 4 years since the last response. We are a small company renting a bizhub C280 and have had problems setting up the scanning, the company who provides the printer aren't particularly great at offering tech support beyond the initial set up. Although it's a different model, the menus and setups appear very similar.

I have encountered all of the problems in this thread separately, and each of the solutions offered has worked. I've also come across and additional issue causing the "Login Failed" error message.

Due to being a very small company and office, we are using a simple LAN system with no local servers or network drives, just individual PCs connected to a LAN. Recently, due to some staff changes, we had a few desk swaps and simply changed the usernames on the various PCs (we're running Windows 10 and all our storage is done via OneDrive and Sharepoint). I therefore changed all the SMB addresses accordingly and ensure all usernames, passwords, host addresses and file paths were 100% correct. Additionally, NTLM was set to v1/v2 and SMB setting were correct. Despite everything being 100% correct, we were getting login failures for all the PCs which had changed usernames. Scanning on all the PCs which had no changes was still working absolutely fine.

I discovered that the problem was due to only changing Windows 10 user names on the PCs, rather than deleting users and creating new ones. Consequently, whilst the user names had changed, the user proflie folder had not. This was what was causing the login error. I found that changing the username on the bizhub address book to match the name of the user profile folder corrected this error (e.g. user profile folder is C:\Users\User 1, user name has been changed to User 2, password is 12345678, you would need to enter User 1 as the username in the bizhub address book and password as 12345678).

Thought this was worth posting in case anyone else ever googles the same error.