Xerox “079-102” — Scan to SMB NTLMv2/auth error (Windows/NAS)
Joe B.
Expert ★★★★★ 27,853 satisfied customers
Specialities: SMB/NTLM, Xerox VersaLink/AltaLink/WorkCentre, Windows Server, Synology/QNAP NAS, Scan to Folder
Xerox 079-102 SMB authentication failure — NTLMv2 required, SMB2/SMB3, share & NTFS permissions, port 445
Technician
• Model (VersaLink/AltaLink/WorkCentre) and firmware up to date?
• Scanning to Windows 10/11, Server 2019/2022, or a NAS (Synology/QNAP)?
• Destination path format:
\\HOST\Share\Subfolder or \\IP\Share?• Username format tried:
HOST\user, DOMAIN\user, or user@domain.local?• Any recent hardening (disable SMB1, force NTLMv2, SMB signing) or password change?
• Can you ping the host and is TCP 445 open through the firewall?
\\KITCHENPC\Scan. I used my Windows account but it still fails.
Technician
• Host now requires NTLMv2 and the device is offering older NTLM/LANMAN.
• Wrong username format (needs
HOST\user or user@domain).• Password out of sync, or share/NTFS permissions not allowing the device account.
• SMB dialect mismatch — host allows only SMB2/SMB3, but the path or settings are incorrect.
Plan: set the right NTLM level on the PC, verify SMB2/3, correct credentials format, then test with \\IP\Share to dodge DNS.
Technician
1) Press Win+R →
secpol.msc → Local Policies → Security Options.2) Set Network security: LAN Manager authentication level = “Send NTLMv2 response only. Refuse LM & NTLM”.
3) Ensure SMB1 is disabled and SMB2/SMB3 enabled on the host.
4) In Windows Defender Firewall → allow File and Printer Sharing (TCP 445 on Private profile).
5) Prefer
\\PC-IP\Share first to bypass DNS/NetBIOS. We can switch back to hostname later.
Technician
• Create a local user on the PC, e.g.
scanner-x with a non-expiring password.• Share
C:\Scan: in Share Permissions give scanner-x = Change; in NTFS Security add Modify.• In the Xerox template:
— Host: PC’s IPv4 (e.g., 192.168.1.50).
— Share:
Scan (just the share name).— Path: optional subfolder (or blank).
— Login Name:
KITCHENPC\scanner-x (or scanner-x@kitchenpc).— Password: the local password.
This avoids domain/Kerberos confusion and matches NTLMv2 policy cleanly.
Technician
• Clock skew — make sure the Xerox time/NTP matches Windows (±2–3 min).
• SMB signing/encryption policy — if Group Policy enforces “Require signing”, older firmware may choke.
On the device: set correct Date/Time & NTP, then retry. If still failing, we’ll update firmware and confirm the SMB client supports signing with SMB2/SMB3.
Technician
1) On Windows: open Computer Management → Local Users → confirm scanner-x isn’t forced to change password at next logon.
2) In Advanced Sharing, verify the Scan share has Change for scanner-x; in Security the folder has Modify for that user.
3) Re-enter the password in the Xerox address book template (typos are common). Save & test again.
4) If the PC is AzureAD-joined, prefer a local user for SMB scanning instead of AAD accounts.
Technician
Hardening checklist to keep 079-102 away:
• Keep SMB1 disabled, ensure SMB2/SMB3 active.
• Enforce NTLMv2 on Windows; Xerox firmware should handle it.
• Use a dedicated local account for Scan to Folder.
• Open only TCP 445 on Private network and block Guest access.
• Sync clocks with NTP on both device and host.
Technician
• Enable SMB2/SMB3 and set Minimum SMB = SMB2.
• Authentication = NTLMv2 only (guest/anonymous off).
• Create a user like
scanner-x with Read/Write on the shared folder; avoid admin accounts.• In the Xerox template, use
\\NAS-IP\Share and the NAS username (no domain).• Some NAS enforce SMB signing — update Xerox firmware if you see intermittent 079-102 after a NAS upgrade.
Technician
• Keep device firmware current (SMB client fixes land often).
• Use the Xerox Address Book template → set Login Name and Folder once, then lock it.
• If you harden further (require SMB signing, change NTLM), test scanning immediately to catch policy drift.
Summary: 079-102 = SMB auth failure. Use SMB2/SMB3, enforce NTLMv2, correct username format, proper share/NTFS permissions, synced time, and firewall for port 445. Want me to remote-check your GPO and device templates? Open the chat.
Quick answer: the accepted fix
Accepted fix for Xerox 079-102 (Scan to SMB): enforce NTLMv2 on the host, keep SMB2/SMB3 enabled (SMB1 off), use a dedicated local account with Modify rights on the share and NTFS, enter credentials as HOST\user, point the template to \\IP\Share first, sync device & host time, and allow TCP 445 on the firewall.
Why 079-102 appears — NTLM policy, SMB dialects, and credential format
Windows hardening (disabling SMB1, requiring NTLMv2, or enforcing SMB signing) is good security, but older MFP defaults can’t authenticate if the username format is wrong or the SMB dialect negotiation fails. Xerox devices speak SMB2/SMB3 on current firmware, so aligning the LAN Manager authentication level, using HOST\user or user@domain, and granting correct share + NTFS permissions eliminates the 079-102 authentication error.
How to verify Scan to Folder after NTLMv2 & SMB changes
• From the device, run Template → Edit → Test with \\IP\Share and your dedicated account.
• Confirm the file lands and inherits Modify permissions.
• Switch to \\HOST\Share and repeat — if it fails, fix DNS or add a host entry.
• On Windows Event Viewer → Security, look for NTLM logon success (Audit Success) from the printer’s IP; failures indicate policy/credential mismatch.
Xerox SMB 079-102 — quick troubleshooting tips
Most cases are NTLMv2 policy + credentials format + folder rights.
Quick path: disable SMB1 (keep SMB2/SMB3), set Windows LAN Manager policy to NTLMv2 only, create a dedicated local scanner account, grant Change/Modify on share/NTFS, sync times via NTP, and enter credentials as HOST\user. Test with \\IP\Share first; once stable, switch to hostname. Update Xerox firmware if your environment requires SMB signing.
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
What exactly is Xerox 079-102 on Scan to SMB?
079-102 indicates an authentication failure to the SMB server. Typical triggers: Windows requires NTLMv2, wrong username format, expired password, missing share/NTFS rights, SMB signing policy the device firmware can’t meet, or clock skew.
Which username format should I use for Scan to Folder?
For a local PC share, use HOST\user (e.g., KITCHENPC\scanner-x). For domain-joined PCs, use DOMAIN\user or user@domain.local. Avoid Guest/anonymous — modern Windows blocks it by default.
Do I need SMB1 enabled for older Xerox models?
No — keep SMB1 disabled for security. Update device firmware and use SMB2/SMB3. If scanning fails after hardening, align LAN Manager authentication level to NTLMv2 and verify firewall/permissions rather than turning SMB1 back on.
Sources
- Microsoft Learn — Detect/enable/disable SMBv1/v2/v3
- Microsoft — Network security: LAN Manager authentication level (NTLMv2)
- Xerox Support — How to Configure Scan to SMB
Filed under: Network security / VPN / office policies (advanced)
Related articles
- Ricoh SMB scan works but print fails — AES signing mismatch
- Your Synology SMB Scan Keeps Failing — Stop the Silence and Find the Real Cause
- Windows print over SMB with 802.1X — machine auth vs user auth setup
- Printer won’t print prescriptions or medical reports — it’s urgent and nothing comes out
- Chrome managed profile watermark prints wrong — policy override checks you can do safely
- Ricoh “Hold Print” enabled by AD — disable policy
- Android VPN blocks printer discovery — split tunnel rule (work profile)
- Android “Secure print only” — enterprise toggle: setup, policy, fixes