NTLM Enabled on IIS 1.0 Creates Problems with Run-Time Bots
Article ID: 171680
Article Last Modified on 6/23/2005
APPLIES TO
- Microsoft Internet Information Server 1.0
- Microsoft FrontPage 1.1 Standard Edition
- Microsoft Windows NT Server 3.51
This article was previously published under Q171680
We strongly recommend that all users upgrade to Microsoft Internet Information Services (IIS) version 6.0 running on Microsoft Windows Server 2003. IIS 6.0 significantly increases Web infrastructure security. For more information about IIS security-related topics, visit the following Microsoft Web site:
SYMPTOMS
When you run Microsoft FrontPage for Windows version 1.1 on Windows NT
Server version 3.51 with Internet Information Server 1.0 installed, you
will not be able to use NTLM Authentication, and you may receive an error
message similar to the following:
HTTP/1.0 500 Server Error
(The type of the token is inappropriate for its attempted use.)
CAUSE
Even though NTLM cannot be used to access CGI scripts on Windows NT Server
3.51, IIS 1.0 tells the browser that NTLM is okay. The browser, not being
able to distinguish between a CGI script or an ISAPI script, unsuccessfully
tries to use NTLM, and the result is the preceding HTTP error message.
RESOLUTION
To avoid the problem, use any of the following workarounds:
Disable NTLM Authentication for the server.
-or-
Turn Allow Anonymous back on.
-or-
Upgrade the server to Microsoft Windows NT 4.0 and Internet Information
Server 2.0, which is capable of handling NTLM access to CGI scripts.
Additional query words: fpiis
Keywords: kbbug kbenv kbhowto kbusage KB171680