How to set up smartphones and PCs. Informational portal
  • home
  • Interesting
  • How to open ftp access to your computer. Reasons why it may not work

How to open ftp access to your computer. Reasons why it may not work

Sometimes a person needs to exchange large files on the web. It is inconvenient to send such files, the size of which exceeds 10 MB, via e-mail, since not all services give the go-ahead for this, so either you have to split the file into parts or archive it to reduce the size to the required size. But what if you need to send more than one file weighing more than 100 MB? Then your FTP server will come in handy. You can make it on a remote computer and upload any files there at high speed through the client. In this article, we will look at how to create an FTP server and what the basic setup of an FTP server is.

For what cases do you need your own FTP server

There are many rogue servers on the web. They store various files, and many of these servers are a kind of storage - users download music, movies, games and other files from there. Especially often, such servers are created over a local network so that data can be exchanged without the Internet.

On the other hand, you need your own FTP server so that you can make changes on your computer from a distance.

In addition, the installation of an FTP server on the local network is a prerequisite for webmasters who want to test their site before launching it on the Internet on a computer.

You may have your own reason why you want to make an FTP server, as well as the method in which you will implement it. But this article will look at a popular way of generating "at home" - you will learn how to set up FTP using the FileZilla program.

How to make FTP server in FileZilla

FileZilla is a client-side and server-side program. You need to download the FileZilla server version on the web. It is better to do this through the official website of the developer, so as not to accidentally download the virus along with the program.

The installation process is very simple. First, open the exe file to run the installer. In the first step of the installation, you will need to agree to the license rules. In the next step, select the services that you want to install along with the FileZilla server, and also define the type of installation. It is recommended to immediately take "Standard". Then select the folder where the program will be installed. Next, an important step will follow - you need to choose how the system will install FileZilla server - as a service or a regular program, and whether this application will be launched when the system is turned on. You can also change the port for the administrator console at this step. Just do not forget to write it down somewhere so that you do not reinstall the program later.

The last step of the installation is to define the users who can use the FileZilla server program. It is better that you are the only user on the computer - then you do not have to configure access to the program manually. After that, do not press the "Install" button, and wait for the installation to finish.

Now let's take a look at how to set up FTP. You can create a server for both the local network and the Internet. At the beginning, after starting the program, a pop-up window will appear in front of you. It will need to specify the local IP address, port and password for the administrator. In fact, this data is only needed to prevent unauthorized people from entering your program from a computer. From other PCs, people will not be able to access the admin interface.

Next, you need to go to the "Edit" menu and open "Settings". In the "General" tab, you will see the basic settings for the server. You can set the port through which users will connect to the server, specify the maximum number of clients, streams and limit sessions with timeouts. Now the port matters - in order to secure your server, it is better to specify a non-standard port. But then you will need to notify users about this. If you do not plan to limit the number of clients in any way, you can leave in the “Max. number of user "value" 0 ", that is, no limit.

The advantage of creating a server using FileZilla server is that you can set all the settings using a user-friendly interface. If you were to do this somewhere in the Linux environment, then you would have to write all the configurations, which is not very convenient and difficult. For example, FileZilla can even set up a welcome message for users. To do this, you just need to go to the "Welcome message" section and write a greeting text for clients. And in a different environment, you would have to write special commands for this.

In the "IP buildings" item you can specify the IP addresses for which the server will be available. If you specify your IP address, then the server will be available only on the local network for your computer. If you want to work through a server on the Internet, it is not recommended to restrict IP addresses. If you have ill-wishers, and you know their IP-addresses, then you can register them in the "IP Filters" item, which will deny entry for the specified IP (ranges can be specified).

The main difference between setting up a server for a local network and the Internet is that in the second case you will have to somehow coordinate the configurations with the firewall and router. The firewall may start to "swear" because someone is trying to connect to the computer, and the router may not let them through the port. In this case, you need to specify the external IP address of the computer in the FileZilla settings in the "Passive mode settings" section. For a local network, you don't have to do anything like that - everything will work right away.

Many of the settings inside the FileZilla server program shouldn't be touched at all. For example, you hardly need to configure the "Security Settings" menu item, which is needed to adjust the server-to-server connection. Also, you don't need to configure "Miscellaneous" and many other menu items. Do not try to parse all program configurations at once, so as not to get confused and create conflict situations in the server operation due to incorrect settings.

Sooner or later, but errors will appear on the server - everyone has them. To calculate them quickly, it is recommended to activate the recording of log files in the "Logging" section of the menu. To do this, determine the maximum size for the file with logs, and also specify the location for such a document on your computer.

In the "Speed ​​Limits" tab you can add restrictions for both outgoing and incoming connections in terms of download speed. But you should not do this if there is no need. After all, one of the main advantages of the FTP protocol is fast loading, which will cease to be such if you set restrictions. After you understand the settings, add users through the "Users" menu - and your server can already be used! Just remember to pass your login information to users. If necessary, you can specify anonymous users without logins. Be sure to specify access rights for users.

Overview of setting up an FTP server under Windows using Serv-U as an example 6.4.

1. What is "FTP"?

Why was this text written at all? Many times I have been asked by novice users of many LANs - "how to exchange files with a neighbor"? After all, it is no longer possible to connect through the network environment, as it was before, because the NetBIOS protocol, which is responsible for supporting the network capabilities of Windows, was banned in LAN. By the way, this was done for a reason, but due to the fact that this protocol is one of the most dangerous holes in the protection of computers, since it is through this hole that most of the virus infection gets ...

Surely, many have heard about FTP, but not everyone knows that this is not a mysterious spell of the ancient Incas, but an English abbreviation that stands for File transfer protocol- file transfer protocol. It is one of the basic Internet protocols designed for the exchange of information. Unlike HTTP, which is primarily used to transfer web texts and images, FTP is used to exchange arbitrary files, often large.

In addition, FTP is convenient for “traversing” directories on a remote computer and for accessing large, branched file structures. HTTP and FTP support authorization, that is, you can make it so that only knowing your username and password will be able to get to you. To share your folders with other users, you need to install an FTP server, and users need to have FTP clients. With the help of the client, users can not only download files from you, but also upload their files to you.

To share your folders with other users, you need to install FTP server and users should have FTP clients... With the help of the client, users can not only download files from you, but also upload their files to you.

A bit of clarification:

There are other ways to exchange files - peer-to-peer clients (such as DC ++, Emule, Torrent), HTTP, FTP, and a few more options. But peer-to-peer clients require complex configuration and the contents of the shared resources are available for everyone to download.

