MAP Command in Nwscript.exe Does Not Work with ASCII Codes Above 127 in Network Provider Name

ID: Q244846

The information in this article applies to:

Microsoft Windows NT Server version 4.0 SP4, Terminal Server Edition

NOTE: The information in this article applies to the French version(s) of Windows NT Server version 4.0 SP4, Terminal Server Edition.

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

After you install French Terminal Server Service Pack 4 (SP4) and the Client for NetWare, the MAP command in the NetWare login script may not work. If you remove SP4, the MAP command works correctly again.

CAUSE

This problem has been encountered with the French edition of Terminal Server SP4, but may also occur with any language.

In the French version of Terminal Server SP4, the name of the network provider for NetWare is "Réseau Netware ou compatible." In SP3, it is "Reseau NetWare ou compatible" with no accented letter. The ASCII code for the accented "e" in SP4 is above 127, and therefore the OEM code (MS-DOS) and the ANSI code (Windows) are not the same.

During initialization, Nwscript.exe reads the name of the provider in the registry and converts the extended characters using the OEM code page instead of the ANSI code page. It then tries to map a drive, which is expecting an ANSI string and not an OEM string. This call does not succeed and generates a "The specified network provider name is invalid" (ERROR_BAD_PROVIDER) error message.

WORKAROUND

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 problem, replace all registry entries for the network provider to make sure extended characters (ASCII code above 127) are not used.

STATUS

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

Additional query words: gsnw

Keywords : kbenv kberrmsg
Version : winnt:4.0 SP4
Platform : winnt
Issue type : kbprb