Article ID: 308337 - Last Review: February 20, 2007 - Revision: 9.10

"System error 85 has occurred. The local device name is already in use" error message

Hotfix download is availableHotfix Download Available
View and request hotfix downloads
View products that this article applies to.
System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.
This article was previously published under Q308337
Notice
This article applies to Windows 2000. Support for Windows 2000 ends on July 13, 2010. The Windows 2000 End-of-Support Solution Center (http://support.microsoft.com/?scid=http%3a%2f%2fsupport.microsoft.com%2fwin2000) is a starting point for planning your migration strategy from Windows 2000. For more information see the Microsoft Support Lifecycle Policy (http://support.microsoft.com/lifecycle/) .

On This Page

Expand all | Collapse all

SYMPTOMS

When you try to connect a drive that was previously connected to a Distributed File System (DFS) resource, you may receive the following error message:
System error 85 has occurred. The local device name is already in use.
This error message persists for the particular drive letter in that particular Terminal Services session. The same drive letter for other Terminal Services sessions may work as expected. A different drive letter that is not typically used also works as expected. The only way to correct the issue is to restart the Terminal Services-based system.
Back to the top

RESOLUTION

Service pack information

To resolve this problem, obtain the latest service pack for Microsoft Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
260910  (http://support.microsoft.com/kb/260910/ ) How to obtain the latest Windows 2000 service pack
Back to the top

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Microsoft Windows 2000 Service Pack 3
   Date         Time   Version            Size    File name
   --------------------------------------------------------------
   27-Sep-2002  00:41  5.0.2195.6069     124,176  Adsldp.dll       
   27-Sep-2002  00:41  5.0.2195.5781     131,344  Adsldpc.dll      
   27-Sep-2002  00:41  5.0.2195.5781      62,736  Adsmsext.dll     
   27-Sep-2002  00:41  5.0.2195.6052     358,160  Advapi32.dll     
   27-Sep-2002  00:41  5.0.2195.5265      42,256  Basesrv.dll      
   27-Sep-2002  00:41  5.0.2195.6058      49,424  Browser.dll      
   27-Sep-2002  00:41  5.0.2195.6012     135,952  Dnsapi.dll       
   27-Sep-2002  00:41  5.0.2195.6012      96,016  Dnsrslvr.dll     
   27-Sep-2002  00:41  5.0.2195.5722      45,328  Eventlog.dll     
   27-Sep-2002  00:41  5.0.2195.5907     222,992  Gdi32.dll        
   27-Sep-2002  00:41  5.0.2195.6059     146,704  Kdcsvc.dll       
   06-Sep-2002  02:18  5.0.2195.6048     200,976  Kerberos.dll     
   27-Sep-2002  00:41  5.0.2195.6011     708,880  Kernel32.dll     
   21-Aug-2002  17:27  5.0.2195.6023      71,248  Ksecdd.sys
   26-Sep-2002  03:01  5.0.2195.6072     507,664  Lsasrv.dll       
   26-Sep-2002  03:01  5.0.2195.6072      33,552  Lsass.exe        
   27-Sep-2002  00:41  5.0.2195.4733     332,560  Msgina.dll       
   27-Aug-2002  23:53  5.0.2195.6034     108,816  Msv1_0.dll       
   25-Jun-2002  20:15  5.0.2195.5913      87,824  Mup.sys
   27-Sep-2002  00:41  5.0.2195.5979     307,472  Netapi32.dll     
   27-Sep-2002  00:41  5.0.2195.5966     360,720  Netlogon.dll     
   27-Sep-2002  00:41  5.0.2195.6048     918,800  Ntdsa.dll        
   27-Sep-2002  00:41  5.0.2195.6025     389,392  Samsrv.dll       
   27-Sep-2002  00:41  5.0.2195.5951     129,296  Scecli.dll       
   27-Sep-2002  00:41  5.0.2195.5951     302,864  Scesrv.dll       
   10-Sep-2002  16:50  5.0.2195.6053     123,392  Sp3res.dll       
   13-Jun-2001  06:05  5.0.2195.3727       3,856  Svcpack1.dll     
   27-Sep-2002  00:41  5.0.2195.6063     380,176  User32.dll       
   27-Sep-2002  00:41  5.0.2195.5968     369,936  Userenv.dll      
   27-Sep-2002  00:41  5.0.2195.5859      48,912  W32time.dll      
   04-Jun-2002  22:32  5.0.2195.5859      57,104  W32tm.exe        
   25-Sep-2002  19:04  5.0.2195.6070   1,642,512  Win32k.sys
   12-Sep-2002  20:50  5.0.2195.6056     179,472  Winlogon.exe     
   27-Sep-2002  00:41  5.0.2195.5935     243,472  Winsrv.dll       
   27-Sep-2002  00:41  5.0.2195.6052     126,224  Wldap32.dll      
   26-Sep-2002  03:01  5.0.2195.6072     507,664  Lsasrv.dll       
   27-Sep-2002  00:41  5.0.2195.6011     708,880  Kernel32.dll     
   27-Sep-2002  00:41  5.0.2195.6070   1,642,512  Win32k.sys
   27-Sep-2002  00:41  5.0.2195.5935     243,472  Winsrv.dll
Microsoft Windows 2000 Service Pack 4
   Date         Time    Version         Size     File name
   -------------------------------------------------------
   28-May-2003  18:48   5.0.2195.6749   88,624   Mup.sys
Back to the top

Windows registry changes

The hotfix installer will create the following Windows registry entry. If a newer version of the Mup.sys file is installed from a different hotfix package, you must manually change this entry.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\mup

Entry: EnableDeviceNameCreateRetry
Type: DWORD
Value: 1 (This value sets the system to automatically recover when the problem that is described in this article occurs.)
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756  (http://support.microsoft.com/kb/322756/ ) How to back up and restore the registry in Windows
Follow these steps, and then quit Registry Editor:
  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate and then click the following key in the registry:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\mup\EnableDeviceNameCreateRetry
  3. On the Edit menu, click Modify.
  4. Type 1, and then press ENTER.
Back to the top

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Back to the top

MORE INFORMATION

For additional information about how to obtain a hotfix for Windows 2000 Datacenter Server, click the following article number to view the article in the Microsoft Knowledge Base:
265173  (http://support.microsoft.com/kb/265173/ ) The Datacenter Program and Windows 2000 Datacenter Server product
For additional information about how to install multiple hotfixes with only one restart, click the following article number to view the article in the Microsoft Knowledge Base:
296861  (http://support.microsoft.com/kb/296861/ ) How to install multiple Windows updates or hotfixes with only one reboot
For additional information about how to install Windows 2000 and Windows 2000 hotfixes at the same time, click the following article number to view the article in the Microsoft Knowledge Base:
249149  (http://support.microsoft.com/kb/249149/ ) Installing Microsoft Windows 2000 and Windows 2000 hotfixes
Back to the top
APPLIES TO
  • Microsoft Windows 2000 Server
  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Professional Edition
Back to the top
Keywords: 
kbautohotfix kbhotfixserver kbqfe kbnetwork kbwin2ksp4fix kbbug kbenv kberrmsg kbfix KB308337
Back to the top