简体中文
EnglishWebsite review
This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.
What is BulletProof FTP Server?
BulletProof FTP Server is a Windows-based file transfer server from BulletProof Software that supports three protocols: SFTP (FTP over SSH), FTPS (FTP over TLS/SSL), and classic FTP (RFC 959). It is aimed at administrators who need to run a file-sharing or distribution endpoint on Windows desktop or server editions and want protocol choice, user control, and monitoring in one graphical application.
What it does
- Multi-protocol access: The same server can accept SFTP, FTPS, and legacy FTP connections, so you can offer encrypted transfers to modern clients while still supporting older tools that only speak plain FTP.
- User and access control: Per-user settings cover disk-space quotas, IP/domain/user restrictions, connection throttling, bandwidth throttling and traffic shaping, and IP auto-banning.
- File layout and sharing: Virtual directories let you map FTP paths to UNC shares, and the product supports ad hoc file sharing via private peer-to-peer connections.
- Operations and visibility: Runtime activity, traffic statistics, event automation, email notifications, and Windows system-service support are included for unattended operation.
- Network friendliness: Passive-mode (PASV) support and NAT/firewall guidance are provided, which matters when clients sit behind routers.
Who it suits
A small business that needs to exchange files with customers, or an IT administrator replacing an ageing FTP setup, is the clearest fit: the graphical interface reduces the learning curve compared with hand-editing configuration files, and the protocol mix avoids forcing every client onto one transfer method. Organisations with strict security policies should note that classic FTP remains available and can be disabled or restricted if you only want encrypted sessions.
How it compares conceptually
| Approach | Strength | Trade-off |
|---|---|---|
| Dedicated Windows FTP/SFTP server (this product) | Focused GUI, quotas, throttling, passive-mode help | Windows-only; you manage the host |
| Built-in OS file sharing | No extra software | Not FTP/SFTP; limited external reach |
| Cloud file-transfer services | No server to maintain | Ongoing cost, data leaves your network |
Practical next step
Before committing, list the clients that must connect and which protocols they support, then confirm your Windows edition (desktop or server) and whether you need the server to run as a Windows service. The vendor provides a free demo, so test SFTP and FTPS logins from outside your network, verify passive-mode transfers through your firewall, and check quota and throttling behaviour with a non-administrative test account. BulletProof Software also publishes related tools such as BulletProof FTP Server and its client companion, which can simplify testing.
How do I set up BulletProof FTP Server on Windows?
BulletProof FTP Server installs as a native Windows application and is configured almost entirely through its graphical interface, so setup means installing the program, creating at least one user account, pointing that account at a folder, and then opening the right port on your network. The product's page lists SFTP (FTP over SSH), FTPS (FTP over TLS/SSL) and classic RFC 959 FTP as supported protocols, plus virtual directories, quota and bandwidth controls, IP auto-banning and Windows system-service mode.
Typical setup sequence
- Install and launch. Download the Windows build from BulletProof FTP Server and run the installer. The listed compatibility covers desktop Windows 11/10/8/7/Vista/XP and Server 2022/2019/2016/2012/2008/2003 in both 32-bit and 64-bit editions, so check your OS against that list first.
- Decide the protocol before anything else. Use SFTP or FTPS for anything crossing the public internet; plain FTP sends credentials and data unencrypted. This is general security practice, and the product supports all three.
- Create a user account. Set a username, password and home directory. This is where you map a real folder — or a UNC network share via a virtual directory — to what that person sees.
- Set permissions per user. Enable upload, download, delete, rename and directory creation only as needed. The product's user-control features include IP/domain/user restrictions and disk-space quotas, which are worth configuring at this stage rather than after something goes wrong.
- Choose a port and passive range. Classic FTP uses port 21; SFTP normally rides on port 22. For passive-mode connections you also need a defined range of data ports forwarded through your router or firewall — the product documents NAT/firewall handling with PASV.
- Run it as a Windows service. System-service support lets the server start without anyone logged in, which is what you want for an unattended file drop.
- Test from outside your own network. Connect from a phone on cellular data, not from the same LAN, so you actually exercise the firewall and passive-port rules.
Choosing between the three protocols
| Protocol | Encryption | Best for | Trade-off |
|---|---|---|---|
| SFTP (FTP over SSH) | Yes, via SSH | External partners, automated transfers | Not the same protocol as FTP; some old clients won't connect |
| FTPS (FTP over TLS/SSL) | Yes, via TLS | Clients that only speak FTP but need encryption | Certificate setup and firewall handling are fussier |
| Classic FTP | None | Isolated lab or LAN testing | Credentials and files travel in the clear |
A concrete scenario
A small accounting firm needs clients to drop tax documents onto a Windows Server 2019 machine. The admin installs the server, creates one account per client with a home folder on a mapped drive, enables upload but disables delete and directory listing outside that folder, sets a quota so a runaway upload can't fill the disk, and enables email notification so the office knows when files arrive. Clients connect over SFTP with a client like FileZilla or WinSCP. If a client's IP is being hammered by failed logins, IP auto-banning cuts that off without manual intervention.
Where people usually get stuck
Passive-mode port ranges are the single most common failure: the control connection succeeds, then the directory listing hangs. If you see that, the data-port range isn't forwarded. Second most common is running the server interactively and then logging off, which kills it — service mode avoids this. Third is testing only from inside the LAN, which hides every firewall problem until a real user hits it.
Start by installing, creating one test account on a local folder, and connecting over SFTP from another machine on your network. Once that works, add the external firewall rules and the passive range, then test from outside.
What is the difference between SFTP, FTPS, and classic FTP in BulletProof FTP Server?
BulletProof FTP Server supports three separate file-transfer protocols from one Windows application: SFTP, FTPS, and classic FTP. They differ mainly in how the connection is secured and which clients can connect.
The three protocols at a glance
| Protocol | How it works | Security | Typical use |
|---|---|---|---|
| SFTP | FTP over SSH | Encrypted tunnel via SSH | Secure transfers with modern clients, especially where SSH is already used |
| FTPS | FTP over TLS/SSL | Encrypted with TLS/SSL certificates | Secure transfers that keep the traditional FTP command model |
| Classic FTP | Standard RFC 959 FTP | Unencrypted | Legacy systems, internal networks, or clients that only speak plain FTP |
What this means in practice
SFTP and FTPS both protect credentials and file contents in transit, but they are not interchangeable. SFTP runs over SSH and is often chosen when firewall rules or existing SSH infrastructure favor a single secure port. FTPS wraps standard FTP in TLS and is often chosen when an existing FTP workflow or client needs encryption without switching to SSH.
Classic FTP sends data and login details without encryption. It remains useful for compatibility with older devices and controlled networks, but it should not be used across the open internet for sensitive files.
BulletProof FTP Server's page also lists controls that apply across all three modes, including user quotas, bandwidth throttling, IP/domain restrictions, IP auto-banning, and virtual directories for UNC shares. Those features govern who can connect and what they can do, regardless of which protocol you enable.
How to choose
- Use SFTP if your users or automated systems already rely on SSH keys or SSH tooling.
- Use FTPS if you need TLS encryption but must keep traditional FTP clients and workflows.
- Use classic FTP only where encryption is not required or where a device cannot support SFTP or FTPS.
- You can enable more than one protocol and assign access per user, so a single server can serve mixed client populations.
A practical next step is to list the clients and scripts that will connect, note which secure protocol each one supports, and then map those to the server's user and permission settings rather than standardizing on one protocol for everyone.
How does BulletProof FTP Server handle user access control and disk space quotas?
BulletProof FTP Server handles access control and disk quotas through per-user settings configured in its graphical interface, not through a separate external directory service. According to the product's own feature list, administrators get "user-control with diskspace quota," plus IP/domain/user restrictions, connection throttling, and bandwidth throttling or traffic shaping. In practice that means each account can be limited on who may connect, how many simultaneous connections are allowed, how much bandwidth it can consume, and how much storage it can occupy.
Access control in practice
- Identity and location limits: IP, domain, and username restrictions let you allow or deny connections based on where a request originates, which is useful for locking an account to an office range or a partner's known addresses.
- Connection and bandwidth limits: Connection throttling caps concurrent sessions, while bandwidth throttling and traffic shaping control throughput per user or session.
- Abuse handling: IP auto-banning blocks repeat offenders automatically, and monitoring of server activity and traffic gives you the evidence to tune rules.
- File placement control: Virtual directories let you map UNC shares into the server's namespace, so a user sees a chosen folder tree rather than the real disk layout. This is how you keep different customers or departments from browsing into each other's storage.
- Account lifecycle: Event support and automation, plus email notification, are the hooks for acting when something happens — a quota warning, a failed login burst, or a completed upload.
Disk space quotas
Quotas are set per user, which is the natural fit for the product's stated B2B and "allow customers to upload files" use cases: a client account can be given a fixed ceiling and no visibility into anything else. Quota enforcement is most useful when combined with connection limits, because an upload-heavy account can otherwise saturate both storage and bandwidth at once. For ad hoc sharing outside the permanent account structure, the private P2P file-sharing feature offers a lighter alternative to creating a full quota-limited user.
Choosing between the protocols
The server supports classic FTP (RFC 959), FTPS (FTP over TLS/SSL), and SFTP (FTP over SSH). The protocol choice interacts with access control, because credentials and restrictions are enforced differently depending on how clients connect.
| Protocol | Transport security | Typical use |
|---|---|---|
| FTP | None | Legacy clients, trusted internal networks |
| FTPS | TLS/SSL | Business partners needing encrypted transfers with certificate-based trust |
| SFTP | SSH | Customers and admins already standardized on SSH keys and tooling |
A practical next step
Sketch your account model before installing: list each user or group, the folder tree they should see, the maximum disk space, the maximum concurrent connections, and the allowed source IP ranges. Then test one restrictive account — a customer upload folder with a small quota and a single allowed IP range — and confirm the quota triggers an email notification. That single test exercises access control, virtual directories, quotas, and automation together, which is faster than validating each setting in isolation.
For broader context on server options, FileZilla publishes a well-known FTP server, and vsftpd is a long-standing Unix alternative; both are worth comparing if you are not committed to a Windows-only deployment.
Can BulletProof FTP Server work behind a firewall or router using passive mode?
Yes. BulletProof FTP Server supports passive-mode operation and includes NAT/firewall handling, so it can serve FTP, FTPS and SFTP clients from a machine behind a router or firewall. The page lists “NAT/Firewall with PASV (passive-mode)” among its features, which is the relevant capability for home and small-office networks.
What passive mode means here
Classic FTP uses two connections: a control connection for commands and a separate data connection for directory listings and file transfers. In passive mode, the server tells the client which port to open the data connection to. That is friendlier to client-side firewalls, but it means the server must advertise an address and port range that outside clients can actually reach.
What you still need to configure
- Port forwarding on the router: forward the FTP control port and the passive data port range to the server machine.
- A reachable external address: if the server is behind NAT, it needs to advertise the router's public IP or hostname rather than its private LAN address, otherwise clients will try to connect to an unreachable address.
- Firewall rules: allow inbound traffic on the control port and the passive range through Windows Firewall and any network firewall.
- Correct passive settings in the server: the passive port range and external IP settings must match what the router forwards.
The product's NAT/firewall feature is meant to reduce this manual work, but it cannot override a router that has no forwarding rule or an ISP that blocks the ports.
Practical scenario
A small business running the server on a Windows machine behind an office router would forward the control port plus a defined passive range, set the server's external address to the office's public IP, and then test with an external client. If transfers connect but hang after login, the passive range or external address is usually the culprit. If the client never connects at all, the control port forwarding is the first thing to check.
Choosing between FTP, FTPS and SFTP
| Mode | Encryption | Typical use |
|---|---|---|
| FTP | None | Legacy or trusted internal networks only |
| FTPS | TLS/SSL | File transfer where TLS is required but FTP tooling is familiar |
| SFTP | SSH | Secure transfers, especially over untrusted networks |
For anything crossing the public internet, prefer FTPS or SFTP; classic FTP sends credentials and data in the clear. The server supports all three, so the choice is mainly about client compatibility and security policy.
Next step
Write down the control port, the passive port range and the public IP or hostname, then verify each one against the router's forwarding table and the server's passive-mode settings. A quick external test from a different network will confirm whether the configuration is actually reachable. If you need a client to test with, the vendor also offers BPFTP Client alongside the server.
How do I purchase or upgrade a license for BulletProof FTP Server?
BulletProof FTP Server is sold and licensed directly by its publisher, BulletProof Software, through the product's own site rather than through a general app store. The page provides a Buy Now entry and a Free Demo download, and it explicitly lists "Upgrade from ANY older version" as a feature, so both new purchases and upgrades are handled through the same vendor channel.
What the page tells you
- Buy Now and Purchase Info links sit alongside the demo download and the End-User License Agreement (EULA) on the product page.
- The current build shown is version 2019.0 for Windows, with 32-bit and 64-bit support.
- Compatibility covers Windows desktop 11/10/8/7/Vista/XP and Windows Server 2022/2019/2016/2012/2008/2003.
- Upgrade eligibility is stated broadly: "Upgrade from ANY older version."
- Support routes listed include Members, Support, and Tech Support, plus a Changelog for version history.
Practical steps
- Download and test the Free Demo first if you are unsure about protocol needs (SFTP, FTPS, or classic FTP) or about features such as virtual directories, quotas, and bandwidth throttling.
- Open Purchase Info to see the current licensing terms, then use Buy Now to complete the order.
- For an upgrade, have your existing license or registration details ready and use the same Buy Now/upgrade path; the "any older version" wording suggests you do not need to be on a recent release.
- Keep the EULA and your purchase confirmation with your records, since licensing terms are governed there.
- After purchase, use Members or Tech Support for registration help and the Changelog to confirm you are running the version you paid for.
New license vs. upgrade
| Situation | Where to go | What matters |
|---|---|---|
| First-time purchase | Buy Now / Purchase Info | Choose the license that matches your user count and deployment |
| Running an older release | Buy Now upgrade path | Have prior license details; "any older version" qualifies |
| Evaluating features | Free Demo | Test SFTP, FTPS, FTP, quotas, throttling, NAT/PASV before paying |
| Post-purchase help | Members / Tech Support | Registration, activation, and configuration questions |
A realistic scenario
A small business running an aging FTP setup on Windows Server wants encrypted transfers for customer uploads. They install the demo, confirm SFTP and FTPS work with their clients, check that passive-mode NAT settings suit their firewall, then buy a license and later upgrade an older seat rather than starting fresh. The trade-off is straightforward: you get one vendor relationship covering demo, purchase, upgrade, and support, but you depend on that vendor's release cadence and Windows-only platform.
Decision criterion
Buy a new license if you have no existing registration; choose the upgrade route if you already hold any earlier version. If you are still comparing options, the demo and the EULA are the two pages worth reading before you pay. Related tools from the same publisher, such as the BPFTP client, are listed on the same site if you need matching client software.
User reviews (0)