Mapped NetWare Drives and Windows 95 Persistent ConnectionsLast reviewed: December 11, 1997Article ID: Q125433 |
95
WINDOWS
kbnetwork kb3rdparty
The information in this article applies to:
SYMPTOMSAfter you install the Microsoft client for NetWare networks as the network services provider, drives that are mapped and printers that are captured in the AUTOEXEC.BAT file are no longer available.
CAUSEBefore you installed the Microsoft client for NetWare networks, the Novell NetWare version 3.x or 4.x real-mode drivers were being loaded. The Microsoft client for NetWare networks uses NWREDIR instead of NETX or VLM as the network redirector. NWREDIR is a 32-bit protected-mode redirector that is loaded when Windows 95 is loading. The AUTOEXEC.BAT file is processed before NWREDIR is loaded. Since the AUTOEXEC.BAT file is processed before network services are started, network drives cannot be mapped and network printers cannot be captured in the AUTOEXEC.BAT file.
RESOLUTION
Network DrivesInstead of mapping network drives in the AUTOEXEC.BAT file, reconnect each network drive in Windows 95 as a persistent connection. To do so, follow these steps:
Network PrintersInstead of capturing network printers in the AUTOEXEC.BAT file, follow these steps:
|
KBCategory: kbnetwork kb3rdparty kbhowto
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |