Troubleshooting of IIS cookies failure

A hardware fault occurred on the Web server. After the fault is fixed, the web site is migrated back to the server. Soon all the websites can be accessed normally. At this time, two websites are found. After opening the Website, you need to enter the user name and password to log on. However, after entering the user name and password, the login fails. When you log on to a website on the server, the system prompts that cookies are disabled, and you can log on to the website on the client. If you click OK, no message is displayed. After checking that no problem was found, I began to troubleshoot the problem in depth.

Let's talk about the server environment: Windows Server 2003 enterprise, IIS 6, and ASP. NET 2.0. When logging on to the server, the system prompts that Cookies cannot be written. Therefore, the browser permission is the first consideration. The security of IE is reduced to a minimum and cannot be logged on. You can determine that it is not a problem with Cookie settings. If you log on to the client, there is no prompt. AccordingProgramWhen the client is logged on, the browser does not write the authentication information into the cookie, resulting in a lack of authentication information after login and jumps back to the login page, it makes people feel that they do not respond after clicking login.

When I access the website using Firefox, I can log on successfully, but ie cannot log on. At this time, I initially determined that the failure was caused by the failure of IE to store cookies. After changing several computers, ie cannot log on. Therefore, it is suspected that the IIS settings make ie unable to store cookies and continue troubleshooting.

Setting the web site read and write permissions, disabling other software, stopping anti-virus software, rebuilding the web site, and restoring the IIS settings. All the methods have been used, and the fault still cannot be solved. You cannot find any information that affects Internet Explorer by searching for IIS settings on the Internet. Then open the site of the backup system, but you can log on normally. It is even more certain that the problem is IIS, but there is no clue about how to continue troubleshooting.

looking at the time on the server, it's over 2 o'clock in the morning, and it's a bit boring. Consider if you want to switch the system to the backup environment. Otherwise, it will be too late to switch again after a few minutes. However, we still hope to solve this fault and disable the backup system. After studying the table for a while, we found that the time was less than 1 point. I was puzzled. I thought I was wrong. I looked at my cell phone and found that it was less than 1. Then, let's look at the server. The time is more than two o'clock, so we can find that the BIOS time has been cleared because the server has changed hardware. Now, the time on the server is half a year later than the standard time. This completely understands the fault, because the failure time of the cookie setting for logon to the web site is half an hour, and the server time is so long, when the client logs on, the cookie will expire immediately, therefore, no matter how you wait, you cannot store cookies. After the server time is changed correctly, the login succeeds and the fault is solved smoothly.