Access to files on a remote computer via FTP is carried out using programs called FTP clients(A www browser such as Opera, Firefox or Microsoft Internet Explorer can be used as a primitive FTP client). Almost all modern operating systems also include a command line FTP client called "ftp".
If you have the Internet, then you can access a lot of information located in various corners of the web. To use FTP, you need a so-called FTP client that connects to the FTP server (the server from where the data is downloaded). Anonymous FTP allows you to connect to the server even without being registered on it (without having a username and password on it). As a rule, anonymous is specified as a login (username), and your e-mail is specified as a password. This is done on large servers so that everyone can download, for example, a free Linux distribution or some other useful software.

Files are transferred in several modes - ASCII mode (short for American Standard Code for Information Interchange) is used to transfer primarily text files (remember that HTML is, in essence, also a text file). Binary mode, as the name suggests, is used to transfer binary code (in other words, it is used for non-text files such as pictures).
When we surf the Internet, open sites, we use HTTP - this protocol is specially designed for loading web pages. At the same time, HTTP is also used to download files. Therefore, many users have a natural question - why use FTP for uploading if HTTP allows it? Each of these protocols was conceived for a different purpose. As we already found out, FTP was designed specifically for transferring files, so this process is most efficiently implemented in it, the larger the file size, the more justified the use of FTP.

The terms "client" and "server" are often found in the computer literature. A server is a program or computer that provides its resources to clients. The server accepts requests from the client and performs the requested actions.
Any server is a program, service (in Windows terms) or daemon (daemon, in Unix terms). Any service accepts requests from clients on one or another software port - through this port, connection establishment and data transfer is organized. For example, the default FTP server accepts requests from clients on port 21.

The FTP client communicates with the FTP server using special FTP commands (depending on the server, they may differ slightly, but in general, the set of commands is more or less standard). Then why not allow the user to enter these commands in order to view the contents of the FTP server without an intermediary, upload files, and set transfer modes. This is exactly how it was at the dawn of the Internet. The pioneers of the global web were hastily typing commands for the FTP server directly from the console. There is such a possibility to this day. True, if for users of Unix-systems this way of communicating with FTP is very familiar, then the owners of Windows probably do not even suspect that their system allows you to do this. It should be noted that using the console version of the FTP client is very exciting at first, and in some cases extremely useful.

In summary, we can say that HTTP is a more universal protocol, which, of course, can be used for uploading files. However, if you want to squeeze the maximum out of the Internet channel and make the download as fast as possible, it makes sense to look for the desired file on an FTP server. The FTP address looks like this:

where user is the username, the colon is the program separator between the username and the password, and password is the password. Doggy means separation between user data and address. Next comes the address itself. It can be an IP address, or it can be a literal value (such as ftp.microsoft.com). The address is again followed by a colon, which separates the address and the connection port number. By default, this port is port 21, but it can be another one assigned by the server administrator.
The address might look like this: ftp://212.199.28.50. This will mean that the username is anonymous, the password is the e-mail address, and the port is 21st.

It is convenient to use the following programs as a client program - Total (Windows) Commander, FAR, FlashFXP, CuteFTP, SmartFTP and even some download managers such as FlashGet and Download Master, which have an FTP client built into the program.

2. Selecting an FTP server

There are a huge number of FTP servers on the market, from microscopic (for one-time transfers) to enterprise-level servers (designed for millions of concurrent connections). For home and semi-professional purposes, several options are sufficient:

Support for multiple domains (IP addresses). This is necessary if you have a local network and the Internet on your computer. And you want to make an FTP server only for LAN or only for the Internet. Or both.

Support for multiple users and their rights. For example, the user Vasya can download erotic pictures from you, while others cannot :)

Support for virtual folders. A very important feature - in order not to create a separate directory for FTP, you can collect it from several folders located on different disks, but the user entering your FTP will see them as if they were all in the same folder.

The ability to limit the transmission rate and the number of concurrent users. Each user is a load on the processor and hard drive of your computer. When there are a lot of them and everyone is downloading a file from you at the same time, your computer can slow down a lot. To prevent users from interfering with you and each other, their number can be limited. That is, let's say two are on your FTP, and the rest who try to connect to your server receive a message like “Too many people. Try to come back later. "

The ability to monitor the actions of the connected user. This is useful for keeping statistics, tuning, and just wondering who is doing what on your server :)
Basically, Microsoft has included its FTP server since Windows 2000. But it is very inconvenient both in setting up and in operation, and has many limitations. Having tried many products, I chose the Serv-U FTP Server as the one that best meets the above conditions. It is about him that I will talk further.

It is also considered professional and stable Gene6 FTP Server... Personally, I also really like the combined HTTP / FTP / Mail / DNS / DHCP free Small HTTP Server... It is distinguished by its simplicity and a very small amount of RAM (about 800 Kbytes !!!).

3. Installing FTP server Serv-U

For an example of installation, let's take "Serv-U.FTP.Server.v6.4.0.4.Corporate.Edition", you can find this archive at the end of the article. After unpacking it, you will receive the file "ServUSetup.exe" - this is the server installer, and the file "keygen.exe" - the generator of the license key for the program. Well, or you don't want to use unlicensed software, you can pay the developer to use the program :)
We launch the installer.
Having agreed with the license, we say where to put the server.
Now we will be asked to specify the required components. To install the server, we need both.
If you bought the program, you can now register it as described in the manual for it. And for the rest, the sequence of actions is as follows: at the bottom right, in the tray, you will see an icon: this means that the server is still turned off. You need to exit this program by selecting Exit and run keygen, generate a key - it will be automatically copied to the clipboard.
The server software installation is complete. Right-click on the icon and select "Start Administrator ..." from the pop-up menu.

4. Setting up the server, creating accounts

After launching the administration program, we will see a window of the following form:

V Main menu the program contains the main control elements, but we will not study them in detail, you yourself can do this later by reading the help for the program. The same goes for the controls and the status bar. The principle of setting up the server is as follows - in the settings tree we select the desired section and in the settings and reports panel we see one or several tabs with settings and (or) statistics. First, let's create our own FTP server. Entering the "Local server" section, you can manage the server installed on your machine. Upon entering the section, the following information will appear in the settings panel:

If you check the box "Start automatically", your server will start with Windows at every boot. Next comes the server status (green - running, red - off). Next is a button that turns on / off the server. And a button that sets the main administrator password. If you set it, no one except you can change the settings of your server. Hereinafter, I will describe only the basic steps for deploying your FTP server, you can learn about other additional features from the help for the program. First, let's configure the global server parameters by going to the "Settings" section.

In the "General" tab we are interested in points:

