Article ID: 181072
Article Last Modified on 9/23/2005
APPLIES TO
- Microsoft Internet Explorer 3.02
- Microsoft Internet Explorer 3.02
This article was previously published under Q181072
SYMPTOMS
If you configure a Microsoft Proxy server to automatically configure Web
browsers using a script and the automatic proxy configuration script
resides on a server with NTLM authentication enabled, the script may not
work. If the script is moved to a server configured for anonymous access,
it works correctly.
In a proxy array, this may force clients to use a proxy that is not local.
If there is only one proxy server on your network, clients may not be able
to connect to resources, receiving the following error message:
A connection with the server could not be established
RESOLUTION
This issue is resolved by installing the following updated files for
Internet Explorer:
Wininet.dll version 4.70.1326 (dated 11/3/97) and later (NFU [non-file
upload] version)
Wininet.dll version 4.70.1448 (dated 11/25/97) and later (FU [file
upload] version)
STATUS
Microsoft has confirmed this to be a problem in Microsoft Internet
Explorer version 3.02 for Windows 95 and Windows NT 4.0. An update to
address this problem is now available, but is not fully regression
tested and should be applied only to computers experiencing this specific
problem. Unless you are severely impacted by this specific problem,
Microsoft does not recommend implementing this update at this time.
Contact Microsoft Technical Support for additional information about the
availability of this update.
Additional query words: autoproxy auto
Keywords: kberrmsg kbqfe kbenv kbprb kbhotfixserver KB181072