Windows 98 Client Unable to Connect to Windows NT Share

• Microsoft Windows 98
• Microsoft Windows 98 Second Edition

SYMPTOMS

When you attempt to connect to a network share on a Microsoft Windows NT 4.0-based server using a Universal Naming Convention (UNC) path, you may experience one or more of the following symptoms:

• You may be unable to gain access to the network share.



• You may repeatedly receive authentication error messages.



• You may be unable to gain access to any other network shares that were working previously until you restart your computer.

CAUSE

This issue can occur because the server is notifying the Windows 98/95 client that the client can have x1FF pending SMB commands to the server, but the client stores this value in a character, producing 0xFF. This value is then incremented to account for the SMB just received, and the client now interprets that it can have 0 outstanding commands to the server so it cannot send any more SMBs.

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).

To work around this issue, use Registry Editor to delete the following value in the following registry key:

Value type: REG_DWORD
Value: x1FF

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanManServer\Parameters\MaxMpxCt

Additional query words:

Keywords : kbnetwork kbui win98 win98se
Version : WINDOWS:
Platform : WINDOWS
Issue type : kbprb