The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

Knowledge Base

Connecting to SMB share on a Windows 2000-based computer or a Windows Server 2003-based computer may not work with an alias name

Article ID: 281308

Article Last Modified on 2/21/2007

APPLIES TO

Microsoft Windows 2000 Server
Microsoft Windows 2000 Advanced Server
Microsoft Windows 2000 Professional Edition
Microsoft Windows Server 2003, Standard Edition (32-bit x86)
Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)

This article was previously published under Q281308

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 Description of the Microsoft Windows Registry

SYMPTOMS

When a client computer connects to a Microsoft Windows 2000-based computer or a Microsoft Windows Server 2003-based computer by using an alias name, the client may receive the following error message:

System error 52 has occurred.
A duplicate name exists on the network.

CAUSE

This problem can occur when you try to connect to the server by using a CNAME alias that is created in the DNS zone. For example, this problem may occur with a command similar to the following sample command

net view \\alias.domain name.com

where alias is a CNAME record that is created for the server in the domain name.com zone. The server is not "listening" on the alias, and therefore is not accepting connections to that name.

RESOLUTION

Windows 2000 Server

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.
To resolve this problem, obtain and install the latest Windows 2000 service pack, and then edit the registry.To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

260910 How to Obtain the Latest Windows 2000 Service Pack

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

   Date         Time   Version        Size       File name
   ----------------------------------------------------------
   02-Jul-2001  22:52  5.0.2195.3804  1,685,632  Ntkrnlmp.exe
   02-Jul-2001  22:53  5.0.2195.3804  1,685,312  Ntkrnlpa.exe
   02-Jul-2001  22:53  5.0.2195.3804  1,705,984  Ntkrpamp.exe
   02-Jul-2001  22:51  5.0.2195.3804  1,663,424  Ntoskrnl.exe
   02-Jul-2001  23:44  5.0.2195.3805    237,072  Srv.sys
   02-Jul-2001  23:53  5.0.2195.3805     73,488  Srvsvc.dll

Additionally, to resolve this problemin Windows 2000 Server you must complete all of the following steps:

Create the CNAME record for the file server on the appropriate DNS server, if the CNAME record is not already present.
Apply the hotfix to the computer for which the CNAME record was created, not the DNS server. (Unless the DNS server and file server in question is the same computer, and then all of the changes is applied is to that server.) This hotfix affects the LAN Manager Server Service and does not affect DNS functionality.
Apply the following registry change to the file server to which you installed the hotfix. To do so:
1. Start Registry Editor (Regedt32.exe).
2. Locate and click the following key in the registry:
  
  HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters
3. On the Edit menu, click Add Value, and then add the following registry value:
  
  Value name: DisableStrictNameChecking
  Data type: REG_DWORD
  Radix: Decimal
  Value: 1
4. Quit Registry Editor.
Restart your computer.

Windows Server 2003

To resolve this problem in Windows Server 2003, complete the following steps:

Create the CNAME record for the file server on the appropriate DNS server, if the CNAME record is not already present.
Apply the following registry change to the file server. To do so, follow these steps:
1. Start Registry Editor (Regedt32.exe).
2. Locate and click the following key in the registry:
  
  HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters
3. On the Edit menu, click Add Value, and then add the following registry value:
  
  Value name: DisableStrictNameChecking
  Data type: REG_DWORD
  Radix: Decimal
  Value: 1
4. Quit Registry Editor.
Restart your computer.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows 2000 Service Pack 3.

MORE INFORMATION

For additional information about how to obtain a hotfix for Windows 2000 Datacenter Server, click the article number below to view the article in the Microsoft Knowledge Base:

265173 The Datacenter Program and Windows 2000 Datacenter Server Product

For additional information about how to install multiple hotfixes with only one reboot, click the article number below to view the article in the Microsoft Knowledge Base:

296861 Use QChain.exe to Install Multiple Hotfixes with One Reboot

This hotfix corrects the problem that is described in the following article in the Microsoft Knowledge Base: For additional information about how to install Windows 2000 and Windows 2000 hotfixes at the same time, click the article number below to view the article in the Microsoft Knowledge Base:

249149 Installing Microsoft Windows 2000 and Windows 2000 Hotfixes

Additional query words: kbBaseOS

Keywords: kbhotfixserver kbqfe kbbug kbfix kboswin2000fix kbwin2000presp3fix kbwin2000sp3fix KB281308

Microsoft KB Archive/281308

Contents