Max. Upload speed: the maximum speed of uploading files to your server from the client
Max. Download speed: maximum speed of uploading files to clients (all together - this is a global setting)
Max. no. of users: the maximum number of simultaneously connected clients (also a global setting)
Delete partially uploaded files: if the client tried to upload a file to your server, but did not fully upload it, whether it is necessary to delete such an unfinished file. If there is a daw, delete it.
Leave the default settings in all other tabs.

In the section "Activity" you can view a report on the program's operation, add an IP address to the list of banned IP addresses, or send a message to connected clients. We will not delve into these possibilities, so we move on to the next section.

The "Domains" section is the main working tool for the administrator. While it is empty. Right-click on the empty settings panel and select "New Domain" from the menu (you can just press the Ins key). The New Domain Wizard will appear. In the first window you will be asked to select the IP address at which your FTP server will "live". If you leave this field blank, the server will respond to all addresses (for example, both in LAN and on the Internet). If the server is made only for LAN, select your IP address in the local network from the drop-down list:

Pressing the "Next" button, go to the next question - you need to enter the domain name. If you are doing Internet FTP, you can enter its address as the name, this will make it possible not to get confused with a large number of domains. Or you can just enter the name of your FTP, for example "My FTP server":

Again "Next", select the port for the FTP server. By default, 21 TCP ports are used for FTP, but if you want to hide your FTP port from scanners, you can specify a different one, as long as there is no other program on it. Also, do not forget to open this port in the firewall or firewall (if you have one), otherwise no one can get to your FTP server! Choosing a port for a domain allows you to organize multiple FTPs on different ports with different content. This is what domains are for.

Press "Next" 2 times and exit the wizard. We see this screen of the global domain settings:

Items in the "Domain" tab mean:

Name: domain name
Domain IP address: IP address of the domain
Domain type: where the domain settings are stored (in the INI file or in the registry)
Security: whether to maintain SSL secrecy
FTP port number: server port number
Enable dynamic DNS: used on the Internet when the DynDNS service is running
Domain is ... (online / offline): the current state of the domain (green - on, red - off)
Put Domain offline: shutdown domain button

Now let's "fine-tune" the resulting domain. To do this, go to the "Settings" section of our domain:

In the "General" tab pay attention to the following values:

Max no. of users: the maximum number of clients that can connect to the domain at the same time.
Minimum password length: The minimum password length for the user. If not set - not checked

On the Vitual Paths tab virtual folders and paths in it are indicated! The folder is given a virtual name (Vitual name), which will be displayed for the user logged in via ftp, instead of the real one. In this case, these folders must be allowed at least for reading (Read) in the settings for each specific user. How to do it - read below.
Mapped to is the path to the user folder to which the virtual folder will be attached (mounted). The user must also have access to it.

Another tab that you can pay attention to is "Messages":

Here you can replace standard server messages with your own, for example, with the name of your FTP or mail address for communication. Attention! Messages can only be in English or written in transliteration!
We go to the "Users" section and create a new user in the same way as we created the domain before. The New User Wizard will appear. First, you will be asked to enter your username. Under this name, the user will log into your FTP. If FTP is open to everyone, use the name anonymous as the name. For any other user you will be asked for a password, for anonymous user the password will not be asked. Next, we specify the initial directory, which will contain the contents of your FTP, visible to this user:

Then the question should be answered "Yes". The wizard ends and a new user is created. The server is ready to go. Some subtleties of the settings, for example, how to link directories from other disks, you can see in the video file that comes with this archive.

5. Verification of work

Launch your FTP client, select to create a new connection, in the connection parameters, specify the FTP server address, port (if it is not a standard one) and username / password (if not specified, the anonymous user will be used and something resembling E- Mail address (few people indicate their real e-mail). Do not forget to specify the proxy server if you are not connecting directly! Now try to connect to your FTP server. If everything is done correctly, the server should respond immediately.
You can also access your server through a browser in passive mode: ftp: // login: [email protected] your_ip or just ftp: // localhost.

P.S. Do not forget that if you are closed from the outside world by a firewall or router, then port 21 must be opened in them for incoming connections (in a router from WAN to LAN from any ip).

Serv-U FTP Server v6.4 Corporate Edition distribution kit with video instructions can be downloaded.

Continuing the topic of transferring files over the Internet, today I will talk about an FTP server. Although I gave my preference, the FTP server should not be overlooked, as it is a very popular way of transferring files. So, a little theory. What is FTP?

FTP (File Tranfser Protocol) in English means "File Transfer Protocol" and is used to exchange files between computers over the Internet or a local network. A regular browser or even Windows Explorer is enough to log into the FTP server. The only condition is open port 21 (used by default, but you can replace it with your own), that is, it must be open. So, if you have a Firewall or a router, you will have to remember where you have instructions for forwarding 21 ports.

So, let's move on to setting up an FTP server.

1) And the first thing we need is to add components to our operating system. To do this, go to "Control Panel" → "Programs" → "Programs and Features" and click the button on the left "Turn Windows features on or off":

2) In the list that opens, we need to enable the IIS component group, namely: FTP Server, Internet Services and Website Management Tools. It should get the same as in the screenshot:

Click OK and wait for the installation of the components to complete. Depending on the edition of your operating system, you may need a Windows installation disc.

In the window that opens, in the left column, open the tree to the "Sites" tab and click on this tab with the right button. Choose "Add FTP Site":

We indicate the name of the site and the directory that will be accessed via FTP protocol:

We specify the parameters for starting the FTP server. If you do not want the server to start automatically when the system starts, uncheck the box. In the SSL subsection, put a full stop to "No SSL":

On the next page, put a tick in front of "Anonymous" and "Normal" and click done:

The FTP site has been created, we continue with the configuration.

4) Go to "Control Panel" → "System and Security" group → "Windows Firewall" and select "Advanced Settings" in the left column:

Go to the "Inbound Rules" tab. You need to find and include two items:

- FTP server (incoming traffic);
- FTP server traffic in passive mode (incoming FTP traffic in passive mode).

To do this, right-click on the rule and select "Enable Rule":

Then go to the "Rules for outgoing connections" tab and enable the "FTP server traffic (outgoing FTP traffic)" rule:

If you have a Firewall or router installed, you need to open port 21 (TCP) for incoming connections and port 20 (TCP) for outgoing ones.

5) It is necessary to create a user who will have full access to the server via FTP (write / delete). First, you need to create a new user group. Therefore, go to the "Control Panel" → the "System and Security" group → "Administrative Tools" → "Computer Management". In the left part of the window, select the section "Local users and groups" → "Groups". Right-click on an empty space in the central part of the window and select "Create group ...":

