Scan-to-folder is not merely a printer feature. It is a small network workflow connecting the scanner, clinic network, Windows file sharing, a credential, a destination folder, and the staff who must retrieve the documents. Replacing one computer can quietly invalidate several parts of that chain.
Do not start by changing random scanner settings
First capture the current destination, protocol, port, username format, computer or server name, IP address, and error message. A known configuration—even a broken one—is easier to repair than an address-book entry that has been repeatedly edited without documentation.
Why printing still works while scanning fails
Printing has a different destination
The workstation sends print jobs to the device. Scan-to-folder reverses the direction: the device must authenticate to a computer or server and write into a shared folder.
The old path is still stored
The scanner may still target the retired computer name, old IP address, old share name, or a folder created inside the former employee’s Windows profile.
The stored credential no longer works
A password may have changed, an account may have been removed, or the replacement computer may interpret a local, Microsoft, or Entra username differently.
Windows sharing behavior changed
The new computer may use a Public network profile, different firewall rules, disabled sharing, different share permissions, or stricter authentication requirements.
Common failure points after a computer replacement
| Failure point | What may have changed | What to verify |
|---|---|---|
| Destination name | The old computer name was retired or the new device was named differently. | Resolve the hostname from another clinic computer and compare it with the scanner address-book entry. |
| IP address | A dynamic address changed after replacement or reboot. | Use a documented hostname or appropriate DHCP reservation rather than relying on an unmanaged address. |
| Share and folder path | The share name, local folder, drive letter, or user-profile path changed. | Confirm the exact UNC path and test it from another device using the intended credential. |
| Credential format | The scanner stored an obsolete username or employee password. | Verify the correct local or organizational account format and whether the device supports the required authentication method. |
| Permissions | Share permissions and NTFS permissions were not recreated together. | Confirm the scan identity can create, write, rename, and close a test file in the destination—and cannot access more than necessary. |
| Firewall and profile | The replacement computer classified the clinic network as Public or lacks the appropriate file-sharing rule. | Confirm the network profile and File and Printer Sharing rules are enabled only where intended. |
| SMB compatibility | An older device may support only obsolete SMB behavior. | Check device firmware and SMB2/SMB3 support before considering any legacy protocol. Do not treat SMB1 as a routine fix. |
A reliable troubleshooting sequence
Capture the scanner configuration
Record the device IP, destination host, share path, port, protocol, username format, file type, and exact error code or message.
Test the destination from Windows
From another clinic computer, open the same UNC path and authenticate with the intended scan identity. Confirm a test file can be written and removed.
Verify both permission layers
Check share permissions and NTFS permissions. A correct setting in only one layer is not enough.
Confirm network and firewall state
Verify the destination computer is on the intended clinic network profile and accepts SMB file-sharing traffic only from the appropriate network.
Update the scanner address book
Enter the verified host, path, username, password, and protocol once. Avoid changing several variables between tests.
Perform a real workflow test
Scan a multi-page document from the device, confirm the file arrives, opens correctly, uses the expected name, and is visible only to authorized staff.
Do not enable SMB1 just because the scanner is old
SMB1 is deprecated and is not installed by default on modern Windows. Before enabling a legacy protocol, verify whether the scanner supports SMB2 or SMB3, update its firmware, check vendor guidance, and consider scan-to-email, a secured server or NAS destination, or replacement hardware. Restoring function by weakening the whole workstation is a rotten trade.
Choose a stable credential and destination
- Avoid tying the workflow to an employee password that will change or disappear when the employee leaves.
- Use a documented clinic-controlled service identity where appropriate and limit it to the required folder.
- Do not give the scanner broad access to a user profile, desktop, entire drive, or unrestricted shared storage.
- Store the credential owner and recovery method under clinic control without placing the password in public documentation.
- Use a durable destination such as a properly managed server, NAS, or dedicated intake location when the workflow is operationally important.
Protect scanned clinical documents
- Limit destination access to the staff roles that actually process the documents.
- Separate temporary intake from long-term records storage when possible.
- Define who moves, reviews, deletes, or archives incoming files.
- Avoid a single shared folder that exposes every scanned document to every employee.
- Confirm backups and retention match the clinic’s actual workflow and obligations.
Document the repaired workflow
| Record | Minimum detail |
|---|---|
| Scanner | Make, model, device name, IP address, firmware version, and vendor contact. |
| Destination | Hostname, share name, UNC path, local folder, protocol, and port. |
| Access | Credential owner, username format, permission scope, and secure recovery location. |
| Network | Network profile, firewall rule scope, DNS or DHCP reservation, and relevant VLAN or subnet. |
| Testing | Single-page and multi-page test, file format, naming result, authorized access check, test date, and approver. |
Frequently asked questions
Why does printing still work when scan-to-folder fails?
Printing and scanning commonly use different protocols and destinations. Printing may continue through a driver or print service while scanning depends on SMB authentication, a shared folder, permissions, and firewall access.
Should a clinic enable SMB1 to make an old scanner work?
Not as a routine fix. Verify SMB2 or SMB3 support, firmware, and safer alternatives first. SMB1 is deprecated and absent by default from modern Windows installations.
Should scan-to-folder use an employee password?
Usually not when the workflow must survive password changes and staff turnover. Use a limited, documented clinic-controlled identity where appropriate.
What should be documented after repair?
Record the scanner IP, destination path, protocol, credential owner, permissions, firewall profile, test date, and approval.
Related ClinicsIT guidance
Authoritative Microsoft references
- Microsoft: SMBv1 is not installed by default
- Microsoft: File and printer sharing ports and firewall rules
- Microsoft: SMB features in Windows
Practical note: Scanner firmware, Windows security settings, SMB support, identity configuration, and privacy requirements vary. Preserve the working environment and document the current configuration before changing protocols, credentials, or access.
Need the clinic’s scanning workflow restored and documented?
ClinicsIT can trace the scanner, network, credential, folder, permissions, and document-access path; repair the practical failure; and leave the clinic with a usable workflow record.
Request a Scanner Workflow Review