If a device requires FTP, set up explicit FTPS in Internet Information Services (IIS) so sign-in and file transfers use TLS. This walkthrough is for a private network with an administrator, a trusted server certificate and Windows with the IIS FTP feature available. Standard Windows 10 Home and Pro support has ended. For a new server, choose a Windows edition still supported for your environment.
Choose the protocol before opening a port
FTPS is FTP protected with TLS. SFTP is a different protocol that uses SSH. Check which one the device or application supports. If it asks for SFTP, use Microsoft’s OpenSSH Server instructions rather than configuring IIS FTP. Plain FTP sends credentials without encryption. A client that only offers plain FTP cannot use this FTPS configuration. If all you need is to open an existing shared folder from another Windows PC, map that network share in File Explorer instead.
Create a restricted FTPS site
- Prepare a folder containing only the files to be shared and a dedicated nonadministrator Windows account for the client. Give that account the needed Windows folder permissions. Start with read access unless uploads are required. Have a TLS certificate installed on the server whose name matches the DNS name clients will enter and whose issuer those clients trust.
- On Windows 10, open Turn Windows features on or off. Under Internet Information Services, enable FTP Server > FTP Service and Web Management Tools > IIS Management Console. Apply the changes. If those features are unavailable or managed by your organization, check the Windows edition or contact the administrator.
- Open IIS Manager. Right-click Sites, choose Add FTP Site, enter a site name and select the dedicated folder. Bind to the intended private server IP and use port 21 for explicit FTPS. Select the server certificate and Require SSL.
- Enable Basic authentication for the intended Windows account and leave anonymous access disabled. In authorization choose Specified users, enter the account and grant Read. Add Write only if the workflow requires it and the Windows folder permissions match. Check the site’s FTP SSL Settings so both control and data channels require encryption. See Microsoft’s FTPS encryption settings.
Connect and verify an actual transfer
Use an FTPS-capable client on the private network. Select FTP with explicit TLS, enter the server’s certificate hostname and port 21, and sign in with the designated account. Verify the certificate without accepting a name mismatch or an untrusted certificate. List the directory and download one harmless test file. For read-only accounts, uploads should be refused. Clients find the server more reliably when it keeps one address, so consider a router reservation or a manual IPv4 address on the server PC.
If login succeeds but listing or transfer stalls, FTP uses a separate data connection. On the server, identify the listening TCP port and its process before changing firewall rules. Configure a limited passive port range in IIS’s server-level FTP Firewall Support, and have the administrator allow the control port and that range only from the intended clients on the private network. Keep the firewall enabled. This local procedure does not require a public router port forward. See Microsoft’s passive FTP port guidance and WinSCP’s illustrated IIS FTPS setup. To retire the service, stop the site in IIS and remove its dedicated inbound rules.
Tim Williams runs Everything Tech, where he writes and reviews plain-English guides for Windows, Office and web browsers, checking each one against the software maker’s own documentation. He has 12 years of experience in IT support and five years of experience writing online tutorials.