We write down the name and description of the group and press the "Create" button:

Go to the "Users" tab and, by analogy, click on an empty space and select "New User":

We register the data and come up with a password (at least eight characters). We also put a check mark on the "Prohibit the user from changing the password" and "The password has no expiration date":

Open the properties of the new user by right-clicking on it. Go to the "Group Membership" tab. Click the button "Add" → "Advanced" → "Search" and select the group that we created a few minutes ago. Click OK.

Click the "Add" button and add the group that we created. We grant the group full access by ticking the appropriate checkbox at the bottom of the window:

Click ok to apply the changes.

Go to "Control Panel" → "Network and Security" group → "Administrative Tools" and open "IIS Manager" → "Sites" and select our site:

We select "Specified roles or user groups" and write the name of our group. Give this group read and write permissions and click OK.

Go back to the site and go to FTP Logging.

Specify the maximum log size or disable it altogether. Click on the right "Apply":

That's all. I hope this article was useful to you, click one of the buttons below to tell your friends about it. Also subscribe to site updates by entering your e-mail in the field on the right.

Thank you for your attention:)

& nbsp & nbsp Abbreviation FTP comes from english F ile T ransfer P rotocol (File Transfer Protocol) is an application layer protocol for exchanging files over the TCP / IP transport protocol between two computers, an FTP client and an FTP server. It is one of the oldest, and nevertheless, still actively used protocol.

