Error Mapping or Reconnecting Network Resource

 Last reviewed: December 13, 1995
Article ID: Q130077
The information in this article applies to:
  • Microsoft Windows 95

SYMPTOMS

You may receive one of the following error messages when Windows 95 is trying to reconnect a mapped network drive or when you try to map a drive to a network resource in Windows Explorer

  • The following error occurred while reconnecting X: to \\<server>\<share> Invalid local device. Do you want to restore this connection the next time you log on?
  • The following error occurred while reconnecting X: to \\server\sys Permanent connection not available Do you want to restore this connection the next time you log on?
  • The following error occurred while trying to connect X: to \\<server>\ <share> Invalid local device
  • The following error occurred while trying to connect X: to \\server\sys Device not connected.

where \\<server>\<share> is a shared Microsoft resource and \\server\sys is a shared resource on a NetWare server.

CAUSE

This error can occur if the drive letter you are trying to map is higher than the last drive available to Windows 95. The last drive available to Windows 95 is defined in the LASTDRIVE= statement in the CONFIG.SYS file. For example, this error occurs if you try to map drive Q, but the CONFIG.SYS file contains the statement LASTDRIVE=P.

RESOLUTION

To work around this problem, use any one of the following methods:

  • Remove the LASTDRIVE= statement from the CONFIG.SYS file.
  • Modify the LASTDRIVE= statement in the CONFIG.SYS file so that the last drive available to Windows 95 is greater than the last drive letter you want to map.
  • Map a drive letter that is less than the last drive available to Windows 95 instead of the drive letter you are trying to map. For example, if the last drive letter available to Windows 95 is drive P, map drive O to the network resource.

STATUS

Microsoft is researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

When you use the protected-mode network clients included with Windows 95 (VREDIR.VXD and NWREDIR.VXD), avoid using the LASTDRIVE= statement in the CONFIG.SYS file. If you use a LASTDRIVE= statement, avoid mapping a drive letter that is greater than the drive letter in the LASTDRIVE= statement.

KBCategory: kbnetwork kberrmsg kbenv kbprb
KBSubcategory: wpp95 win95 msnets
Additional reference words: 95

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: December 13, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.