In announcing the release of the 15th Anniversary Edition of Acronis True Image 2019, the company revealed that its artificial intelligence-based anti-ransomware technology – stopped more than 200,000 ransomware attacks on 150,000 customers last year.
Scanning from Kyocera printers to Windows 2008 R2 share.
We are migrating from Windows SBS 2008 server to a Windows SBS 2011 environment which includes a new Windows 2008 R2 server. Our Kyocera printers (TASKalfa 420i, KM-6030, and TASKalfa 4500i) used to be able to scan to an SMB share on our Windows 2008 SBS server just fine. However, when I try to scan to our new 2008 R2 file server (with the exact same share permissions and file structure) I receive a test failure on the printer and I see this error in the event log of the file server:
Event ID: 4625
An account failed to log on.
Subject:
Security ID: NULL SID
Account Name: -
AccountDomain: -
Logon ID: 0x0
LogonType 3
Account for Which Logon Failed: NULL SID
Account Name: scanuser
Account Domain: KM-NETPRINTERS
Failure Information:
Failure Reason: Unknown user name or bad password.
Status: 0xc000006d
Sub Status: 0xc0000064
If I simply switch the server IP address on the Kyocera back to the old server IP, it works perfectly fine. How can I fix this?
Thank you
Event ID: 4625
An account failed to log on.
Subject:
Security ID: NULL SID
Account Name: -
AccountDomain: -
Logon ID: 0x0
LogonType 3
Account for Which Logon Failed: NULL SID
Account Name: scanuser
Account Domain: KM-NETPRINTERS
Failure Information:
Failure Reason: Unknown user name or bad password.
Status: 0xc000006d
Sub Status: 0xc0000064
If I simply switch the server IP address on the Kyocera back to the old server IP, it works perfectly fine. How can I fix this?
Thank you
Who is Participating?
Experts Exchange Solution brought to you by
Enjoy your complimentary solution view.
Get every solution instantly with Premium.
Start your 7-day free trial.
I wear a lot of hats...
"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.
Experts Exchange Solution brought to you by
Your issues matter to us.
Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.
Start your 7-day free trial
Everyone is given the Full Control permission on the share. I also double checked the NTFS permissions and they check out as well.
Security on the 2008 server is tighter - full control for everyone may still be looking for a validated domain user. It would be best to create a scan user on your domain with limited rights and then give this user rights to the share. Make sure this user is configured with a password that never expires and define this user name and password in the Kyocera device. This should resolve your issue.
Turns out I needed to unshare the folders, re-apply all of the permissions to all child objects, and then re-share to fix this problem.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Printers and Scanners
From novice to tech pro — start learning today.
-
Microsoft ApplicationsCertification: MOS Microsoft Office Specialist - Word 2013 Part … 198 lessons
Experts Exchange Solution brought to you by
Enjoy your complimentary solution view.
Get every solution instantly with Premium.
Start your 7-day free trial.
Everyone Read or Full control?
If that is correct then take a look at your NTFS permissions. Is there an account for the kyocera in there? Does it have write or modify permissions?
If that looks ok and you can verify the permissions are you sure you have the correct path and share name of the folder?
Usually scanning to a smb share is a permissions issue.