Printer troubleshooting technician providing live chat help

Joe B.

Reviewed for technical accuracy

Specialities: Windows & macOS, Printers/MFPs, SMBv2/v3, Active Directory, NAS (Synology/QNAP), Security Baselines

Repair scan-to-folder after SMB hardening — SMB signing required, NTLMv1 disabled, guest access removed, minimum SMB set to v2/v3

Technician avatar Technician
Hey! We’ll troubleshoot why scan-to-network folder suddenly fails after SMB hardening. Which MFP brand/model (Ricoh/Konica/Canon/Kyocera/Sharp/HP)? Does the target path look like \\SERVER\Scans or a NAS (Synology/QNAP/TrueNAS)? Any errors on the panel such as “Authentication failed”, “SMB protocol error”, or “Cannot connect to server 445”? Did you recently enforce SMB signing, disable NTLMv1, or raise “LAN Manager auth level”?
Customer
We hardened Windows Server 2019 using the security baseline. Since then the MFPs can’t scan to \\filesrv\dept-scans. Panel shows “SMB authentication error”. Workstations can still browse the share. We also turned off guest access and removed SMB1.
Technician avatar Technician
Got it. Hardening often enforces SMBv2/SMBv3 only, SMB signing required, and NTLMv2 or Kerberos. Older MFPs send NTLMv1, anonymous/guest, or lack signing — the server then rejects the session. Plan:
1) Verify the device supports SMBv2/3 with signing (update firmware if available).
2) Use a dedicated service account (no guest), confirm share + NTFS permissions.
3) Ensure correct DNS, time sync, and that port 445 is reachable (no firewall block).
4) If the model can’t sign, switch the scan destination to a NAS that allows per-share policies or use SMB proxy/scan app alternative (FTP/SMTP with OAuth if compliant).
Customer
The devices are Konica C368 and a couple of older Ricohs. We used a generic “scanuser” local account. After baseline, logs show “The server requires signing”. Where do we enable SMB signing on the MFP?
Technician avatar Technician
Step 1 — Turn on SMBv2/SMBv3 and signing on the MFP
• Konica Minolta: Administrator → Network → SMB Settings → set SMB Client: v2/v3 and enable SMB Signing; enter the server via FQDN (ensures Kerberos/NTLMv2).
• Ricoh: Interface Settings → SMB → set SMB (Client): 2.0/3.0, enable Signing. Update to the latest firmware to add SMBv3.
• Re-save the destination with \\filesrv.domain.local\dept-scans and credentials of the scan service account.
Customer
We changed to SMBv3 with signing. Now the error is “Authentication failed”. The account works on a PC. Could NTFS permissions or “Account is sensitive and cannot be delegated” affect it?
Technician avatar Technician
Step 2 — Use a proper service account + correct ACLs
• Create DOMAIN\svc_scan (password never expires, cannot change password). Do not mark “sensitive & cannot be delegated”.
• Share permissions: svc_scan = Change (or Modify).
• NTFS: grant Modify on the Scans folder.
• In the address book, set Username as DOMAIN\svc_scan; if using a NAS local user, use nasname\svc_scan.
• Test from a PC with: cmd /c net use \\filesrv\dept-scans /user:DOMAIN\svc_scan <password>. If this fails, fix ACLs or account first.
Customer
The net use test works. But the Ricoh still fails. We also disabled LM/NTLMv1 and set “Send NTLMv2 response only”. Time is off by 7 minutes on the copier.
Technician avatar Technician
Step 3 — Fix time/DNS & auth method
• Sync the MFP clock to your NTP source (within 5 minutes) — skew breaks Kerberos tickets.
• Use FQDN for the server and set DNS servers to the AD DNS. Avoid raw IP when Kerberos is expected.
• On older devices that can’t do Kerberos, ensure they send NTLMv2 (often called “NTLM” on panels). With NTLMv1 disabled, jobs will fail unless NTLMv2 is used.
Customer
We also tightened SMB by requiring encryption on the share. Do MFPs support SMB encryption?
Technician avatar Technician
Some newer MFPs support SMB 3.x encryption; many older ones do not. If “Encrypt data access” is forced on the share, the device must use SMB 3.x with encryption; otherwise the server denies it. Options:
• Disable “require encryption” on that one share and rely on signing + NTLMv2/Kerberos plus strong ACLs.
• Or scan to a NAS (Synology/QNAP) share that allows per-share settings while keeping server policy strict.
• Long-term: update firmware or the device to a model with full SMBv3 encryption support.
Customer
After NTP/DNS fixes the Konica works. The Ricoh still errors unless we target a Synology share. Any last things to check?
Technician avatar Technician
Yes — final compatibility checks:
• Confirm network path uses \\serverFQDN\share, not a DFS link older firmware can’t resolve.
• Ensure firewall allows TCP 445 between the MFP VLAN and the fileserver; avoid SMB over NetBIOS ports (137–139).
• On Synology/QNAP set Minimum SMB = SMB2, Maximum = SMB3, and allow NTLMv2. Create a local user matching svc_scan if not using AD.
Customer
Great — scans now land in the folder from both brands. We’d like a checklist to stay compliant after future updates.
Technician avatar Technician
Final checklist:
• Keep firmware current; set MFP SMB client = v2/v3 + signing.
• Use svc_scan with NTLMv2/Kerberos and least-privilege Modify rights.
• Ensure DNS + time (NTP) accuracy; reference FQDN paths.
• Document share/NTFS ACLs and review after security baselines or GPO changes.
• Prefer IP segmentation and allow TCP 445 explicitly between the MFP and the file target.
Customer
Perfect — scan-to-folder is back and aligned with our SMB security posture. Thanks!
Technician avatar Technician
Summary: When scan-to-network folder breaks after SMB hardening, upgrade MFP firmware and enable SMBv2/SMBv3 with signing, use a dedicated service account with correct share/NTFS rights, enforce NTLMv2/Kerberos, fix DNS/NTP, and validate TCP 445 reachability. If encryption is required and the device can’t support it, target a NAS share or replace the device. Need help mapping your exact model? Open the chat.

