Sharp MX-5070N Driver, Scan-to-Folder Errors, and VLAN Network Issues
The Sharp MX-5070N driver enables printing and scanning communication between the device and networked systems, including scan-to-folder workflows. When scan-to-folder suddenly fails while printing continues to work, the driver is often suspected, but in many cases the issue is tied to network segmentation, destination resolution, or SMB compatibility rather than a driver fault.
This page provides Sharp MX-5070N driver context together with troubleshooting notes describing situations where scan-to-folder fails after VLAN changes, destinations cannot be resolved, or SMB protocol differences affect scan delivery.
Problem: Sharp MX-5070N scan-to-folder fails with “Selected Servers not found” after VLAN change
What users observed: After workstations were moved to a new VLAN while the copier remained on the original network, scan-to-folder stopped working for most users and displayed “Selected Servers not found.” Printing continued to function normally, and users could still send print jobs to the device. In some cases, one workstation that had been moved earlier continued to receive scans while others could not.
What was tried: Users restarted the copier, adjusted UNC paths to use IP addresses instead of hostnames, and reviewed SMB configuration including SMBv1 compatibility on destination systems.
How this played out: The issue remained limited to scan-to-folder while printing worked without interruption. Switching from hostname to IP did not restore functionality, and the behavior pointed to destination resolution and SMB negotiation across VLAN boundaries rather than a driver or general network connectivity issue.
Problem: Sharp MX-5070N scan-to-folder unreliable across VLANs and subnets
What users observed: Scanning to individual workstation shares became inconsistent or failed entirely when devices and users were separated across VLANs, even though normal printer access and printing remained functional.
What was tried: Users continued attempting direct scan-to-workstation configurations, expecting the issue to be related to connectivity or driver setup.
How this played out: A more stable approach involved creating a central network share accessible by both the copier and all users. Scanning to this shared location, with separate user folders, allowed scan workflows to continue without relying on individual workstation accessibility across VLAN boundaries.
Problem: Sharp MX-5070N scan-to-folder affected by SMB protocol differences
What users observed: Scan-to-folder success varied depending on the SMB version supported by the copier and the destination system. In some cases, disabling SMBv1 on a workstation caused scanning to that system to fail.
What was tried: Users reviewed SMB settings, considered firmware updates, and tested different SMB configurations on destination systems.
How this played out: The behavior aligned with SMB protocol compatibility rather than driver issues. Some Sharp devices relied on SMBv1, while newer models supported SMBv2 or SMBv3. Where protocol expectations did not match between the copier and destination system, scan-to-folder failed. The outcome depended on aligning SMB support or using a shared destination that maintained compatibility.
Across Sharp MX-5070N troubleshooting reports, the recurring pattern is that scan-to-folder failures after network changes are caused by VLAN segmentation, destination resolution limits, and SMB protocol mismatches rather than driver faults. Printing typically remains unaffected because it uses different communication paths, while scan workflows depend on network accessibility and protocol compatibility that must be aligned across environments.
Other devices showing similar behavior:
- Scans your system for missing or outdated drivers
- Downloads and installs the correct versions
- Creates a restore point before making changes