Network Sharing is imperative! Network Sharing

As a network administrator, I was asked by my boss today: "I heard that everyone is sharing songs, games, and so on the Internet. I have shut down all these games from today! I will check it in 2 days. Remember it all! The same is true for servers ". I'm dizzy! In the first sentence, network sharing is useless. So they went down to the customer sites and banned their network sharing. In order to be more secure, they simply removed the sharing service and printing. However, the following question arises: What should I do when some public files need to be exchanged? This is banned on the server. It is impossible for the person at the top to identify the problem. Since the question has come out, can you switch files without network sharing? Fortunately, I was good at research and realized two methods in a short time. Let's look at my practices below:

The basic method is to use the client to adopt IE and put all the files to be exchanged on the server for unified management, which is greatly enhanced in terms of security and management.

1. WEB Sharing

Install IIS on a Windows 2000 Server. Method: click "Control Panel"> "Add/delete programs"> "Add/delete WINDOWS Components" to check INTERNET services, in this case, you may need a Windows installation CD. After the folder is added, open the folder to be shared, such as KAV. a web Sharing dialog box is displayed, indicating an alias. The default name is the same as that of the original directory, select read from the access permission options in the middle. After all settings are complete, click OK! The server side settings are complete. If the client needs to access this folder, open IE and enter: http: // tw-02/kav in the address bar, where the TW-02 is the machine name of the server and you will be able to see the folder, you can right-click the desired files and select "Save as target" to save the files locally. If you need to download all files, you can install a FLASHGET file and use it to download all the links. This method is good, but its disadvantage is not false: first, the interface looks unfriendly, which is far different from copying files in the resource manager directly in "Network neighbors, in addition, you can only implement the Single-stem mode. If you need to collect files handed in by the client, it is not convenient. All WEB Sharing is suitable for issuing the publish mode, for example, this method is feasible when documents with a small number of files need to be distributed.

2. FTP sharing

Maybe you only want to think that FTP is not used for setting up file exchanges on the Internet? In fact, it is the same for LAN exchange, and it can achieve its flexibility and security for file management. Next I will take SER-U as an example to explain how to achieve a simple! Install the SER-U5 on the server, and the settings of the SER-U can be found in other relevant documents, which are not described here. After using its default configuration, you can set up a user name named anonymous and specify a main directory for it. The main directory is E: ftp. You can set various permissions for the shared directory, for example, read, write, list, and no list permission, the folder will not be displayed in the user's window. Because FTP uses its own unique user and security mechanism, with better flexibility than Microsoft, you can define related permissions and set up different users to achieve File Communication. Enter ftp: // 192.168.0.2 in the address bar to access the configured FTP server. The IP address is required here! I don't feel familiar with it. In fact, what is the difference between it and the resource manager? When you need files or folders in it, you only need to select and hold it down and drag it to your local destination, if the folder has the write permission, drag and drop the file to the window in the same way. My practice is to open a public account for the Communication of general files, and then open an account for file exchange based on the previous article anonymous, allow the client to have certain write permissions on the directory during access, and of course restrict their storage space to save the server space for no reason. Someone may ask if the user can delete the file on FTP or rewrite it at will, by default, you cannot perform unauthorized operations if you do not delete, write, or append permissions to a directory in your account.

The header is actually checked. I checked a client to see if it was shared again. I even used my computer to view it on the network. I was very satisfied when I found that there was no mess in the network, when I learned that I used a flexible method to share the network, I repeatedly said, "Good, no mistakes, and enhanced management. It is very good!" If you are interested, try again!