Introducing your own hard-built websites that cannot be visited, and it is indeed frustrating. But don't worry, this article will guide you to find the root of the fault. Most Operation Failed Factors The reason for the failure of the operation is not more than the following: network connection failure, firewall settings, IIS permission issues. In general, network failure is easy to find. For example, if your network cannot transmit any data, then the problem is very likely to be on the network hardware. If the local network is normal, it cannot access your website from the outside, then the picture port 80 is not banned by the firewall, as long as it makes a simple port scan (port sniffing) is clear. I intend to re-write a complete trouble-of-time diagnosis guide according to the response of this article. However, this paper only discusses the failure of IIS due to permissions issues. Establishing a diagnosis of security log IIS connection failure, the first step is a clear understanding of the phenomenon of the fault. At this point you often need to view your event log. However, you have to do some settings first, otherwise the information in the event log is useless. Since discussing the IIS operational fault related to permissions, then we must use the security log. So first you have to reconfigure the security log: tell IIS what we have to record, then stop IIS, then empty the security log, and finally restart IIS service. Maybe you will be strange: Why should I stop IIS? Because IIS sometimes writes the security log to Cache (cache). If you don't restart IIS, then after you empty the log, the records in the cache will be written immediately. Obviously, this information will be mistaken to be currently recorded and introduce you to astray. Therefore, I strongly recommend stop and restart IIS services. Now set IIS. First, enter Program | Administrative Tools | Computer Management. Then, find the Services and Applications | Internet Information Services. Expand the Internet Information Services item Display site. Right-click on the problematic website name, select the Properties to open the property page, now the web site item in the Properties page, select the Enable logging item to open the log. At this point, you will see a list allows you to choose the log file format. I recommend using the W3C Extended format, point the Properties button, select the Extended Logging Properties (Extended Log Properties page). By default, General Properties in the Properties page has been selected. Here you can set a new record file here, this value does not matter, choose it yourself. Extended attribute pages is more important. Here you can choose which information needs to be saved to the log. You can choose freely, but at least you should include the following items: Date, Time (Time), Client IP Address, User Name, Method (Method), HTTP STATUS (HTTP Status) And Win32 STATUS (Win32 State). After the choice is completed, click OK, then click OK, you can return to the computer management interface. Since we have already configured the website record option, let's empty the Cache (Cache) and logging. Step 1: Stop all IIS services.
The method is: enter the DOS command prompt mode (Type the command in the DOS prompt window: Net Stop iisadmin / y requires this command to stop all IIS services. After completing, leave the DOS prompt window, enter the Programs | Administrative Tools | Event Viewer. Right-click on Security Log, select Clear All Events (Clear all events). Ok, now you have already emptied Cache and security logs, you can restart IIS. Back to the DOS prompt window, type 4 lines: Net Start W3SVC Net Start Msftpsvc Net Start NNTPSVC Net Start SMTPSVC pays attention to everyone needs everyone needs. For example, for example, if you don't run an FTP service, you don't have to type commands related to FTP (Translator Note: W3SVC - Web, MSFTPSVC - FTP, NNTPSVC - NNTP, SMTPSVC - SMTP). Check if the security log is now setting up a security log, you can create a log entry. Try to visit the failed website. I suggest that if possible, try to access it from many people's machines from the interior and outside of the company. Because this can be obtained by many useful logging, the root cause of the problem can be greatly helped by comparative analysis of them. Perhaps you will find that only from the company can access, but from the outside; or only the authorized user can access, and anonymous users can not. and many more. When you organize the security log project, I recommend you to see the error code of 401 and 403. There are many errors that are 401 and 403. But once you have exact code, you get an extremely important clue. Many 401 and 403 errors are listed below: 401; 1 illegal operation: Login failed 401; 2 illegal operation: Server setting error 401; 3 illegal operation: Using Control List (ACL) Item 401; 4 illegal Operation: IIS filter prevents access 401; 5 illegal operation: ISAPI or CGI application 403; 1 Operation prohibition: No permission 403; 2 Operation prohibition: No read permission 403; 3 Operation prohibition: No write permission 403; 4 Operation prohibition: SSL 403; 5 Operation prohibition: 128-bit SSL 403; 6 Operation prohibition: IP address is rejected 403; 7 Operation prohibition: Require customer certificate 403; 8 operation prohibition: Refuse to access site 403; 9 operation prohibited : Currently connected users 403; 10 Operation prohibition: Setup error 403; 11 Operation prohibition: 403; 12 Operation prohibition: Requireable customer certificate 403; 13 Operation prohibition: Customer certificate has been invisible 403; 14 operation prohibited : Rejecting column catalog 403; 15 Operation prohibition: More than license customer number 403; 16 operation prohibition: customer access certificate illegal or not authenticated 403; 17 Operation prohibition: customer access certificate expire or have not succeeded, from you The 401 and 403 errors are found in the security log, and the list of the above list may be helpful? If you still haven't found a reason, please see the next section. There will be special permission issues and solutions.
