Article ID: 235703 - Last Review: November 1, 2006 - Revision: 1.5

NetWare Migration Tool May Not Migrate Long File Names with Correct Permissions

View products that this article applies to.
This article was previously published under Q235703
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986  (http://support.microsoft.com/kb/256986/EN-US/ ) Description of the Microsoft Windows Registry

On This Page

Expand all | Collapse all

SYMPTOMS

When you migrate a folder with a long folder name from NetWare to a Windows NT domain, the permissions for the folder and any files or subfolders it contains may not be migrated correctly.
Back to the top

CAUSE

This behavior is caused by the Nwconv.exe tool. This tool is not capable of enumerating rights for files or folders with long file names.
Back to the top

RESOLUTION

Windows NT Server or Workstation 4.0

To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual software update. For information on obtaining the latest service pack, please go to:
For information on obtaining the individual software update, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS (http://support.microsoft.com/default.aspx?scid=fh;en-us;cntactms)

Back to the top

Windows NT Server 4.0, Terminal Server Edition

To resolve this problem, obtain the latest service pack for Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
152734  (http://support.microsoft.com/kb/152734/EN-US/ ) How to Obtain the Latest Windows NT 4.0 Service Pack

Back to the top

STATUS

Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition.

This problem was first corrected in Windows NT Server 4.0 Service Pack 6 and Windows NT Server 4.0, Terminal Server Edition Service Pack 6.
Back to the top

MORE INFORMATION

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

For this fix to work, you must add a REG_DWORD value named DisableAltFileName with a data value of 0 to the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NwRdr\Parameters
Adding this value and setting it to 0 enables alternate file name support, which is necessary for this fix to work correctly.
Back to the top
APPLIES TO
  • Microsoft Windows NT Server 4.0, Terminal Server Edition
  • Microsoft Windows NT Server 4.0 Standard Edition
Back to the top
Keywords: 
kbhotfixserver kbqfe kbbug kbfix kbqfe KB235703
Back to the top
 

Get Help Now

Contact a support professional by E-mail, Online, or Phone

Article Translations