Windows 95/98 Clients Hang with SQL 7.0 and Dfs Installed on Server

ID: Q234647

The information in this article applies to:
  • Microsoft Windows 98
  • Microsoft Windows 95
  • Microsoft Windows NT Server version 4.0
  • Microsoft SQL Server version 7.0
IMPORTANT: This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to do this, view the "Restoring the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help topic in Regedt32.exe.

SYMPTOMS

Windows 95 clients using Microsoft distributed file system (Dfs) or Windows 98 clients may stop responding (hang) in any of the following situations:

  • Windows 95 Dfs clients or Windows 98 clients hang while logging on to a Windows NT 4.0 domain controller that has a Dfs root share and SQL 7.0 installed.


  • After successfully logging on to a domain, Windows 95 Dfs clients and Windows 98 clients hang when trying to connect to or browse a Windows NT 4.0 domain controller (or member server) that has a Dfs root share and SQL 7.0 installed.


  • Windows 95 Dfs clients or Windows 98 clients hang while logging on to a Windows NT 4.0 domain controller, if the user has a logon script that maps a drive to a Windows NT 4.0 domain controller (or member server) that has a Dfs root share and SQL 7.0 installed.


When a user is trying to log on, Windows 98-based computers may display Creating User Profiles and Loading System Policies dialog boxes, and then hang. If you press CTRL+ALT+DELETE, you see that Mprexe.exe is not responding.


CAUSE

SQL 7.0 installs the following key on the SQL server, which Windows 98 clients and Windows 95 Dfs clients cannot process correctly:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanManServer\Parameters\MaxMpxCt
This key has a REG_DWORD value of x1FF.


RESOLUTION

WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, view the "Changing Keys and Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it. If you are running Windows NT, you should also update your Emergency Repair Disk (ERD).

  1. Start Registry Editor (Regedt32.exe) on the Windows NT 4.0 server that has the Dfs roots hare and SQL 7.0 installed.


  2. Locate the REG_DWORD x1FF value under the following key in the registry:


    3. HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanManServer\Parameters\MaxMpxCt
  3. On the Edit menu, click DWORD, type 1FE, click Hex, and then click OK.


  4. Quit Registry Editor.



STATUS

Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article.


MORE INFORMATION

The problem does not affect Windows NT Workstation or Windows 95 clients that are not Dfs-aware.

If you click Cancel at the domain logon prompt, you can log on locally.

Other possible solutions include:

  • Move the Dfs root share to a member server or domain controller that does not have SQL 7.0 installed.


  • Install the NWLINK protocol on all servers and clients.


  • If you stop the Netlogon service on the domain controller that is running Dfs and SQL 7.0, you should be able to log on to the domain (provided that there are other domain controllers that can be reached by the client) but unable to browse the domain controller running Dfs and SQL 7.0.


  • Apply SQL Server 7.0 Service Pack 1 (SP1).


This problem has also been observed in environments without SQL or Dfs; the problem was resolved using the solution listed above. Mprexe.exe may not be responding for many underlying reasons. This article addresses one possible solution.

Additional query words: freezes service rootshare stops

Keywords : kbenv ntdomain
Version : WINDOWS:95; winnt:4.0,7.0
Platform : WINDOWS winnt
Issue type : kbprb


Last Reviewed: September 20, 1999
© 2000 Microsoft Corporation. All rights reserved. Terms of Use.