Printer troubleshooting technician providing live chat help

Joe B.

Reviewed for technical accuracy

Specialities: Windows Server/AD, SMB2/SMB3, NTLM/Kerberos, MFPs (HP/Ricoh/Canon/Brother), NAS (Synology/QNAP)

Scan to SMB keeps failing — NTLMv1 disabled, SMB1 removed, switch to SMB2/SMB3 with NTLMv2 or Kerberos, fix signing/guest access

Technician avatar Technician
Hey! We’ll stabilize your Scan to SMB. Intermittent failures right after hardening (disabling NTLMv1 or removing SMB1/CIFS) usually mean the MFP is still trying to use legacy auth. A few checks to target the fix:
• MFP brand/model & firmware? (HP/Ricoh/Canon/Brother/Konica)
• Target share type — Windows Server, NAS (Synology/QNAP), or workstation?
• On failures, do you see messages like “Login error”, “SMB protocol error”, “NTLMv1 not permitted”, or “STATUS_ACCESS_DENIED”?
• Is the scan account a domain user or local account? Any password rotation recently?
Customer
Ricoh MFP, scans to a Windows Server share. After security changes (disabled NTLMv1 & removed SMB1), scans work some days then fail with “Login error”. No changes on the share path.
Technician avatar Technician
Classic symptom of legacy negotiation. When NTLMv1 is blocked on DCs/servers and SMB1 is removed, older MFP stacks sometimes fall back between LM/NTLMv1 and modern NTLMv2. If time/clock skew or SMB signing requirements change, it gets intermittent.
Our plan: 1) Force the MFP to use SMB2/SMB3 and NTLMv2 (or Kerberos if supported). 2) Verify share ACLs and test with a least-privileged service account. 3) Align security baselines — LAN Manager authentication level, SMB signing, and guest access. 4) Update firmware and disable legacy fallbacks on the device.
Customer
Where do I set SMB2/NTLMv2 on a Ricoh? I only see “SMB” with a version dropdown and an “Authentication” selector.
Technician avatar Technician
Step 1 — Force modern protocol/auth on the MFP
• In the MFP web UI: set SMB version = SMB2/SMB3 (avoid “Auto” if it can negotiate down).
• Set Authentication = NTLMv2 (or Kerberos if the device supports AD join). Disable “LM/NTLMv1”.
• Save a scan account like DOMAIN\svc_scan with a long password and “Password never expires”.
• Update firmware — many vendors added SMB2/NTLMv2 + SMB signing fixes in later builds.
Related keywords: scan to folder fails, STATUS_LOGON_FAILURE, NTLM blocked, SMB2 only, upgrade firmware.
Customer
Server side is Windows Server 2019. NTLMv1 was disabled via policy. Anything to check on the share or domain?
Technician avatar Technician
Step 2 — Align AD policies & SMB settings
• In GPO set Network security: LAN Manager authentication level to “Send NTLMv2 responses only. Refuse LM & NTLM”. This equals LmCompatibilityLevel=5 on DCs. (Audit first to identify old clients.)
• Ensure SMB1 is removed and SMB2/SMB3 enabled on file servers. Windows 10/11 clients and modern NAS support this out of the box.
• Review SMB signing requirements (newer Windows can require signing by default). If your MFP supports signing, leave it required; if not, set signing allowed on the server share while you patch the device.
• Disable guest access for the share; require explicit credentials.
Keywords: SMB signing enforcement, NTLM hardening, Kerberos preferred.
Customer
Permissions look fine but failures are random. Any logs I can check when Scan to SMB fails?
Technician avatar Technician
Step 3 — Prove which auth/protocol is used
• On the file server: check Event Viewer → Security for 4625 (failed logons) and the Failure Information detail (NTLM vs Kerberos).
• Enable NTLM auditing in policy to detect any NTLMv1 attempts.
• On Windows file servers, review Microsoft-Windows-SMBClient/Connectivity and SMBServer/Security logs for SMB negotiation, signing, and STATUS_ACCESS_DENIED.
• If needed, a short packet capture during a failed scan will show Session Setup with NTLMv1 vs NTLMv2 and SMB dialect (2.0/3.x).
Customer
We also scan to a Synology. After changes, that share stopped too with “NTLMv1 not permitted”. Any NAS tips?
Technician avatar Technician
Step 4 — NAS hardening without breaking scans
• In NAS File Services → SMB, set Minimum protocol = SMB2, Maximum = SMB3. Keep NTLMv2 only and turn on SMB signing if your MFP supports it.
• Create a dedicated scan account with read/write on the share and NTFS/ACLs. Avoid guest. Map the path as \\NAS\Scans\%User% where supported.
• Ensure NAS time sync (NTP) with the domain to prevent NTLM/Kerberos timestamp issues.
• Update the NAS SMB package; older builds defaulted to NTLMv1/SMB1 compatibility.
Customer
After forcing SMB2/NTLMv2 on the MFP and NAS, scans mostly work. We still get occasional “Access denied”. Could SMB signing be the last piece?
Technician avatar Technician
Likely. Newer Windows builds can require SMB signing by default. If your MFP supports signing, enable it. If not, set the server/NAS to signing allowed (not required) temporarily while you upgrade firmware.
Also check:
• Clock drift < 5 minutes (DC/NAS/MFP).
• Share/NTFS: give the service account Modify on the target folder and ensure inheritance isn’t blocking subfolders.
• Avoid DFS referrals for legacy MFPs; point directly to the hosting server path.
Customer
Any best practice to avoid breakage when we fully block NTLMv1 across the domain?
Technician avatar Technician
Rollout playbook
1) Audit NTLM with Windows policy before enforcing — locate any NTLMv1 traffic from MFPs/NAS.
2) Patch device firmware; set SMB2/SMB3 + NTLMv2 (or Kerberos).
3) Harden GPO: LMCompatibilityLevel=5, remove SMB1, configure SMB signing appropriately.
4) Test with a dedicated service account, then deploy via template/clone to all MFPs.
5) Monitor Security/SMB logs for a week; only then flip enforcement to refuse LM/NTLM.
Customer
Done — with SMB2/NTLMv2 and signing aligned, scans are reliable. Anything else to keep it stable?
Technician avatar Technician
Summary: Intermittent Scan to SMB after hardening means legacy negotiation. Set the MFP to SMB2/SMB3 + NTLMv2 (or Kerberos), remove SMB1, refuse NTLMv1, align SMB signing, fix permissions, and keep firmware current. Need help mapping your exact MFP/NAS menus? Open the chat.

