Our MFP still scans to FTP, is that still acceptable?
Plain FTP is unencrypted and shouldn't be in a corporate network anymore. Replace with SMB (to file server), SFTP, or cloud (SharePoint, OneDrive). If the FTP server is reachable over internet, this is urgent.
Try this first
- 1Inventory where the FTP scans go. Own internal server? External partner? Cloud host? The replacement depends on it.
- 2For internal flow: convert to SMB on a file server or NAS, or scan-to-SharePoint if you use M365. Covered earlier in scan-to-NAS / scan-to-SharePoint.
- 3For an external partner that only accepts FTP: insist on SFTP or FTPS, no plain FTP. Otherwise client documents travel cleartext.
- 4Remove the FTP scan destination once the new flow works. Not later, otherwise someone keeps using it.
- 5Close FTP port (21) on the firewall once everything is migrated. Even internal FTP is a latent risk.
When to bring us in
For audit-strict sectors (healthcare, finance, legal) FTP-to-external is genuinely a checklist risk. We do the migration including communication to the external party.
See also
- Printer suddenly not foundFor everyone at once: print server or network. For one person: local Windows driver or expired authorisation.
- Print job stuck in queue, nothing happensA stuck queue blocks all subsequent prints. Cleaning takes two minutes.
- Scanner no longer sends emails (scan-to-email)Almost always: the account the scanner uses had its password expire, or the mail provider blocks old protocols.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.