A printer that stopped scanning after a Windows Server migration may look like an SMB compatibility problem. It may also have the wrong destination, credentials, DNS record or permissions. Work through those separately before changing the server’s protocol configuration.
Updated November 3, 2026. The earlier version led with enabling SMBv1 and treated Windows Network Discovery as a prerequisite. This revision replaces those defaults with checks that identify what the printer actually needs.
1. Verify the destination and identity
- Record the printer model, firmware version and the SMB versions it supports. Check with the manufacturer or service provider if firmware is not publicly available.
- Check the address-book entry: server name, share name, optional subfolder, username format and password. A share name and its local disk path are different things.
- Confirm that the printer resolves the destination name to the expected server. Recheck cached settings or restart the printer after correcting DNS.
- Use a dedicated scanning identity with the share and NTFS permissions required for that destination. A successful test under an administrator’s own account does not test the printer’s credentials.
From a machine on the printer’s network, these PowerShell commands help test the path:
Resolve-DnsName 'fileserver.example.com'
Test-NetConnection 'fileserver.example.com' -Port 445
They test from that machine, not from the printer. If it works on the workstation and fails on the printer, inspect the printer’s VLAN, DNS, access rules and logs too. An IP-address test can help isolate DNS, but changing the destination to an IP may also change authentication behavior; it is not a universal final configuration.
2. Check the SMB negotiation and server-side evidence
# Run on the destination Windows Server; inspection only.
Get-SmbServerConfiguration |
Select-Object EnableSMB1Protocol, EnableSMB2Protocol, RequireSecuritySignature
Get-SmbSession |
Select-Object ClientComputerName, ClientUserName, Dialect
A failed connection might never create a session. Use the printer’s exact error and timestamp with the Windows SMB and authentication event logs. Determine whether it failed to reach TCP 445, negotiate a dialect, authenticate, or write into the target folder. Those failures require different fixes.
Where the evidence points to a signing or authentication mismatch, check the requirements for that Windows release and printer firmware. Do not turn off signing or enable guest access simply because the scan failed.
3. Prefer a supported SMB version
Ask for firmware that supports SMB2/SMB3, use a supported alternative scanning destination, or replace a device that cannot meet the environment’s requirements. Microsoft’s SMBv1 guidance strongly recommends against reinstalling the protocol because of its known security weaknesses.
Some older devices really are limited to SMB1. That is a compatibility constraint to document, not evidence that the main file server should accept it. Any temporary legacy bridge needs a defined owner, restricted reachability, a limited destination and a removal plan. Do not use a domain controller as the default workaround for an obsolete scanner.
4. Separate scanning from network browsing
A manually configured scan destination does not require the server to appear in Explorer’s Network view. UDP 137 name discovery, Windows discovery services and SMB file access are related in some older workflows, but they are not the same test.
The previous recipe changed DNS Client, Function Discovery, SSDP and UPnP startup settings together. That does not establish why a printer cannot write to a known share. If Network Discovery itself is the problem, inspect its service dependencies, network profile, firewall and applied policies separately. Avoid changing several services just to keep the discovery toggle enabled.
Validate with the printer
Send a scan from the device to the exact production folder. Confirm the file opens, has the expected content and permissions, and can be created repeatedly after a restart. Record the working printer firmware and server configuration so the next migration has an actual reference.
Validation for this revision: Documentation review and command syntax review. No printer or Windows Server configuration was changed during this refresh.