Quick answer: the accepted fix

Accepted fix when Scan to SMB intermittently fails after NTLMv1 is disabled: force the MFP to use SMB2/SMB3 and NTLMv2 (or Kerberos), remove outdated auto-queues, align SMB signing policy, and use a dedicated service account with proper share/NTFS permissions. Update firmware on the MFP/NAS.


Why Scan to SMB breaks after disabling NTLMv1 (SMB1 removal, signing enforcement)

When SMB1 is removed and NTLMv1 is refused by DCs, older MFP firmware may still attempt legacy LM/NTLMv1 or downgrade SMB negotiation. Newer Windows builds can also require SMB signing, which legacy devices ignore. Migrating the device to SMB2/SMB3, enforcing NTLMv2, and enabling signing (or allowing it temporarily) stabilizes scan to folder on Windows Server and NAS.

How to verify the fix (server logs & protocol)

Trigger a scan and check Windows Security 4625/4624 for NTLMv2 or Kerberos, and SMB logs for the SMB dialect (2.x/3.x) and signing status. If you still see monochrome NTLM or SMB1 in captures, the MFP hasn’t applied settings or needs a firmware update.

Scan to SMB — quick stabilization tips

Most intermittent cases are protocol/auth mismatches: NTLMv1 blocked, SMB1 removed, or signing enforced.

Quick path: MFP SMB2/3 + NTLMv2 → dedicated service account → remove SMB1 → review LAN Manager auth level and SMB signing → patch firmware/NAS SMB package → verify with server logs. This resolves the majority of scan to folder failures across HP/Ricoh/Canon/Brother.

Disclaimer: This information is AI-generated and intended for general guidance only. For advice specific to your environment, please consult a verified expert on Whizz-Tech before making decisions.


Getting Started Is Easy

Ask for help, 24/7

Members enjoy round-the-clock access to 12,000+ verified Experts, including tech support, mechanics, vets, and more.

Expert will respond in minutes

We match you with an Expert who specializes in your situation. Talk, text, or chat — whichever you prefer.

Save time & money

No scheduling hassles or expensive consults. Membership can save you significant time and money each month.

FAQ

Why did Scan to SMB start failing after hardening?

Blocking NTLMv1 and removing SMB1 breaks legacy MFP stacks. Force SMB2/3, require NTLMv2 (or Kerberos), align SMB signing, and update firmware.

Should we re-enable NTLMv1 or SMB1 temporarily?

No. Keep security posture. Instead update firmware and configure the device for SMB2/3 + NTLMv2; use a dedicated account and correct ACLs.

Do we need SMB signing?

Newer Windows may require signing. Enable signing on devices that support it; otherwise allow signing on the server short-term and schedule a device upgrade.

Kerberos vs NTLMv2 — which is better for MFPs?

Kerberos is preferred if the MFP can join the domain. If not, NTLMv2 with proper time sync and strong passwords is stable and secure.

Sources

Matt Verified Icon
Matt ● replies in < 1 min
Technician Expert
⭐⭐⭐⭐⭐ Trusted by 27,000+ customers
Avatar
Alex · Expert's Assistant