FTP protocol is designed to solve the following tasks:

  • access to files and directories on remote hosts
  • ensuring client independence from the type of file system of the remote computer
  • reliable data transmission
  • use of resources of the remote system.
  • FTP protocol supports two connection channels at once - one for transfer teams and the results of their implementation, the other for exchange data... With the standard settings, the FTP server uses TCP port 21 to establish a channel for transmitting and receiving commands and TCP port 20 to establish a channel for receiving / transmitting data.

    The FTP server listens for connections from FTP clients on TCP port 21 and, after establishing a connection, receives and processes FTP commands which are plain text strings. The commands define the connection parameters, the type of data transferred, and actions with respect to files and directories. After agreeing on the transmission parameters, one of the exchange participants becomes passive, waiting for incoming connections for the data exchange channel, and the second establishes a connection to this port and starts transmission. When the transfer is complete, the data connection is closed, but the control connection remains open, allowing the FTP session to continue and a new data transfer to be created.

    FTP can be used not only to transfer data between a client and a server, but also between two servers. In this case, the FTP client establishes a control connection with both FTP servers, switches one of them to passive mode, and the second to active, creating a data transfer channel between them.

    An FTP client is a program that connects to an FTP server and performs the necessary operations to view the contents of the server's directories, receive, transfer, and delete files or folders. A regular browser, operating system components or specially developed software products, such as a popular download manager, can be used as such a program. Download Master or multifunctional free FileZilla FTP Client.

    The FTP protocol was developed back in the days when the client and server interacted directly, without any intermediate transformations of TCP packets, and in standard mode it assumes the possibility of creating a TCP connection not only at the initiative of the client, but also at the initiative of the server from TCP port 20 to TCP - the port of the client whose number is transmitted during the creation of a data transfer session.

    The realities of today are such that such a TCP connection from a server to a client in the vast majority of cases is impossible or very difficult to implement due to the fact that in most cases, a technology with network addresses translation is used to connect to the Internet. NAT(Network Address Translation) when the client does not have a network interface available to create a direct TCP connection from the Internet. A typical scheme for a standard Internet connection looks like this:

    Internet connection is performed through a special device - Router(router with NAT function), which has at least two network ports - one connected to the provider's network, which has a network interface with a routed IP address (so-called "white IP"), for example 212.248.22.144, and a port with a network interface for connecting LAN devices with a private, non-routable IP address, for example 192.168.1.1 ("gray IP"). When creating connections from network devices on the local network to external network nodes, IP packets are sent to the router, which translates addresses and ports in such a way that the sender's address becomes its white IP address... The translation results are saved and when a response packet is received, the reverse address translation is performed. Thus, the router provides forwarding of TCP / IP packets from any devices on the local network to external networks and forwarding the received response packets. But in cases where a packet is received at the input of the network interface connected to the provider's network that has nothing to do with the response TCP packets, the following options for the reaction of the router software are possible:

    The packet is ignored because there is no network service to process it.

    A packet is received and processed by the network service of the router itself, if such a service exists and is waiting for an inbound connection ("listening") on the port, the number of which is indicated in the received packet.

    The packet is forwarded to a server in the local network that is waiting for this type of incoming connections in accordance with the port mapping rules specified by the router settings.

    Therefore, at present, the so-called "passive mode" has become the main operating mode for FTP, in which TCP connections are made only from the client to the server's TCP port. The active mode is used in cases where there is a possibility of TCP - connections from the server to the client ports, for example, when they are in the same local network. The choice of the FTP connection mode is made by special commands:

    PASV- the client sends a command to carry out the data exchange in a passive mode. The server will return the address and port to which you need to connect to receive or transmit data. An example of a fragment of an FTP session with the passive mode setting:

    PASSV- command to switch to passive mode, transmitted by FTP - client to FTP server

    227 Entering Passive Mode (212,248,22,144,195,89)- FTP server response, where 227 is the response code, a text message about switching to passive mode and in brackets the IP address and port number that will be used to create the data transmission channel. The address and port number are displayed as decimal numbers, separated by commas. The first 4 numbers are the IP address (212.248.22.144), the remaining 2 numbers set the port number, which is calculated by the formula - the first number is multiplied by 256 and the second number is added to the result, in this example the port number is 195 * 256 +89 = 50017

    PORT Client IP address port number- the client sends a command to establish a session in active mode. The IP address and port number are specified in the same format as in the previous example, for example PORT 212.248.22.144,195,89 To organize data transfer, the server itself connects to the client on the specified port.

    Installing and configuring FileZilla FTP Server.

    You can download the FileZilla Server installation package for your operating system version at

    The server is installed in a standard way, with the exception of the item with the choice of server control panel settings:

    This is the main server management tool through which all the necessary settings are made. By default, the control panel operates on a loopback interface without password access. If necessary, for example, if you need to remotely manage the FTP server, these settings can be changed.

    After the installation is complete, a window will open to connect to the server:

    After entering the IP address, port number and password (if you specified them during installation), the FileZilla Server control panel opens:

    The main menu and control panel buttons are located in the upper part of the window. Below there are two areas - server information messages and statistical information. Overall, the FTP FileZilla Servver control panel is pretty simple and easy to use. Main menu items:

    File- operating modes of the FTP server control panel. Contains subparagraphs

    - Connect to Server- connect to server
    - Disconnect- disconnect from the server
    - Quit- shutdown of the control panel.

    Server- FTP server management. Contains subparagraphs:

    - Active- start / stop FTP server. When the checkbox is checked, the FTP server is started, when it is unchecked, it is stopped.
    - Lock- deny / allow connections to the server. If the checkbox is checked, new connections to the server are prohibited.

    Edit- editing settings. Subparagraphs:

    - Settings- basic server settings.
    - Users- FTP server user settings
    - Groups- settings of user groups.

    As an example, let's configure the server for the following conditions:

  • the server is behind NAT, has a private IP address, but must be accessible from the Internet, supports passive mode, and uses non-standard TCP ports. The use of non-standard ports can reduce the likelihood of hacker attacks, and in addition, some providers use traffic filtering and block the standard 20 and 21 ports.
  • users have the ability to download from the server, upload to the server, delete and rename files and folders.
  • in the case of using a dynamic IP-address, it is required to ensure the availability of the server by the DNS-name.
  • the server will operate on a workstation under Windows 7 / Windows 8.
  • In other words, you need to create an Internet-accessible FTP server to exchange files between users, of course for free. It is quite clear that in addition to creating the necessary configuration of the FTP server itself, it will be necessary to change some router settings, Windows firewall parameters, solve the problem of a dynamic IP address so that the server is accessible by name, regardless of the IP address change.

    Solving the problem of a dynamic IP address.

    & nbsp & nbsp This problem does not require a solution in cases where a static IP address is used when connecting to the Internet, or a dynamic one, but in accordance with the provider's settings, it is almost always the same. Otherwise, you can use the technology called Dynamic DNS (DDNS). This technology allows to update the information about the IP address on the DNS server in almost real time, and to access the router (and services behind it) by the registered name, regardless of the dynamic IP change.

    To implement this technology free of charge, you will need to register with some kind of dynamic DNS service and install client software to update the DNS record if the corresponding IP address changes. Dynamic DNS is usually supported by manufacturers of network equipment (D-Link, Zyxel, etc.), some hosting and specialized companies, such as the well-known DynDNS. However, after in the second half of 2014, all services that were provided to registered users free of charge for non-commercial use became paid, the most popular solution, perhaps, was the use of dynamic DNS based on the service. No-IP.org, which in a free mode provides support services for 2 nodes with dynamic IP. To use the service for free, you will need to register, and periodically (approximately once a month) visit the site to update information about the nodes used with dynamic IP. If you skip updating the node data, the service is suspended, and, accordingly, it will be impossible to connect to the node by name. When using the service for a fee, the update is not required.

    & nbsp & nbsp Almost all modern routers (modems) have built-in support for a dynamic DNS client. Setting it up is usually very simple - you fill in the fields with the username and password, as well as the hostname, obtained during registration on the DDNS service. Example for Zyxel P660RU2

    & nbsp & nbsp Using the DDNS client built into the router / modem is preferable to the DNS data update utility operating in the OS environment, since it allows you to implement additional capabilities, such as controlling the router via the Internet when the computer is turned off and remotely turning on the power of computers behind NAT using technology Wake on lan.

    In those cases where the built-in DDNS client is not possible, you will have to make do with application software - a dynamic DNS support client program. Such a program periodically connects to the server that maintains the registered domain name associated with the router through which the Internet connection is made, and calls the IP update procedure when it changes. The server settings are made in such a way that the comparison of the DNS name and the IP address of the Internet connection is performed in a very short time, and the dynamic nature of the address has practically no effect on the performance of the services associated with the DNS name.

    The procedure is as follows:

  • We go to the site No-IP.org. To work with an existing or new account, use the button "Sign In"(at the top right of the page).

  • Create, if it has not yet been created, your account - click "Create Account"... The registration form changes from time to time, but it is mandatory to enter the desired username, password and your E-mail. A letter with a link to confirm registration is sent to the e-mail specified during registration. When registering, select free access - press the button Free sign up after filling in all the required form fields.
  • After successful registration, we enter the site and add an entry for our site - press the button "Add Hosts"

    In fact, only the selected hostname needs to be entered, in this case - myhost8.ddns.net... The rest of the parameters do not need to be changed. Then you need to download and install special software - Dynamic Update Client(DUC), the link to which is located on the main page of the site. After the installation of the DUC is complete, it will start and an authorization window will open, where you need to enter the username or E-mail and password received during registration on the no-ip.org website. Then press the button Edit Hosta and put a check mark in front of the previously created hostname (myhost8.ddns.net). Now, the selected hostname will always match the "white IP address" of your Internet connection. If you have problems updating the IP address, check to see if the DUC client's network activity is being blocked by a firewall.

    Setting up an FTP server

    & nbsp & nbsp The use of non-standard port numbers for the FTP server is not at all necessary if the provider does not use traffic filtering, or if you do not care about port scanning for vulnerabilities and attempts to brute-force passwords. In this article, using an FTP server with non-standard TCP ports is presented as one of the possible options.

    FileZilla Server settings are made through the menu "Edit" - "Settings"

    Window General Settings intended for general FTP server settings.

    In the "Listen on this port" field, you can specify the port number for incoming TCP connections. By default, this field is set to 21 , and to use a non-standard number, you need to specify the selected value, for example - 12321 ... Using a non-standard TCP port has some inconvenience, since it requires you to specify its value when creating a session:

    If the server is planned to be used both with access from the Internet and in a local network, it makes sense to leave the default value of 21, and use a non-standard port number for connections from the Internet by configuring the forwarding of packets received on port 12321 of the router to port 21 of the FTP server in local network. With this setting, you do not need to specify the port number for FTP sessions within the local network.

    Other parameters are for performance tuning and session timeouts. They can be left unchanged. The rest of the general settings sections can also be left by default:

    Welcome message- the text that is sent to the client when connecting.

    IP Binding- on which network interface client connections will be expected. By default - on any, but you can specify a specific one, for example - 192.168.1.3.

    IP Filter- setting up rules for filtering IP addresses of clients. By default - connections are allowed for any IP.

    Chapter Passive mode settings serves for the settings of passive FTP mode and will require changing almost all the default parameters.

    The port numbers that will be used for data transmission in passive mode must be set manually, since you will need to configure the router to redirect them to the network interface that the server listens to. Therefore, you need to check the box to enable the "Use custom port range" mode and set the range - for example, from 50000 before 50020 ... The number of ports the server listens to determines the limit for the number of simultaneous data transmissions.

    Subsection IPv4 specific defines the IP address that will be sent by the server in response to the PASV command. In this case, it should not be the server's own IP 192.168.1.3, but the "white IP" of our Internet connection. Therefore, you need to set the "Use the following IP" mode and instead of the IP address, enter the name obtained during registration on the dynamic DNS service - myhost8.ddns.net... Alternatively, you can use the FileZilla project's external IP detection mode by enabling. "Retrieve external IP Address from:". You can choose this option when you cannot use the dynamic DNS facility. If you intend to use an FTP server in your local network, you need to set the "Don" t use external IP for local connections "mode (do not use the external IP address for connections within the local network)

    The rest of the server settings can be left unchanged or, if necessary, performed later: Security settings- Security Settings. By default - connections are denied that can be used to implement DDoS attacks

    Miscellaneous- adjusting the size of buffers and other parameters of logs and some FTP commands.

    Admin Interface settings- server control panel settings. You can specify the network interface, the listening port number, the IP addresses from which the connection to the control panel is allowed and the password.

    Logging- server event log settings. By default, the file is not written to.

    Speed ​​limit- settings for limiting the data transfer rate. By default - unlimited.

    Filetransfer compression- file compression settings during transfer. The default is no compression.

    SSL / TLS settings enabling encryption of transmitted data. The default is no encryption.

    Autoban- enable automatic blocking of users who guess the password to connect. By default, automatic blocking is disabled.

    Configuring Port Forwarding and Firewall

    In order for the FTP server to be accessible from the Internet, it is necessary to configure the router so that incoming connections arriving at certain TCP ports on the external interface are redirected to TCP ports that are listened to by the FTP server on the internal network. For different models of routers, the settings may differ in terminology, but their meaning is the same - a TCP packet received on the external (WAN) interface with a specific port number is sent to the local network to the required IP address and port. Example of D-Link DIR-320NRU router settings for port forwarding used for passive FTP mode:

    Packets received on the "white IP" interface and having port numbers in the range of 50000-50020 will be redirected to the IP address specified in the "Internal IP" field (in our case, 192.168.1.3). Likewise, a redirect is created for port 50021 if you changed the default port number, or to port 21 of the FTP server if you left it unchanged.

    After applying these settings, the FTP server will be available at the URL ftp://myhost8.ddns.net:50021 or, for a connection within a local network:

    ftp://192.168.1.3- if you have not changed the default port number (21) in the FTP server settings.

    ftp://192.168.1.3:50021- if a non-standard port number is used.

    A computer name can be used instead of an IP address if it can be resolved to an IP address

    ftp: // comp1

    ftp://comp1.mydomain.ru

    Diagnosing problems

    If the connection to the FTP server does not work, then there may be problems with the firewall blocking the connections required for the operation of the created FTP server. If you are using the built-in Windows firewall, you need to add a rule to allow network activity for the "FileZilla FTP server" service. If you use a third-party firewall or antivirus with traffic filtering, then you need to create a corresponding rule using the available settings tools to allow network connections. Options are possible when settings are made to allow any network activity of a particular program, or to allow selected addresses and ports that are applied to all programs.

    The best place to start diagnostics is on the FTP server itself. As a diagnostic tool, you can use the standard telnet - client(utility telnet.exe). All firewalls do not block connections on the loopback interface, and to verify that the server settings are correct, you can connect to it by entering the command:

    telnet localhost 21- if the standard port number is used.

    telnet localhost 50021- if the standard port number has been changed.

    When this command is executed, a connection to the FTP server is made via a loopback interface, and the server prompt (Welcome Message) should be displayed in the telnet window. If it does not, the server may be stopped, there is a port conflict, or port 21 (50021) is not listening. For diagnostics, you can use the command netstat:

    netstat –nab

    Command line options mean:

    n- use numeric port numbers and IP addresses

    a- display all connections and listening ports

    b- display the names of programs participating in the creation of connections.

    An example of the displayed command results:

    Active connections

    Name & nbsp & nbsp Local address & nbsp & nbsp External address & nbsp & nbsp Status
    TCP & nbsp & nbsp & nbsp & nbsp 0.0.0.0:21 & nbsp & nbsp & nbsp & nbsp & nbsp & nbsp & nbsp & nbsp 0.0.0.0 0 & nbsp & nbsp & nbsp & nbsp & nbsp & nbsp & nbsp & nbsp LISTENING
    TCP & nbsp & nbsp & nbsp & nbsp 0.0.0.0:135 & nbsp & nbsp & nbsp & nbsp & nbsp & nbsp & nbsp 0.0.0.0 0 & nbsp & nbsp & nbsp & nbsp & nbsp & nbsp & nbsp & nbsp LISTENING
    RpcSs

    In a collumn Local address there is a value 0.0.0.0:21 , which says that the program named FileZilla Server.exe listens (state LISTENING) TCP port number 21 on all network interfaces. If a specific interface and a different port number were specified in the FTP server settings, then this value will contain IP: port, For example - 192.168.1.3:50021

    To display the results in page mode, you can use the command:

    netstat -nab | more

    Or use search results by port number: netstat -nab | find ": 21"

    If the server is not available on the non-loopback interface, and is available on the loopback, you need to understand the firewall settings.

    Setting up users and groups.

    Users and groups are configured via the "Edit" - "Users" ("Groups") menu. It is not necessary to create groups, but sometimes it is convenient for those cases when there are a large number of users and their rights with respect to the FTP server differ. The settings for both groups and users are almost identical:

    This example displays the result of adding an FTP server user named user1 has full rights to write, read, delete and merge files, as well as view the contents, delete and create subdirectories in a directory C: \ ftp \ public

    On the page General adding, deleting and changing user properties is performed.
    On the page Shared Folders the settings are made that determine the list of file system directories that will be used by the FTP server to provide access to them via the FTP protocol. Each user or group of users can be granted their own directory with certain rights in relation to its contents.
    On the page Speed ​​limits you can set limits on the data exchange rate.
    On the page IP Filter you can set filtering rules for the user's IP address by specifying the addresses from which the connection to the server is prohibited or allowed.

    List of basic FTP commands

    ABOR - Abort file transfer
    CDUP - Change directory upstream.
    CWD - Change current directory.
    DELE - Delete file (DELE filename).
    HELP - Displays a list of commands accepted by the server.
    LIST - Returns a list of files in a directory. The list is sent over a data connection (port 20).
    MDTM - Returns the modification time of a file.
    MKD - Create directory.
    NLST - Returns a list of directory files in a shorter format than LIST. The list is sent over a data connection (port 20).
    NOOP - Empty operation
    PASV - Enter passive mode. The server will return the address and port to which you need to connect to pick up the data. Transmission will begin when you enter RETR, LIST, etc.
    PORT - Enter active mode. For example PORT 12,34,45,56,78,89. In contrast to the passive mode, for data transfer, the server itself connects to the client.
    PWD - Returns the current server directory.
    QUIT - Disconnect
    REIN - Reinitialize connection
    RETR - Download file. RETR must be preceded by a PASV or PORT command.
    RMD - Remove Directory
    RNFR and RNTO - Rename file. RNFR - what to rename, RNTO - what.
    SIZE - Returns the size of the file
    STOR - Upload a file to the server. STOR must be preceded by a PASV or PORT command.
    SYST - Returns the system type (UNIX, WIN,)
    TYPE - Set the type of file transfer (A - text ASCII, I - binary)
    USER - Username to log into the server

    Sample FTP session

    FTP client connects to server with username user1, with an empty password and downloads a file named cpu-v... Messages from the FTP server are highlighted in red, and messages from the FTP client are highlighted in blue. The exchange of directives and parameters may differ slightly for different versions of the FTP client and FTP server software.

    After connecting, the server sends information about itself to the client:
    220-FileZilla Server version 0.9.45 beta
    220-written by Tim Kosse ( [email protected])
    220 Please visit http://sourceforge.net/projects/filezilla/
    The client passes the username:
    USER user1
    The server asks for a password:
    331 Password required for user1
    The client passes in an empty password:
    PASS
    The server checks the user account and reports the start of the session:
    230 Logged on
    The client asks for the type of operating system on the server:
    SYST
    The server reports that the type Unix emulated by Filezilla server:
    215 UNIX emulated by FileZilla
    The client requests a list of parameters supported by the server:
    FEAT
    The server responds with a list of supported parameters:
    211-Features:
    MDTM
    REST STREAM
    SIZE
    MLST type *; size *; modify *;
    MLSD
    UTF8
    CLNT
    MFMT
    211 End

    The client asks for the current server directory:
    PWD
    The server reports that the current directory is root ("/"):
    257 "/" is current directory.
    The client reports that it will transmit binary data:
    TYPE I

    The server confirms the type of transmitted data:
    200 Type set to I
    The client reports that it will use passive FTP mode:
    PASV
    The server reports the transition to passive mode and transmits the IP and port for passive FTP mode.
    227 Entering Passive Mode (212,248,22,114,195,97)
    The client requests to receive a file named cpu-v from the current server directory
    RETR cpu-v
    The server informs about the start of data transfer:
    150 Opening data channel for file download from server of "/ cpu-v"
    Upon completion, the server reports a successful transfer:
    226 Successfully transferred "/ cpu-v"

    In conclusion, I will add that the Filezilla project includes not only the development and maintenance of a high-quality free FTP server, but also a popular free FTP client.

    An article with a brief description of a free FTP client for Linux, Mac OS and Windows. This FTP client supports many application data transfer protocols - FTP, FTP over SSL / TLS (FTPS), SSH File Transfer Protocol (SFTP), HTTP, SOCKS and FTP-Proxy. In other words, Filezilla FTP Client is a universal software for receiving and transferring files over all modern application protocols between nodes on various platforms.

    FTP is a very convenient way to exchange information with someone. Having installed an FTP server, you can both receive files and share your files with others. Everything is very conveniently configured, on a remote computer your FTP server looks like a regular folder, from where you can even copy the necessary files with an explorer.

    There are several different programs for making an FTP server from your computer. They differ in capabilities, reliability, security, settings and licenses. In my opinion, some of the best Windows servers are Serv-U and Gene 6.

    The choice of software is a private matter for everyone, but on this page I will tell you how to configure Serv-U 6 series (versions 6.4.x.x).

    System requirements

    • A computer, almost any.
    • Internet, with external IP address, if you are going to exchange or distribute data over the Internet, or any, if you want to exchange data within the local network.
    • It is desirable to have unlimited traffic, but even on limit traffic it is possible - they usually take into account only incoming traffic, and all outgoing traffic is free. The ratio is somewhere around 50 to 1, that is, for every 50 megabytes of traffic downloaded from you, 1 megabyte of reverse (FTP commands, various technical information) will be downloaded to you. Well, if it is being downloaded to you, then vice versa.
    • Several ports need to be open. According to the FTP standard, 2 ports are required: 21 for transferring commands and a certain range from the upper ports (say, from 2000 to 3000) for transferring the actual data. If your port 21 is closed to the entrance (for example, Moscow Stream filters incoming traffic on this port, covering it with a concern for protecting users, and you cannot disable this filtering), then you can transfer it to another. But in this case, you will need to specify the port when giving the link: "ftp://dimonius.homeip.net:22/" for port 22.
    • If you have a router (LAN-ADSL modem or WiFi modem), then additional configuration may be required for the modem to transmit data via the ports specified in the previous paragraph to the computer and back (this is strictly individual for each router, so I will not raise it here this question).

    It should be borne in mind that the speed of your outgoing channel will be divided among all the pumping ones, so you should calculate the resources and set adequate limits on the number of pumping ones and the speed.

    There is also a possibility that your antivirus will warn you that you are installing an FTP server with which you will be able to access the files on your computer (they usually define it as "Program.Serv-U"), this is normal and you do not need to contact attention to this.

    Installation and initial configuration of Serv-U

    1. We download Serv-U from my FTP, or from the manufacturer's website.
    2. Install. The installation does not differ from the installation of other programs - you just need to specify the installation folder and click "Next" several times.
    3. The FTP server consists of a service and a management program. After installation, at the last step, you will be prompted to launch the administration module (the Start Serv-U Administrator program checkbox), check the box and the setup wizard will start.
    4. Answer step by step:
      • Enable small images with menu items - Yes
      • IP address - empty
      • Domain name - " Local"
      • Install as system service - Yes
      • Allow anonymous access - Yes
      • Anonimous home directory - the starting directory for all FTP accounts. For instance " c: \ FTP"(the folder must be created with a conductor).
      • Lock anonimous users in to their home directory - Yes
      • Create named account - #
    5. The initial configuration has been completed, and the main window of the server configuration program will open.
    6. For a start, it's a good idea to register the program (the line in the tree on the left is License).
    7. Then select Settings and there we set up 3 tabs: "General", "Dir Cache" and "Advanced" according to the illustrations.
    8. The "Activity" tab serves for user control. On it you can see who is currently logged into the server, who is downloading what, and through the "Spy User" by right-clicking on the mouse, you can follow the actions of a particular user from the moment of login.
    9. Select "Local" in "Domains". The global server settings that we configured through the configuration wizard appear on the right. If necessary, then it will be possible to change them later, whether to create a new server with different settings (for example, on a different port or if you have several network cards, on different IP addresses for different subnets).
    10. Now we will set up the "Local" branch in "Domains" one by one.
    11. Select "Settings" and set up the bookmarks one by one.
    12. The "General" tab is configured according to the picture.
    13. "Virtual path"a very important bookmark, and you will need it more than once. A virtual file system is configured on it. That is, regardless of where the folder is physically (on which disk and in which subfolder) on the FTP server, you can place them and name them whatever you want, without affecting physical names and position.

      We will be interested in the upper plate "Virtual path mapping", the lower one is used to create links to already added files and folders (let's say you want to add 1 folder to 2 subfolders on the FTP server at once). Click the "Add" button below the top list and enter:

      • Physical path - the path to the real folder or file. It can be selected via the button with a drawer to the right of the input field. For example, let's enter "C: \ Video \"
      • Map physical path to - the path to which we will attach our folder. Relatively " C: \ FTP", which we introduced in paragraph 4.6. In our example, it will be" C: \ FTP ", and then, when entering the server, users will see the" Video "subfolder in their folder.
      • Mapped file name - the name that the user will see. For our example, let's say "Movies" rather than the abstract "Video".
      • In the same way, we add the rest of the folders, to which we are going to give access later.
    14. On "Dir access" you can add IP addresses and subnets, which will be allowed access or, on the contrary, denied to the current server. This is used if someone is trying to hack the entire server, or you have multiple servers and you want to prevent people from one subnet from logging into another server. In most cases, everything will be empty here.
    15. "Messages" - you can configure messages that will be reported by the server when connecting, leaving the client and in some other cases.
    16. "Logging" - here you can leave the checkboxes by default, only in the "Log file name" field through the "browse" button, select any file (say Log.txt in the folder where the server is installed), and check the "Enable logging to file" checkbox below ... This will allow you to see who did what and who poured and poured what. Do not forget to clean the log file from time to time, otherwise it will grow to a very large size.
    17. "UL / DL Ratios" - allows you to adjust the ratio of uploaded to downloaded, but usually it is configured for specific users, and not for the server as a whole.
    18. On the "Advanced" tab, leave all the checkboxes by default.
    19. The "Activity" section duplicates the same section above, only for users of a specific server. Since usually the server is configured on one computer alone, then this section completely duplicates the same section above.
    20. Setting up users and groups is described in the next section.
    21. Don't forget to open ports 21, 2000-2500 on your firewall. Setting up an FTP server without firewalling your computer is not a good idea.
    22. If you have a router, then in the "Port Mapping" (or simply "Mapping") section of the web interface, you must specify the port number and indicate to translate them to the IP address of your computer. In this case, the computer must have a static address - this is done in the properties of the Windows connection (Start - Settings - Network Connections - Local Area Connection (by right-clicking) - Properties - Internet Protocol (TCP / IP) - Properties)

    Configuring Users and Access

    1. Highlight the "Users" branch in the Serv-U administrator and press Ins. Next, you should specify the username in turn (it is better to use English letters and numbers), the password, the user's initial folder (which will be shown to him after the login, that is, the folder that we selected in paragraph 4.6 of the "Installation and Initial Serv-U Configuration" section) , and answer "Yes" to the question "Lock user into home dir".
    2. If you select the created user, then on the "Account" tab you can configure to change the username and password, temporarily block the account (checkbox "Disable Account"), indicate which groups the user and his home directory belong to.
    3. On the "General" tab, you can configure basic user settings:
      • "Requre secure connection" - require a secure connection. Need not.
      • "Hide hidden files" - do not show hidden files. Usually not needed.
      • "Always allow login" - not needed.
      • "Allow only X logins from one IP" - allow only X logins from one IP. It is recommended to set 2-4 on general accounts and not fill out on personal ones.
      • "Allow user to change password" - allow the user to change the password. You don't need it on general accounts, you can bet on personal ones.
      The rest of the fields are optional, except for "Idle timeout" (idle time after which the connection will be automatically disconnected) - it is recommended to set 10 minutes. So that incorrectly disconnected users and users who do nothing do not occupy the channel.
    4. The Dir Access tab shows the folders to which the user will have access. First, the folders must be added to the settings of virtual paths (section "Installation and initial configuration of Serv-U", point 13). There, for each folder, the type of access to this folder is checked: listing (list), reading files (read), writing (write), creating files (create), deleting (delete), starting (execute). The same thing, except for the launch, there is also regarding subdirectories, besides there is a checkbox "including nested" (Inherit), so that the same settings apply to nested folders and files. Some of the folders and files here may be present on a gray background - this is what users have access to as a member of groups.
    5. The "IP Access" tab regulates access by IP. If you want to make yourself personal access to important folders, say from work, then it makes sense to restrict access by IP - only from work or only from home. Even if you accidentally pick up a Trojan or someone sniffers your password, it will not be able to infect your sites or steal important data.
    6. On the "UL / DL Ratios" you can set the ratios, that is, set the condition that until you get a few megabytes, it will not be possible to merge. The proportions can be adjusted, which is convenient when you want to force people to share with you. True, no one guarantees that you will not be flooded with something large and completely unnecessary, such as a Windows swap file or some uncompressed video), as well as adjust how much you can upload by volume so that one user does not completely clog your disk.
    7. And, finally, on the "Quota" tab, you can set limits on the volume of the disk allocated to this account (so that users do not fill the entire disk)

    Passwords for general access can be set simple, but complex passwords for accounts with important data - from small and large letters, numbers and special characters.

    Configuring DynDns

    If you distribute data on the Internet, and you have a dynamic IP, then a problem arises. When reconnecting, the address changes and you need to somehow find out the new one. Constantly editing information about the IP address is not convenient for both the server owner and the clients. To solve the problem, you can register on the dedicated DynDns website. After free registration, you will be given a third-level name with a second-level domain of your choice (such as dimonius.homeip.net or dimonius.dyndns.org), this service has a lot of different domains and there is plenty to choose from. Then a small program is installed on the computer, where the account data is entered, and when reconnecting, it updates the data on the DynDns website and the name always refers to the current IP address. if you have a router, then many of them can work with DynDns right out of the box - just go to the appropriate item in the router's Web interface and enter your account details.


    To register and configure a domain, you need:
    1. Go to the DynDns website, to the registration form.
    2. Enter your nickname, password, mail. Select a subdomain of your site.
    3. Download the program from here and install it.
    4. Enter your account details in it.
    5. The program must start together with Windows in order to monitor the change of the IP address.
  • Top related articles