Network & Protocol Access
Files.com hosts FTP, FTPS, SFTP, and WebDAV services so applications, devices, and trading partners can exchange files using the protocols they support. A reachable service and permission to use a site are separate. Listening on a port or responding to a protocol command does not grant access to files or site administration.
Shared Services and Protocol Availability
The port reference lists the supported service ports. Port 21 being open does not mean that unencrypted transfers are allowed: Files.com requires FTP encryption by default, and plain FTP must be explicitly enabled. FTP connection profiles cover Implicit FTPS, alternate ports, and separate data connections. SFTP connection settings cover its alternate port. WebDAV uses HTTP methods for file and folder operations; recognizing those methods does not authorize their use.
On shared service addresses, disabling FTP or SFTP for one site does not close the shared ports, because other customers still need those services. The disabled protocol remains unavailable to that site's users even though the service answers connections. Site protocol settings describe shared and dedicated addresses.
For client protocol connections, an enabled protocol is another prerequisite; having a valid credential does not enable a protocol that the site has disabled. Site protocol settings and the user's protocol privileges let you keep unused connection methods unavailable.
IP and Country Restrictions
IP whitelists on client connections apply to the source address Files.com observes. An address on any applicable site, user, group, or Partner list can satisfy the whitelist; the lists do not form a series of increasingly narrow requirements. Country restrictions, when configured, are separate checks that must also pass. Files.com does not recommend adding static IP restrictions unless your organization requires them, because changing networks, proxies, and service addresses can interrupt legitimate work.
Network location is not a person's identity. Several devices can share one public address, and one device can use several addresses over time. Use the account and credential model to establish who is connecting, and use network restrictions only for the additional connection requirement they actually enforce.
Native Files.com Connections
A native Files.com Remote Server connection from another site uses the key and applicable folder permissions without applying the issuing site's IP whitelists, country lists, user or group protocol permissions, or Global Acceleration regional connection setting. Those controls therefore cannot be used to end native access. The site has a separate control for disabling use of its keys by these connections.