Proxy client conflict with third-party providers causes problems (303757)

SYMPTOMS

The New.net eClient and similar programs try to extend the DNS name-resolution mechanism to allow third parties to create their own root domain names (such as .shop, .free, and so on) by installing as layered service providers above Winsock. After installation completes, these programs prompt you to restart your computer.

The ISA Server Firewall client is also installed as a layered service provider (LSP), and needs to maintain its installation order and position. If the ISA Server Firewall client is installed on the computer, the installation of then New.net eClient may cause problems for the ISA Server Firewall client, and may cause your computer to have various problems after the suggested reboot, including after installing, reinstalling, or uninstalling the ISA Server Firewall client. Some of the problems that are common to Microsoft Windows 98/95, Microsoft Windows NT, Microsoft Windows 2000, Microsoft Windows XP include:

The Lsass.exe tool reports an Error 10091 in the event viewer (the event number and description are not available).
You may receive a STOP error message on a blue screen.
Your operating system may start very slowly.
You may lose all network connectivity.
Programs may be unable to connect through the firewall.
You may experience a stack overflow, where the Mstask.exe and Inetinfo.exe tools stop responding (hang), the Phone Dialer tool may be unavailable, and the Event Viewer may contain a lot of errors. This appears as an exception 0xC00000FD on many programs, and may cause your computer to shut down if this happens in a system service. You may see an application error or an access violation error (on computers that are equipped with debuggers) or a Dr. Watson error. The difference is that the access violation error is an exception code of 0xC0000005, and the stack overflow is 0xC00000FD.
If you use the Chkwsp32.exe tool to troubleshoot this problem, you may receive a report that the WSP client is not the first LSP.

CAUSE

This problem can be caused by several conditions:

An incompatibility exists between the proxy (WSP Client) client files and another third-party provider.
If the third-party provider is installed after the proxy client and it is installed with a higher priority than the proxy client, this can causes an infinite recursion between the two.

This problem still occurs if the proxy client is installed after the third-party client/provider if the next provider for UDP exists in the same DLL as the next provider for TCP. The problem occurs because the proxy client copies the ProtocolChain member from the last TCP/IP provider it finds on the computer. This causes the proxy provider to be considered a "layered" provider instead of a base provider if it finds the New.net eClient instead of MSAFD.

The New.net provider may not start when it is called from the proxy client. Chkwsp32 indicates that ISA is not the first LSP, and the program does not connect through the proxy. Note that you can use the Sporder.exe tool to see the chainlen parameter.

RESOLUTION

Important The following hotfix should be applied to the proxy server, and you should run the client installation again. This is the recommended way to update the client configuration and the affected files. The fixed version of the client can work correctly with another service provider that is installed on your computer.

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix should have the following file attributes or later:

   File name       Platform
   ------------------------
   Stpext32.dll    Intel
   Wspwsp.dll      Intel

This problem occurred with version 2.98 of the New.net Client. (Version 2.98 was released June 19, 2001.) The problem was created by the Microsoft Proxy client and was corrected by Microsoft in this hotfix. However, New.net also published a workaround in New.net Client version 3.36. The New.net workaround prevents the problem on any systems that have not been updated with the Microsoft hotfix. (New.net Client version 3.36 was released December 5, 2001.)

Note You may be able to recover a damaged computer if you uninstall the appropriate program or programs. If your computer does not start normally, start it in "Safe mode without networking" mode. If you cannot uninstall the New.net eClient by using the Add/Remove Programs tool in Control Panel, visit the following New.Net Web site for information about how to manually uninstall the client:

http://www.newdotnet.com

Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.

Proxy client conflict with third-party providers causes problems (303757)

SYMPTOMS

CAUSE

RESOLUTION

STATUS

MORE INFORMATION