Microsoft Knowledge Base Email Alertz

After 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.

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 125433 - Last Review: January 19, 2007 - Revision: 1.3

Mapped NetWare Drives and Windows Persistent Connections

System TipThis article applies to a different version of Windows than the one you are using. Content in this article may not be relevant to you. Visit the Windows Vista Solution Center
This article was previously published under Q125433

On This Page

SYMPTOMS

After 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.

CAUSE

Before 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 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 Drives

Instead of mapping network drives in the AUTOEXEC.BAT file, reconnect each network drive in Windows 95/98 as a persistent connection. To do so, follow these steps:
  1. Start Windows Explorer.
  2. On the Tools menu, click Map Network Drive.
  3. In the Drive box, click the drive letter you want for the connection.
  4. In the Path box, enter the path for the network connection.
  5. Click the Reconnect At Logon check box to select it.
  6. Click the OK button.
  7. Repeat steps 2-6 for each network drive.
  8. Remove the Map commands from the AUTOEXEC.BAT file. The network connections will be available each time you start Windows.

Network Printers

Instead of capturing network printers in the AUTOEXEC.BAT file, follow these steps:
  1. Click the Start button, point to Settings, and then click Printers.
  2. Double-click the Add Printer icon to start the Add Printer Wizard.
  3. When you are prompted "How is this printer attached to your computer?" click the Network Printer option button, and then click the Next button.
  4. In the Network Path Or Queue Name box, enter the correct path or queue name for the network printer. If you print from MS-DOS-based applications as well as Windows-based applications, click the Yes option button underneath the "Do you print from MS-DOS-based programs?" prompt. Click Next.
  5. Click Next.
  6. Click the Finish button.
  7. Repeat steps 2-6 for each network printer.
  8. Remove the capture commands from the AUTOEXEC.BAT file. The network printer connections will be available each time you start Windows.

APPLIES TO
  • Microsoft Windows Millennium Edition
  • Microsoft Windows 98 Second Edition
  • Microsoft Windows 98 Standard Edition
  • Microsoft Windows 95
Keywords: 
kb3rdparty kb3rdpartynetclient kbnetwork kbprb KB125433
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate