Article ID: 829011
Article Last Modified on 12/3/2007
APPLIES TO
- Microsoft Internet Information Services 6.0
SYMPTOMS
You are prompted by the browser for your user credentials if both of the following conditions are true:
- You are logged on locally to a computer that is running Microsoft Windows Server 2003.
- You open a browser to request a Common Gateway Interface (CGI) script from the Microsoft Internet Information Services (IIS) server on the local computer.
If you use the same credentials that you used to log on locally to the computer, the CGI script is returned successfully.
CAUSE
The browser prompts for new credentials because IIS incorrectly returns a 401 Access Denied Error to the browser during the original request.
WORKAROUND
To work around this problem, use the same credentials that you used when you originally logged on to the local computer.
RESOLUTION
Service pack information
To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
889100 How to obtain the latest service pack for Windows Server 2003
Hotfix information
Prerequisites
No prerequisites are required.
Restart requirement
You must restart your computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfix.
File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Date Time Version Size File name -------------------------------------------------------------- 10-Oct-2003 20:52 5.2.3790.91 129,536 Msv1_0.dll
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Server 2003 Service Pack 1.
Keywords: kbbug kbfix kbqfe kbwinserv2003sp1fix kbwinserv2003presp1fix kbhotfixserver KB829011