Quick answer: the accepted fix

Accepted fix when scan-to-folder fails after SMB hardening: enable SMBv2/v3 + signing on the MFP, use a DOMAIN service account, grant Modify on share/NTFS, reference \\serverFQDN\share, ensure NTLMv2/Kerberos with correct time/DNS, and verify port 445 connectivity. Adjust encryption policy or target a compatible NAS if needed.


Why SMB hardening breaks legacy scan-to-folder (SMB1 removal, NTLMv1 disabled, signing required)

Security baselines remove SMB1, disable guest sessions, require SMB signing, and enforce NTLMv2 or Kerberos. Many older copiers speak only SMB1/NTLMv1 or cannot sign packets, so the server rejects the session. Updating firmware, selecting SMBv2/3 in the panel, and switching to a service account usually restores compliant scan-to-network folder workflows.

How to verify secure SMB scanning works

From the MFP, browse to \\serverFQDN\share using the svc_scan credentials. Confirm the device saves a test PDF/TIFF and the file ACL inherits properly. Check the server’s Security log for Event ID 4624 with Authentication Package = NTLMv2 or Kerberos and SMB signing enabled. If failure continues, test with net use from a PC on the same VLAN and compare dialects in Get-SmbSession.

Scan-to-folder — quick troubleshooting tips

Most post-hardening failures are auth/compatibility issues: SMB1 disabled, NTLMv1 blocked, signing required.

Quick path: update firmware → set SMBv2/3 + signing → use DOMAIN\svc_scan → grant Modify → use FQDN + NTP sync → verify TCP 445 → adjust encryption or point to a NAS. This sequence fixes the majority of SMB scan issues across Ricoh, Konica, Canon, Kyocera, Sharp, and HP.

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-folder stop after we removed SMB1?

Legacy MFPs only speak SMB1/NTLMv1. After hardening, servers accept only SMBv2/SMBv3 with NTLMv2/Kerberos and often signing, so connections are refused.

Do we need guest access for scanning?

No. Create a service account with Modify rights on the share/NTFS. Guest/anonymous is typically disabled by baselines.

How do we handle SMB encryption requirements?

Use an MFP that supports SMB 3.x encryption or target a NAS share where encryption is optional. Otherwise the server will reject unencrypted clients.

What ports and names should we use?

Allow TCP 445 and reference the file server by FQDN (for Kerberos). Keep device time synced via NTP.

Common SMB scan problems and quick fixes
SymptomLikely causeQuick fix
Authentication failed Guest disabled, NTLMv1 blocked Use DOMAIN\svc_scan with NTLMv2/Kerberos
Server requires signing Device not signing SMB Enable SMB signing on MFP; update firmware
Cannot connect to server 445 Firewall/VLAN ACL Allow TCP 445 between MFP and fileserver
Works to NAS, not to Windows Share policy requires encryption Allow non-encrypted on that share or upgrade MFP to SMB3 encryption

Step-by-step (Windows Server / NAS)

  1. Upgrade MFP firmware; set client to SMBv2/SMBv3 with signing enabled.
  2. Create DOMAIN\svc_scan; grant Modify on share and NTFS; store creds in address book.
  3. Use \\serverFQDN\share; sync NTP; ensure AD DNS is configured on the MFP.
  4. Verify connectivity with net use and Get-SmbSession; open TCP 445.

Note for mixed environments (macOS/NAS)

  1. On Synology/QNAP set Min SMB = SMB2, Max = SMB3; allow NTLMv2; create a dedicated scan user.
  2. If encryption is mandatory on Windows shares, consider targeting a NAS share or upgrading the MFP for SMB3 encryption.

Sources

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