Let IIS support FLV details setting method _win Server

Most of the domestic Win2003 host, FLV format File Upload server can not play, the default is not specified output FLV This format although the FTP can be seen, but not through HTTP access, can not be played. The reason is that WIN2003 has tightened the mime verification of IIS6, and all the unregistered extended file formats show 404 errors. Manually add a MIME mapping relationship to the HTTP header->mime in the IIS site Properties, MIME type: video/x-flv extension:. flv, which can be played through flash7+ client load.
"Virtual host does not support FLV format Files": For example, your FLV file name is 1.flv, a directory named "1.flv" is built on the virtual host, and the FLV format file in this directory is renamed: Index.htm, so that's it. The filename address in the player remains intact.

let IIS support the details of FLV Setup methods:
Iis--> website---> Properties--->http performance--->mime type---> NEW:
Extension:. flv (Note that there is a. In front of the FLV.)
MIME type: Flv-application/octet-stream
as shown in the following illustration:

you have to set the content

1: Active Server Pages,internet Data Connector in Web service extensions, RPC Proxy service extensions, and server-side include files must be set to allow conditions

2: "Website"-"Properties-" Home directory-"configuration-" option-"Start parent path

3: "Website"-"Properties-" services-"in isolation mode, select" Run WWW service in IIS5.0 isolation mode "

4: Start-"procedures-" management tools-"services." Find RPC services, double-click-"Login-" allow services to interact with desktop

This allows the ASP's Server.CreateObject ("Wscript.Shell") to be run under windows2003

Originally I want to use asp.net to do this procedure, in Asp.netzh also has been the problem. So the use of ASP
Functionality can be implemented in ASP. I did not do it under the ASP.net, if you are interested you can try!


2: The solution:

① deletes or renames the following hazardous ASP components:
Wscript.Shell, WSCRIPT.SHELL.1, Wscript.Network, Wscript.network.1, ADODB.stream, shell.application
Start-------> Run--------->regedit, open Registry Editor, press Ctrl+f, and then enter the name of the component above Wscript.Shell and the corresponding classid, then delete or change the name ( Here suggest that you rename, if there are some of the Web page ASP program to use the above components, just write the ASP code when we change the component name can be used normally. Of course if you are sure that your ASP program does not use the above components, or straight
Delete the mind some ^_^, according to the general generally will not do these components. After you delete or rename the IISReset, you can increase the efficiency after restarting IIS. )
[Note: Because ADODB.stream this component has a lot of web pages will be used, so if your server is open virtual host, it is recommended to deal with the situation. ]

② about the security of the FSO that is commonly said for File System Object (classid:0d43fe01-f093-11cf-8940-00a0c9054228), if your server must use the FSO, ( Some virtual host servers generally need to open the FSO function can refer to my another article on the FSO security solution: Microsoft Windows Server FSO security vulnerabilities solution. If you are sure you don't want to use it, you can simply reverse-register the component.

③ Direct counter Registration, uninstall these dangerous components method: (Practical to do not want to use ① and ② class such trivial method)

Uninstall the Wscript.Shell object, under CMD or run directly: regsvr32/u%windir%\system32\wshom.ocx

Uninstall the FSO object, under CMD or run directly: regsvr32.exe/u%windir%\system32\scrrun.dll

Uninstall Stream object, under CMD or run directly: regsvr32/s/u "C:\Program Files\Common Files\system\ado\msado15.dll"

If you want to recover, just remove/u to re-register the above related ASP components such as: Regsvr32.exe%windir%\system32\scrrun.dll

④ about Webshell using Set domainobject = GetObject ("winnt://.") To obtain the server's process, service and user information such as prevention, you can workstation[service in the provision of network links and communications] that is, LanmanWorkstation service stopped and disabled. After this processing, Webshell shows that the process will be blank.

3 in accordance with the 1, 2 Methods of ASP class hazardous components processing, with Arjunolic ASP probe test, "Server CPU Details" and "Server operating system" is not found, the content is blank. Then use the ocean Test Wsript.shell to run the cmd command is also a hint that active cannot create an image. Everyone can no longer for ASP Trojan endanger the security of the server system and worry.

Of course, server security is far from these, here for you to introduce the only I in the handling of ASP Trojans, Webshell on some experience. In the next article, we will introduce how to simply prevent others from executing commands such as NET user on the server, preventing overflow attacks from being Cmdshell, and performing the simplest and most effective precautions for adding users, changing NTFS settings to terminal logins, and so on.