Chapter 17 - Windows 98 on Third-Party Networks

Article
02/20/2014

Archived content. No warranty is made as to technical accuracy. Content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.

This chapter describes how to install and configure Microsoft Windows 98 on Novell® NetWare® and other third-party networks. It discusses the issues you should consider before configuring Windows 98 for third-party networks, including issues to consider when installing real-mode clients. For NetWare networks, it also explains how to choose between Microsoft-supplied and NetWare-supplied networks.

Overview of Windows 98 on Third-Party Networks

Networking support is built into Windows 98. The Windows 98 network architecture includes a network provider interface, which defines a set of APIs that Windows 98 uses to access the network for actions, such as connecting to, logging on to, and browsing servers. Microsoft has made this set of APIs widely available to network vendors so that they can develop new protected-mode network providers (drivers for network clients) that are compatible with Windows 98.

Windows 98 includes two protected-mode network clients (Client for Microsoft Networks and Client for NetWare Networks). Windows 98 also includes built-in support for several 16-bit, real-mode network clients; however, in most cases, you also need to use supporting software from the appropriate network vendors. Additionally, the Windows 98 network provider interface enables you to use third-party network clients. Furthermore, because the Windows 98 network architecture supports multiple network providers, you can use multiple network clients on one computer. You can use one 16-bit, real-mode client, and as many 32-bit, protected-mode network clients as you need. Contact your network vendor to obtain a 32-bit, protected-mode network client for your network.

This chapter discusses the following networking software:

Artisoft LANtastic version 7.0 (client and server components)
Banyan Enterprise Client version 7.32 and later
Banyan VINES client version 7.1 and later
DIGITAL PATHWORKS 32 client
IBM Networks Client for Windows 95
Client for NetWare Networks
NETX, the real-mode Novell NetWare workstation shell client for servers running NetWare version 3.x and later
VLM (Virtual Loadable Module), the real-mode workstation shell client for servers running NetWare version 4.x.
Novell Client for Windows 95/98 (also known as Client 32)
Solstice NFS Client version 3.1 and later

Note See the Network.txt file for a list of clients and servers that Windows 98 does not support.

For information about how to install third-party networks using custom setup scripts, see Chapter 3, "Custom Installations."

Overview of Windows 98 on NetWare Networks

With Windows 98, you can use the built-in features and commands to perform most common network operation and administration tasks on NetWare networks. The following networking features are available in Windows 98 to support computers running on NetWare networks:

Automatic setup and customization of Windows 98 on NetWare workstations**,** as described in Chapter 3, "Custom Installations," and Chapter 4, "Automated Installations."
System policies to enforce desktop and system settings for individual or multiple computers, as described in Chapter 8, "System Policies."
Integration of network resources in Network Neighborhood, and common controls, such as the Open or Save As dialog boxes, as described in Chapter 18, "Logon, Browsing, and Resource Sharing."
Password caching for network connections and user-level security with pass-through validation to NetWare servers, as described in Chapter 9, "Security."
Printing to NetWare print queues using Point and Print. For information, see Chapter 11, "Printing, Imaging, and Fonts." You can use several different NetWare clients, and different features are available depending on the client you choose.

Additionally, the Windows 98 Resource Kit includes an agent for simple network management protocol (SNMP), as described in Chapter 23, "System and Remote Administration Tools."

Planning for Windows 98 on NetWare Networks

When planning for Windows 98 on NetWare networks, you will need to consider the following issues:

The network client you will use.
The protocols you will use.

Choosing the Network Client

Windows 98 runs on workstations that can connect to Novell NetWare versions 3.x, and 4.x servers. You can use several different networking clients:

The 32-bit, protected-mode Microsoft Client for NetWare Networks.

If you use Microsoft Client for NetWare Networks, you can also use the optional Microsoft Service for NetWare Directory Services. This service provides tight integration with Novell Directory Services (NDS).
Novell Client for Windows 95/98 (also known as Client 32), a 32-bit, protected-mode client.
NETX, the real-mode networking client for servers running NetWare version 3.x and later
VLM, the real-mode networking client for servers running NetWare version 4.x.

Note Microsoft does not support connecting to servers running versions of NetWare earlier than NetWare 3.11. Microsoft also does not support using Novell Client for DOS/Windows 3.x. When using Novell Client for Windows 95/98, Microsoft recommends using version 2.2 or later with updated versions of Vmlid.nlm and Odiload.vxd, which you obtain from Novell.

You should use a protected-mode client rather than a real-mode client. Protected-mode clients offer the following benefits:

Provide easy installation and configuration using built-in Windows 98 tools.
Use no real-mode memory.
Provide faster data I/O across the network than do real-mode clients.
Offer greater stability than do real-mode clients.
Enable you to run additional protected-mode clients.

The following sections describe the issues you will need to consider before choosing each client.

Note For computers that use Microsoft Client for NetWare Networks, all the files required for networking are included with Windows 98. However, you will need some Novell-supplied files in order to run NetWare utilities. Additionally, Windows 98 does not include any Novell-supplied components required for Novell clients. For information about obtaining updates for Novell-supplied files, see "Obtaining Current Novell-Supplied Files" later in this chapter.

For information about configuring Novell-supplied components and running NetWare utilities, consult your Novell documentation. For information about licensing requirements, see your Novell NetWare license agreement.

Issues with MS-supplied NetWare Clients

You might choose not to use Client for NetWare Networks in the following cases:

If you want to use Novell-supplied utilities, such as Novell Application Launcher, Novell IP Gateway, Remote Access Dialer, and NetWare Distributed Print Services, you should use Novell Client for Windows 95/98.
If you want to take advantage of NetWare NCP packet signature for enhanced protection of servers and client computers using NCP, you must use Novell Client for Windows 95/98 or VLM, because Client for NetWare Networks does not support this feature.
If your site needs to use NetWare Internet Protocol (IP), you should use Novell Client for Windows 95/98, the NETX client, or the VLM client. Client for NetWare Networks does not support NetWare IP, and you cannot use Microsoft TCP/IP to communicate with NetWare servers using NetWare IP.
If you use 3270 emulators that rely on MS-DOS-helper terminate-and-stay-resident (TSR) programs or need 3270 emulation for applications in MS-DOS sessions, you should use NETX or VLM.
If you are using custom VLM components, such as PNW, you should use VLM.
If you have problems with programs that make proprietary or undocumented API calls, you should use a Novell-supplied client.

Issues with Novell-supplied NetWare Clients

If you are using a Novell-supplied NetWare client, you should use Novell Client for Windows 95/98. It is a 32-bit, protected-mode client that provides access to Novell Directory Services (NDS) and newer Novell-supplied utilities.

You might choose not to use Novell Client for Windows 95/98 and instead use Client for NetWare Networks in the following cases:

If you have problems with Setup using MsBatch.
If you want to take advantage of Windows 98 peer resource sharing without running another network client.

Choosing Protocols on NetWare Networks

This section discusses issues you should consider when using the following protocols:

Microsoft's 32-bit, protected-mode IPX/SPX-compatible protocol.
Novell's 32-bit, protected-mode IPX/SPX-compatible protocol.
Novell's real-mode IPX protocol.
Microsoft's TCP/IP.
Novell's NetWare/IP.

Microsoft provides a 32-bit, protected mode IPX/SPX-compatible protocol that is compliant with network driver interface specification (NDIS) 3.1 and later and with the IPX specification. This protocol can use IPX routers, such as Novell NetWare servers configured as routers to transfer packets across LANs to access resources on other computers running any IPX/SPX protocol. With the Microsoft IPX/SPX-compatible protocol, you do not need to load the Novell-supplied Vipx.386 driver.

Consider the following issues when using Microsoft's 32-bit, IPX/SPX-compatible protocol:

You can use this protocol with Client for NetWare Networks and Novell Client for Windows 95/98, but you cannot use it with Novell's real-mode clients, NETX and VLM.
The Microsoft IPX/SPX-compatible protocol is installed automatically if you install Client for NetWare Networks. However, if you configure Windows 98 to maintain the existing NetWare client and protocol software instead, you can later try to install the Microsoft IPX/SPX-compatible protocol by following the instructions in Chapter 15, "Network Adapters and Protocols."
You can install both protected-mode and real-mode IPX drivers on the same adapter with ODI drivers.

Novell provides a 32-bit, IPX/SPX-compatible protocol that works with Novell Client for Windows 95/98. Novell Client for Windows 95/98 does not work with the Novell IPXODI protocol, the 16-bit module for the NETX and VLM clients.

Client for NetWare Networks does not support NetWare IP. Also, Microsoft TCP/IP cannot provide TCP/IP support on NetWare networks. NetWare IP uses other protocol implementations for IP functionality, so the two protocol suites cannot communicate with each other.

Although you cannot use Microsoft TCP/IP as the supporting protocol for Client for NetWare Networks or for Novell-supplied, real-mode networking clients, you can use Microsoft TCP/IP to support Novell Client for Windows 95/98 and other networking clients on the same computer. Use this configuration when TCP/IP-based communications are used on the network.

Setting Up Windows 98 for NetWare Networks: An Overview

If you are administering a NetWare network, the move to Windows 98 will involve incremental planning, testing, and gradual implementation of Windows 98 on many computers on the network. Typically, the administrator will take time to complete the following tasks:

Install Windows 98 on a single workstation, and experiment with various configuration alternatives.

This task includes experimenting with the typical applications used at your site and working over the network to assess the performance, reliability, and robustness available under Windows 98.

For information about choosing protocols and a network client, see the section "Planning for Windows 98 on NetWare Networks."
Prepare an implementation strategy, as summarized in Chapter 1, "Deployment Strategy."
Test the selected configuration of network clients, protocols, and drivers on a small network.
Create default user profiles, system policies, and setup scripts, and perform other customization tasks for automatic installation and configuration, based on the inventory and implementation strategy.
Test automatic installation on a small network.
Prepare and implement the strategy for rollout on the larger network.

Windows 98 Setup detects whether a Novell NetWare workstation shell client is running on the computer. During the detection phase, Windows 98 Setup also tries to determine whether the computer is using real-mode TSRs that cannot be replaced (such as Dosnp.com, TCP/IP client software, or 3720 emulators).

After detection is complete, Windows 98 Setup determines whether to remove the existing components and install Client for NetWare Networks. If Setup finds the NETX client, it removes NETX and automatically configures Client for NetWare Networks. See "Installing or Upgrading a Real-Mode client" for issues you should consider before upgrading NETX or VLM.

However, Windows 98 Setup does not automatically install Client for NetWare Networks if detection finds the following:

The computer is using Novell Client for Windows 95/98 or VLM with NetWare 4.x NDS, and you call Login.exe either in Autoexec.bat or a batch file referenced by it (such as Startnet.bat). In this case, Setup leaves all existing networking components in place.
Certain TSRs are present that require ODI. In this case, Setup installs Client for NetWare Networks but configures it to run over ODI.
Certain TSRs are present that are not compatible with the protected-mode client, but can use the new implementation of the IPX/SPX-compatible protocol. In this case, the real-mode network client and adapter drivers are left in place, but Setup installs the new protocol.
Certain TSRs are present that are not compatible with Client for NetWare Networks or other protected-mode components. In this case, Setup leaves all existing real-mode networking components in place.

To install Client for NetWare Networks and other protected-mode networking components, Setup might perform the following actions:

Comment out NetWare-related TSRs in Autoexec.bat that are not required with Client for NetWare Networks or other Windows 98 components.
Move certain TSRs from Autoexec.bat to Winstart.bat so that this software can be loaded at the appropriate time during system startup.
Install new 32-bit, protected-mode versions of networking components such as protocols and network adapter drivers.
Comment out entries from System.ini that are not required when using protected-mode networking components.
Configure settings in the registry related to support for NetWare networks

The actions for software detection and installation of new networking components are defined in a file named Netdet.ini in the \Windows directory. Installation actions are defined in Netdet.ini for the software listed in Table 17.1. For a complete and current list, see Netdet.ini in your \Windows directory.

Table 17.1 Windows 98 Setup software detection and installation

Software detected	Windows 98 Setup default action
Btrieve (Brequest.exe)	Installs Client for NetWare Networks, with all protected-mode components.
Dosnp.exe	Keeps the real-mode IPX protocol in place.
LAN Workplace	Installs Client for NetWare Networks, but keeps the real-mode ODI network adapter and IPX protocol in place.
Novell NetBIOS TSR	Installs the Microsoft IPX/SPX-compatible protocol and enables NetBIOS support.
NACS/NASI (Nasi.exe)	Retains all existing Novell-supplied networking components.

For information about the format of entries in Netdet.ini and how to customize this file, see Chapter 3, "Custom Installations."

Windows 98 Setup automatically configures settings for network adapters and protocols. The specific issues for configuring drivers and protocols depend on whether the computer is using Client for NetWare Networks or a Novell-supplied workstation shell.

Note Windows 98 Setup does not automatically install the Microsoft Service for NetWare Directory Services, which provides integration with NDS. To install Microsoft Service for NetWare Directory Services, follow the procedure "To add Microsoft Service for NetWare Directory Services after installing Windows 98" in "Setting Up Microsoft Service for NetWare Directory Services" later in this chapter.

Configuring NetWare Servers to Support Windows 98

This section presents information about installing Windows 98 source files on NetWare servers, automating Setup for NetWare workstations, support for long file names on NetWare servers, and where to place user profiles and system policy files on NetWare servers.

Installing Windows 98 Source Files on NetWare Servers

The Windows 98 master files can be placed on a NetWare server to be used as source files for installing Windows 98 locally on NetWare workstations.

To set up Windows 98 source files on a NetWare server

On the network administrator's computer, log on to the NetWare file server where you want to place the Windows 98 source files. Make sure you log on with security privileges that allow you to create directories and copy files to the file server. Then copy the Windows 98 source files to the NetWare file server.

Automating Setup for NetWare Workstations

You can create automatic installation procedures for installing Windows 98 on multiple workstations. The steps include the following:

Creating setup scripts for installing Windows 98 on computers connected to NetWare networks, specifying the network client and supporting components, plus defining other software components to be installed.
Defining user and computer settings to be used in setup scripts for specific NetWare workstation configurations.
Creating logon scripts to set up Windows 98 automatically on NetWare workstations when users log on.

For a complete description of the procedures for preparing and managing automatic installation of Windows 98 on multiple computers, see Chapter 4, "Automated Installations."

Supporting Long File Names on NetWare Servers

Computers running a 32-bit, protected mode client with Windows 98 can use long file names on NetWare 3.x and 4.x volumes configured to use the OS/2 name space, which emulates a high-performance file system (HPFS) volume. File names on such NetWare volumes have a maximum length of 254 characters and use an 8.3 truncation on the first instance of the file name. For example:

longfilenameold.tst --> LONGFILE.TST
longfilenamenew.tst --> LONGFIL0.TST

The following procedures describe how to enable long file names on NetWare servers.

To enable long file names on NetWare servers running versions 4.10 or earlier

At the NetWare server console prompt, type the following lines:
```
load os2
```

add name space os2 to volume sys

Then add the following line to Startup.ncf:
```
load os2
```

Shut down the file server. Then copy Os2.nam from the NetWare distribution disks or compact disc to the same disk and directory that contains Server.exe on the NetWare file server.
Restart the NetWare file server.

To enable long file names on NetWare servers running versions later than 4.1x

At the NetWare server console prompt, type the following lines:
```
load long
```

add name space long to sys

To verify that long file names have been added

At the NetWare server console prompt, type volume.

If you have problems with these procedures, contact Novell for more information.

When you use long file names for files on a NetWare volume while running Windows 98, the following exceptions occur:

You cannot use a combination of short names and long names for a path used in an MS-DOS prompt window.
You cannot use cd in an MS-DOS prompt window to switch directories using first a long file name, then a truncated name, or vice versa.
You cannot use dir in an MS-DOS prompt window to check a directory on a NetWare server if you used a truncated name to switch to that directory.

To avoid these problems, use Windows Explorer. Otherwise, avoid long directory names if you do a lot of work at the command prompt.

NetWare 3.11 servers experience problems with applications that open a large number of files. Error messages report these problems as sharing or lock violations, or report a "file not found" error when you know the file exists, or report other errors in opening files. Novell supplies a patch for this problem, which you can obtain from https://support.novell.com/ .

However, if you have not applied the patch, this problem affects how NetWare 3.11 servers handle long file names, even if the OS/2 name space is enabled. To avoid such problems, Windows 98 Setup enables long file name support only with NetWare servers version 3.12 or later.

To support long file names on all NetWare servers, you should apply all proper NetWare patches at your site. You must also set the value of SupportLFN to 2, expressed in binary as "10," in the following registry subkey:

Hkey_Local_Machine \System \CurrentControlSet \Services \VxD \Nwredir

Important Enter the value for this registry subkey in binary notation. Thus, enter the binary value "10" for a decimal value of 2.

The possible values for this registry key are the following:

0, which indicates that long file names are not supported on NetWare servers.
1 (the default), which indicates that long file names are supported on NetWare servers version 3.12 and later.
2, which indicates that long file names are supported if the NetWare server supports long file names. This can include NetWare 3.11 servers where the patch has been applied.

These values can also be set globally using system policies. The related policy name is Support Long File Names under the policies for Client for NetWare Networks.

If computers running Windows 98 will be providing File and Printer Sharing Services for NetWare Networks, then the NetWare server providing access validation can be configured with a special WINDOWS_PASSTHRU account. This special account is used to support pass-through validation for user-level security. It is not necessary for users who already have an account on that server.

For more information about configuring and managing pass-through and user-level security for Windows 98 on NetWare networks, see Chapter 9, "Security."

Placing Profile and Policy Files on NetWare Servers

User profiles, which consist of the user-specific information in the registry, can be used to ensure a consistent desktop for individual users who log on to multiple computers, or for multiple users logging on to the same computer. User profiles can be used on a NetWare network with computers configured to use Microsoft Client for NetWare Networks. When a user account is created on a NetWare server, a subdirectory of the MAIL directory is created automatically for that user. Because a MAIL directory is always available for each user, Windows 98 uses these individual directories to store user profiles. If you want to use user profiles to enforce a mandatory desktop, place the related User.man file in the users' MAIL directories.

If you are using system policies to enforce specific desktop or system settings, the appropriate Config.pol file must be stored in the SYS:PUBLIC directory on each NetWare server that users use as a preferred server. Windows 98 automatically downloads policies from this file.

Note Novell Client for Windows 95/98 always looks for Config.pol in the SYS:SYSTEM directory of the preferred server, not the logon server. If you have not set the preferred server, Config.pol does not automatically download.

For more information about using user profiles or creating system policies, including information about using profiles and policies with Service for NetWare Directory Services, see Chapter 7, "User Profiles," and Chapter 8, "System Policies."

Installing and Configuring MS Client for NetWare Networks

The redirector provided by Client for NetWare Networks (Nwredir.vxd) is a file system driver that supports the NCP file sharing protocol for NetWare 3.x and NetWare 4.x. Client for NetWare Networks also supports Microsoft File and Printer Sharing for NetWare Networks (Nwserver.vxd, the NCP peer server provided with Windows 98).

In addition to installing Client for NetWare Networks, you can install the optional Microsoft Service for NetWare Directory Services. Microsoft Service for NetWare Directory Services adds several features, such as support for NDS and for logon scripts. If you install Microsoft Service for NetWare Directory Services, Client for NetWare Networks will be automatically installed.

This section describes how to install and configure Client for NetWare Networks and Microsoft Service for NetWare Directory Services, and provides some technical notes on supporting files.

For information about how to configure logon for Client for NetWare Networks and Microsoft Service for NetWare Directory Services, see Chapter 18, "Logon, Browsing, and Resource Sharing."

Setting Up MS Client for NetWare Networks

When using Client for NetWare Networks, you generally do not need to load any Novell-supplied drivers or components. This client runs with the Microsoft IPX/SPX-compatible protocol and NDIS-compliant, protected-mode drivers, which Windows 98 Setup installs automatically when you select this client.

However, you may need to load Novell-supplied files if you are running NetWare-aware utilities and they do not function correctly with Microsoft Client for NetWare Networks, or if you have installed Microsoft Service for NetWare Directory Services and you need to run NDS-based utilities. For a list of these files, see "NetWare API Support in Client for NetWare Networks" later in this chapter.

When Windows 98 is installed with Client for NetWare Networks, Windows 98 Setup automatically moves any relevant Net.cfg settings to the Windows 98 registry. You can configure the related settings using the Network option in Control Panel. You can also configure the network adapter driver and the IPX/SPX-compatible protocol, as described in Chapter 15, "Network Adapters and Protocols."

If you did not install Client for NetWare Networks before Windows 98 Setup, you can switch to this client any time after Windows 98 is installed. If you need to connect to the NDS tree, follow the procedures outlined in "Setting Up Microsoft Service for NetWare Directory Services" later in this chapter. However, if you do not need to connect to the NDS tree, follow the procedure "To add Client for NetWare Networks after Windows 98 has been installed" in this section.

You can also install Client for NetWare Networks and configure related options when installing Windows 98 using custom setup scripts, as described in Chapter 3, "Custom Installations."

Tip To display the Network option without opening Control Panel, right-click the Network Neighborhood icon on the desktop. Then click Properties on the context menu.

Note Windows 98 Setup copies files from your original Windows 98 installation media, so make sure your original Windows 98 installation media are ready before you perform this procedure.

To add Client for NetWare Networks after installing Windows 98

In Control Panel, double-click Network and examine the list of installed components. If the computer currently has NETX or VLM installed, select that NetWare Workstation Shell client in the list of installed components, and then click Remove. Also, select and remove the IPXODI protocol if it appears in the list.
Click Add, and then double-click Client in the Select Network Component Type dialog box.
In the Select Network Client dialog box, click Microsoft in the Manufacturers list, and then click Client for NetWare Networks in the Network Clients list. Then click OK.

You must shut down and restart the computer for the changes to take effect.

Caution Do not click Cancel during the installation. If you decide that you do not want to install Client for NetWare Networks, you must complete the installation process and then remove Client for NetWare Networks.

Setup automatically installs and configures all related components. Windows 98 Setup also adds the value lastdrive=32 to the parameters for the network client in the registry. This value makes room for entries in a table to store drive information. For Microsoft networking, the last drive would be set to Z (or 26), but NetWare allows six additional entries in its drive table.

Setting Up MS Service for NetWare Directory Services

If you install Microsoft Service for NetWare Directory Services, Client for NetWare Networks will also be automatically installed. You do not need to install Microsoft Client for NetWare Networks if you install Microsoft Service for NetWare Directory Services.

Adding MS Service for NetWare Directory Services after Installing Windows 98

You can add Microsoft Service for NetWare Directory Services whether or not you have already installed Client for NetWare Networks.

Note Windows 98 Setup copies files from your original Windows 98 installation media, so make sure your original Windows 98 installation media are ready before you perform this procedure.

To add Microsoft Service for NetWare Directory Services after installing Windows 98

In Control Panel, double-click Network and examine the list of installed components. If the computer currently has NETX or VLM installed, select that NetWare Workstation Shell client in the list of installed components, and then click Remove. Also, select and remove the IPXODI protocol if it appears in the list.
Click Add, and then double-click Service in the Select Network Component dialog box.
In the Select Network Service dialog box, click Microsoft in the Manufacturers list, and then click Service for NetWare Directory Services in the Network Services list. Then click OK.

You must shut down and restart the computer for the changes to take effect.

After your computer restarts, you will be prompted to log on to the NDS tree. Make sure the dialog box identifies the correct context and tree.

Caution Do not click Cancel during the installation. If you decide that you do not want to install Microsoft Service for NetWare Directory Services, you must complete the installation process, and then remove Microsoft Service for NetWare Directory Services.

Automated Installation of MS Service for NetWare Directory Services

You can include Microsoft Service for NetWare Directory Services in automated installations that work with Msbatch.inf. For more information about automated installations, see Chapter 4, "Automated Installations."

To include the Service for NetWare Directory Services in an automated installation

Copy the following two lines to the [Network] section in Msbatch.inf.
```
Clients=NWREDIR
```

Services=NWREDIR4

**Note** You can also include entries for other networking clients and services on the above lines. Each entry should be separated by a comma. For example: 

<pre IsFakePre="true" xmlns="https://www.w3.org/1999/xhtml">Clients=VREDIR,NWREDIR

If you want to set the preferred tree and default context in Msbatch.inf, add the following lines:
```
[NWRedir4]
```

PreferredTree = <Tree> NameContext = <MyNameContext>

Save and exit Msbatch.inf.

At the command prompt, type:

setup <drive letter>:<path>\msbatch.inf

– Or – 

Place Msbatch.inf in the same directory as Setup.exe and then run Setup.

If you are doing an automated installation of Microsoft Service for NetWare Directory Services on computers that are running the NETX or VLM client, you should be aware of the following issues:

Setup does not automatically comment out the line in Startnet.bat or Autoexec.bat that loads NETX or VLM. This will not cause any problems, but you may want to delete the line or comment it out.
If Windows is not already installed on the computers, an error message may appear during Windows 98 Setup saying that you should run the Novell Workstation Shell install program after Windows 98 Setup. Disregard this message.

Configuring MS Client for NetWare Networks

This section presents information for configuring and using Microsoft Client for NetWare Networks, including the following topics:

Configuring protected-mode NDIS network adapter drivers for Client for NetWare Networks.
Configuring Client for NetWare Networks with ODI network adapter drivers.
Running NetWare utilities with Client for NetWare Networks and Microsoft Service for NetWare Directory Services.

For information about configuring logon options for Client for NetWare Networks, see Chapter 18, "Logon, Browsing, and Resource Sharing."

Configuring Protected-Mode NDIS Network Adapter Drivers for Client for NetWare Networks

When you install Client for NetWare Networks, a 32-bit, protected-mode, NDIS 3.1 and later compliant network adapter driver is installed automatically, unless the computer is running software cited in Table 17.1.

Although it is possible to run Client for NetWare Networks over ODI drivers, Microsoft recommends that you install a 32-bit, protected-mode network adapter driver to take advantage of the performance improvements offered by these drivers, as described in Chapter 15, "Network Adapters and Protocols." If you do configure Client for NetWare Networks to use ODI drivers instead, you can switch to the protected-mode drivers at any time.

Depending on when you install Client for NetWare Networks, you might have to install the 32-bit, protected-mode network adapter driver before you can install the network client. Setup prompts you to do this if it is necessary.

To switch to a 32-bit, protected-mode network adapter driver

In Control Panel, double-click Network, and then double-click the network adapter in the list of installed network components.
In the Driver Type tab, click the option named Enhanced mode (32 bit And 16 bit) NDIS driver, and then click OK.
Shut down and restart the computer.

For more information about using NDIS, see Chapter 15, "Network Adapters and Protocols."

Configuring Client for NetWare Networks with ODI Network Adapter Drivers

This section describes how to configure Client for NetWare Networks with ODI network adapter drivers. For more information about ODI, see "Configuring Network Adapter Drivers for Real-Mode Novell Clients" later in this chapter.

Figure 17.1 shows the architecture for Client for NetWare Networks with ODI network adapter drivers. Novell-supplied components appear in bold.

Cc768187.wrk0y02(en-us,TechNet.10).gif

Figure 17.1 Architecture for protected-mode client with ODI drivers

Using an ODI driver instead of an NDIS 3.1 or later driver with Client for NetWare Networks has the following drawbacks:

There is some use of conventional memory, and overall performance on the network is not as good as with NDIS 3.1 or later drivers.
There are no Plug and Play capabilities for the networking components.

If you want to use the current ODI driver instead of a Windows 98 NDIS network adapter driver, you can select that driver using the Network option in Control Panel. For more information about using ODI drivers, see "Configuring Windows 98 with ODI Drivers" later in this chapter. For information about the related files, see "Obtaining Current Novell-Supplied Files" later in this chapter.

To use ODI drivers with Client for NetWare Networks

In Control Panel, double-click Network.
In the list of installed components, double-click your network adapter.
In the Properties dialog box for your network adapter, click the Driver Type tab.
Click Real mode (16 bit) ODI driver, and then click OK. Then shut down and restart the computer.

Running NetWare Utilities with Client for NetWare Networks and MS Service for NetWare Directory Services

With Client for NetWare Networks, you can use the 32-bit, protected-mode graphical tools built into Windows 98 as well as the 16-bit command-line utilities provided with NetWare for managing and sharing resources. You can run all NetWare 3.x utilities that reside on the NetWare server, such as SYSCON. You can also run most bindery-based NetWare 4.x utilities. However, you cannot use the VLM NWUSER utility, and you cannot use utilities that require NDS.

If you are running Microsoft Client for NetWare Networks along with Microsoft Service for NetWare Directory Services, you can use all the tools listed above, as well as graphical tools and utilities that require NDS, including NWAdmin, CX, and NETADMIN.

Tip SYSCON, a tool for NetWare 3.x servers, and NETADMIN, a tool for NetWare 4.x servers, are located in the SYS:PUBLIC directory. To access them using NetWare 3.x, map a drive to them either in a logon script or while you are running Windows 98. If you are using NetWare 4.x, you can also access NETADMIN from Network Neighborhood. Both SYSCON and NETADMIN are MS-DOS utilities, so whichever way you access them, you must run them from a command prompt (either a virtual machine or the Run prompt).

To run NetWare utilities from an MS-DOS prompt

Map a drive to the volume containing the NetWare utilities by using statements in a logon script or by using the Map Network Drive dialog box.

When you use Map Network Drive, you can make this a persistent connection by clicking the Reconnect at logon box.
From Start, point to Programs, and then click MS-DOS Prompt to start an MS-DOS session.
Switch to the mapped network drive, and then run the utilities in the usual way.

If you are running Microsoft Service for NetWare Directory Services and you are logged on to an NDS tree, you can also run NetWare utilities by clicking on their icons in Network Neighborhood.

To run NetWare utilities from Network Neighborhood

In the NDS tree, double-click the volume that contains the utility.
Double-click the utility.

Note To run NetWare 4.x NDS utilities, you must install Microsoft Service for NetWare Directory Services. You also need access to, and the appropriate license to use, the NetWare dynamic link libraries (DLLs) listed in "NetWare API Support in Client for NetWare Networks" later in this chapter.

Installing and Configuring Novell NetWare Clients

Windows 98 can run with the following Novell-supplied clients:

Novell Client for Windows 95/98, a 32-bit, protected-mode client that supports NDS.
NetWare VLM, a 16-bit, real-mode client that supports NetWare 3.x and 4.x servers.
NetWare NETX, a 16-bit, real-mode client that supports NetWare 3.x servers, as well as NetWare 4.x servers in bindery mode.

It is strongly recommended that you use Novell Client for Windows 95/98 instead of a real-mode client. Novell Client for Windows 95/98 provides more efficient memory use than the real-mode clients. It also provides such capabilities as support for NDS, support for optional components, such as IP Gateway, and integrated Windows logon.

Note If you are running Windows 98 Setup from a Windows for Workgroups computer that has Novell Client for DOS/Windows 3.x, Setup will fail. You should delete Novell Client for DOS/Windows 3.x Client before running Windows 98 Setup.

The following section describes how to set up and configure Windows 98 with Novell-supplied clients. For more information, contact Novell.

Note Before installing Windows 98, make sure that you have the necessary Novell-supplied files for Windows support, which can be obtained from Novell.

If you are upgrading to Windows 98 from another version of Windows, and you had Novell-supplied NetWare client software on your previous version of Windows, make sure that the Novell-supplied NetWare client software is working properly before you start Windows 98 Setup. To verify that the Novell-supplied software is working, make sure you can successfully connect to and use resources on a NetWare server.

This section describes how to install Novell Client for Windows 95/98 after Windows 98 Setup. First, it describes how to prepare the installation, then it describes how to perform the installation, and finally, it describes how to remove Novell Client for Windows 95/98.

Removing Incompatible Software

Before you install Novell Client for Windows 95/98, make sure that none of the following software is installed on your Windows 98 computer:

Microsoft Client for NetWare Networks.
Microsoft File and Printer Sharing for NetWare Networks.
Microsoft Service for NetWare Directory Services.
NETX or VLM.
Novell IPXODI protocol (the 16-bit protocol for NETX and VLM clients). This is the 16-bit module for the NETX and VLM clients. The Novell Client for Windows 95/98 uses the IPX 32-bit protocol.

These network components conflict with Novell Client for Windows 95/98. If any of these components are installed, the Client installation program detects the conflict and removes the conflicting network components.

Preparing NetWare servers for the Installation

You must also prepare your servers for the installation. For NetWare 3.x and 4.x servers (except NetWare 4.11 servers), make sure the patches shipped with Novell Client for Windows 95/98 are installed.

Also, to support long file names, load Long.nam on each NetWare 4.11 server and on each volume. (See the Novell Client online help for more information.) For versions of NetWare earlier than NetWare 4.11, use the OS/2 name space instead of Long.nam.

Each name space uses up to 252 kilobytes (KB) of disk space. Each name space added to a volume requires additional server memory. If you add name space support to a volume, but do not have enough memory, the server cannot mount that volume. Once you add a name space to a volume, you cannot remove that name space unless you delete the volume and re-create it or use VREPAIR.

For information about how to calculate the memory required for name space support and for how to remove a name space, contact Novell.

Installing Novell Client for Windows 95/98

If you have installed Microsoft Client for NetWare Networks or an old version of a Novell protected-mode NetWare client, Setup for Novell Client for Windows 95/98 replaces it with the Novell Client.

You can run Setup in one of four ways:

From the Network option in Control Panel.
From a Novell-provided Novell Client for Windows 95/98 CD-ROM.
By downloading the Novell Client for Windows 95/98 files from Novell's Web site at https://www.novell.com/ .
By placing the Novell Client for Windows 95/98 files on a Windows NT or NetWare server and then running Setup from the mapped drive.

This section discusses the first two methods.

Regardless of which method you choose, you should have your original Windows 98 installation media ready before running Setup.

Take the following steps to install Novell Client for Windows 95/98 from the Network option in Control Panel.

To install Novell Client for Windows 95/98 from the Network option in Control Panel

Start Windows 98.
In Control Panel, double-click Network.
Remove any installed NetWare clients and components, and then click Add.
Click Client, and then click Add.
In the Select Network Client dialog box, click Have Disk.
Enter the directory where your Novell Client installation files are located, and then click OK.
In the Network dialog box, select the Novell Client and then click Properties.
Type the preferred server, tree, and context, click OK, and then click OK again.
When Windows 98 asks you whether to restart the computer, click Yes.

Take the following steps to install the Novell Client for Windows 95/98 from the Novell-provided Novell Client for Windows 95/98 CD-ROM.

To install Novell Client for Windows 95/98 from the CD-ROM

Start Windows 98.
Insert the CD-ROM for Novell Client for Windows 95/98. The setup file, Setup.exe, loads automatically.
Click a language for the installation.
Click a set of components to install.
Click Install the Novell Client for Windows 95/98.
Accept the Novell License Agreement by clicking Yes.
Click Typical and then Install. Setup installs default settings.
If prompted to select a network adapter, choose one that matches your hardware. The Select Device dialog box displays a list. After you choose one, you may be asked to set the Interrupt Request (IRQ) and I/O Address Range. Note that asterisks help you avoid settings that conflict.
If prompted to set a Preferred Server, Preferred Tree, and Name Context, click Yes, enter information, and then click OK.

For NetWare 3.x, set a Preferred Server. For NetWare 4.x, set a Preferred Server, Preferred Tree, Name Context, and First Network Drive.

Click one of the following:
- Reboot. (The new client and settings do not take effect until you do this.)
- Return to Windows.
  
  This option takes you to the Network option in Control Panel and allows you to install optional components or configure your workstation.

Removing Novell Client for Windows 95/98

You can remove Novell Client for Windows 95/98 in one of two ways:

From the Network option in Control Panel. If you choose this option, client configuration information remains in the registry.
By running Novell's Uninstall utility. If you choose this option, all client configuration information is removed from the registry.

To use the Control Panel

In Control Panel, double-click Network, and then click the Novell Client for Windows 95/98.
Click Remove.
Remove any other Client networking components in the same way.

Examples of other networking components are Novell ODINSUP and the IPX 32-bit Protocol for Novell Client for Windows 95/98.
Click OK.
Click Yes and restart the workstation.

To use Novell's Uninstall utility

Locate and open the Unc32.exe file on the CD-ROM.

The file is on the Novell Client for Windows 95/98 CD-ROM in the Products\Win98 \IBM_ENU\Admin folder.
Optionally, if you want to remove any ODI drivers installed on the workstation, check the Remove Novell 32-bit ODI Adapter check box.

This check box appears only if a 32-bit ODI adapter has been installed on the workstation.
Click Continue.

The uninstall process begins.

Caution Do not try to cancel the uninstall process by turning off your computer. If you do so, your registry might become corrupt. If you do turn off your computer during the uninstall process, run the Uninstall utility again to finish uninstalling the client and to clean up the registry.
Click Reboot when the uninstall process is complete.

Configuring Network Adapter Drivers for Novell Client for Windows 95/98

Novell Client for Windows 95/98 works with Microsoft-provided, 32-bit NDIS network drivers and with Novell's 32-bit ODI drivers. If you want to use Novell Client for Windows 95/98 with Novell's 32-bit ODI drivers, you must install them by running Novell's Setup.exe instead of by using the Network option in Control Panel.

Novell Client for Windows 95/98 might also work with NDIS 2 or 16-bit ODI drivers; however, this configuration is not recommended.

Installing or Upgrading a Real-Mode Novell Client

Windows 98 works with the real-mode NETX and VLM clients; however, it is strongly recommended that you upgrade to the protected-mode Client for NetWare Networks or Novell Client for Windows 95/98.

By default, Windows 98 Setup automatically replaces NETX with Microsoft Client for NetWare Networks. To install Windows 98 with NETX, you must use a custom setup script.

However, Microsoft supports upgrading from NETX to Client for NetWare Networks only if you are logged on to a NetWare server at the time of the upgrade. For more information, see the troubleshooting step "Upgrade from NETX to Client for NetWare Networks fails," later in this chapter.

If you are running VLM and you do not call Login.exe either in Autoexec.bat or a batch file referenced by it (such as Startnet.bat) when you install Windows 98, Windows 98 Setup might replace VLM with Client for NetWare Networks.

However, Windows 98 Setup does not replace VLM with Microsoft Client for NetWare Networks if you are logged on to NDS when you start Windows 98 Setup. If you are running VLM and you are logged on to NDS using the Login.exe command either in Autoexec.bat or a batch file referenced by it (such as Startnet.bat), Windows 98 uses the existing networking configuration specified in Net.cfg for protocols, adapter drivers, and other values.

If you currently use Ipx.com, Microsoft recommends that you upgrade to the latest versions of NetWare client software that use ODI drivers before you install Windows 98. Windows 98 does not support Ipx.com.

Caution NETX and VLM require that you log on to the appropriate NetWare server before starting Windows 98. Thus, if you are using these clients, you should not log on to a NetWare server from within Windows 98.

Instead, log on to the server from Autoexec.bat or from a batch file that is called from Autoexec.bat. You should also continue to load the necessary MS-DOS-based TSR programs using Autoexec.bat or Startnet.bat.

For information about where a logon command should be placed in system startup files, see Chapter 18, "Logon, Browsing, and Resource Sharing."

This section describes how to install Windows 98 with ODI drivers, how to verify that you are using the correct drivers, how to retain VLM and NETX when you are upgrading to Windows 98, and how to install them after Windows 98 Setup. For architectural information about ODI drivers and for information about Net.cfg settings, see "Configuring Network Adapter Drivers for Real-Mode Novell NetWare Clients" later in this chapter.

Installing Windows 98 with ODI Drivers

Before you install Windows 98 on a computer, the real-mode IPXODI network should be configured and working properly using your Novell-supplied installation program. Test to confirm that there are no errors when loading the Novell-supplied files Lsl.com, Ipxodi.com, the ODI driver, and Netx.exe or Vlm.exe, or when accessing resources on NetWare servers.

If Windows 98 Setup cannot identify the ODI driver being used, you might have to configure the network adapter driver manually.

To configure the network adapter driver manually

In Control Panel, double-click Network, and then click Add.
In the Select Network Component Type dialog box, click Adapter, and then click Add.
In the Select Network Adapters dialog box, click Have Disk. You must provide an INF file for the correct IPXODI support driver to match the type of network adapter used, using a file supplied by Novell or the adapter manufacturer.

Verifying Drivers for Real-Mode Clients After Windows 98 Setup

Before installing a real-mode client, make sure the correct adapter driver is installed. Real-mode clients require 16-bit ODI drivers, and some cards do not work with those drivers. If you cannot install the correct adapter driver, you will not be able to install the real-mode client.

To determine whether the correct adapter driver is installed after Windows 98 Setup

In Control Panel, double-click Network, and then double-click the network adapter (or your existing ODI driver) in the list of installed components.
In the Properties dialog box for the network adapter, click the Driver Type tab.
Make sure the Real mode (16 bit) ODI driver option is selected.

Upgrading Windows 98 with VLM

This section describes how to upgrade Windows 98 and retain the VLM client if VLM support was previously installed under Windows 3.x or Windows 95 and you are upgrading from the \Windows directory, or if VLM was previously installed under DOS.

If you run Windows 98 Setup without the proper preparation, Setup replaces VLM with Client for NetWare Networks. You can prevent VLM from being replaced in one of two ways:

By including VLM in Msbatch.inf. For more information about Msbatch, see Chapter 3, "Custom Installations," and Appendix D, "Msbatch.inf Parameters for Setup Scripts."
By following the steps in the following procedure.

To retain VLM during Windows 98 upgrade

Make sure that you have the files Netware.hlp, Nwpopup.exe, Vipx.386, Vetware.386, Ipxodi.com, Lsl.com, Netware.drv, and the driver for your network adapter.

Note If you are upgrading from a version of Windows, those files should be located in you /Windows/System and network client directories.

Otherwise, use the NetWare Nwunpack command to expand the following files from your VLM installation media: Netware.hl_, Nwpopup.ex_, Vipx.38_, Vnetware.38_, Ipxodi.co_, Lsl.co_, Netware.dr_, and the driver for your network adapter.
Add the Login.exe command in Autoexec.bat or a batch file referenced by Autoexec.bat, such as Startnet.bat.
Reboot.
When prompted to log on to the NetWare server, log on and make sure your Novell-supplied software is functioning correctly.
Run Windows 98 Setup.
If Windows 98 asks for the Novell-supplied files that you expanded using Nwunpack, enter the path for those files.
If prompted, run the Novell Workstation Shell Install program. Consult your NetWare documentation for information about the Novell-supplied installation program.

Note Setup might place the entry device=*vnetbios in System.ini, which causes a blue screen error to appear when you restart the computer. You can safely ignore this screen.
After Setup finishes, in Control Panel, double-click Network.

You must reboot your computer for the changes to take effect.

In the Network option in Control Panel, you will see that Setup has added Novell NetWare (Workstation Shell 4.0 And Above [VLM]) as a network client. You might also need to modify configuration files, such as Net.cfg and Autoexec.bat. Consult your NetWare documentation for more information.

Installing VLM for the First Time After Windows 98 Setup

This section describes how to install the VLM client after Windows 98 Setup if it has not been previously installed. For information about how to upgrade VLM from Windows 95, see the sections "Upgrading Windows 98 With VLM in Typical Installations" and "Upgrading Windows 98 With VLM in Special Cases," earlier in this chapter.

Note Before attempting to install VLM, you should follow the procedure in "Verifying Drivers for Real-Mode Clients After Windows 98 Setup," earlier in this chapter.

To install VLM after Windows 98 Setup

On your VLM installation disk, locate the files Netware.hl_, Nwpopup.ex_, Vipx.38_, Vnetware.38_, Ipxodi.co_, Lsl.co_, Netware.dr_, and the driver for your network adapter. Use the NetWare Nwunpack command to expand them.
Remove all NetWare clients from the Network option in Control Panel.
In Control Panel, double-click Network, and then click Add.
In the Select Network Component Type dialog box, double-click Client.
In the Select Network Client dialog box, click Novell in the Manufacturers list, and click Novell NetWare (Workstation Shell 4.0 and above [VLM]) in the Network Clients list. Then click OK, and then click OK again. The computer copies files, then prompts you to reboot to the command prompt.
Reboot the computer.
After rebooting, run the Novell-supplied installation program. Consult your NetWare documentation for information about the Novell-supplied installation program.
After the installation program has finished copying files, exit to MS-DOS and then type win at the c: prompt.

Note You will see an error message stating that you have a bad or missing VnetBIOS. Continue past this error message.
In Control Panel, double-click Network. Windows 98 should notify you that the VLM installation program has been run.

You must reboot your computer for the changes to take effect. You might also need to modify configuration files, such as Net.cfg and Autoexec.bat. Consult your NetWare documentation for more information.

Upgrading Windows 98 with NETX

By default, if Windows 98 Setup detects the NETX client, it replaces NETX with Microsoft Client for NetWare Networks. If you want to retain NETX when you upgrade to Windows 98, follow these steps.

To select Novell-supplied NETX client support during Windows 98 Setup

Have your NETX files available before you run Setup.
In Msbatch.inf, add the value netware3 to the parameter Clients.
Run Setup with the Msbatch.inf parameter.

– Or –

Place Msbatch.inf in the same directory as Setup.exe and then run Setup.

For information about creating and using Msbatch.inf files, see Chapter 3, "Custom Installations." For information about Msbatch.inf parameters, see Appendix D, "Msbatch.inf Parameters for Setup Scripts."

Alternatively, you can install the Novell-supplied NETX client software after you have run Windows 98.

Note Before attempting to install NETX, you should follow the procedure in "Verifying Drivers for Real-Mode Clients After Windows 98 Setup," earlier in this chapter.

To reinstall NETX after Windows 98 Setup

Back up your NETX files.
Run Windows 98 Setup.
After Windows 98 Setup is complete, in Control Panel, double-click Network.
Remove all other NetWare clients from the Network option in Control Panel.

Important Make sure you remove Client for NetWare Networks before installing NETX.
Click Add, and then double-click Client.
In the Select Network Client dialog box, click Novell in the Manufacturers list, and click Novell NetWare (Workstation Shell 3.X [NETX]) in the Network Clients list. Then click OK.

Windows 98 automatically installs IPXODI support.
Click OK in Network properties, and provide a disk or a location for any files that Windows 98 requests to complete the installation. Then shut down and restart the computer.

Usually, you will have to reinstall Novell-supplied files at this stage, because Windows 98 Setup previously replaced these files with versions required by Client for NetWare Networks. You must also make sure that Net.cfg is present and contains correct settings, and that the required settings are present in Config.sys and Autoexec.bat. See your Novell documentation for information about these required settings.

Configuring Network Adapter Drivers for Real-Mode Novell Clients

Before attempting to install a real-mode client, you should make sure your network adapter card and drivers work with your real-mode client. In some cases, you must obtain a driver that works with ODI. After you install a real-mode client, you might need to make changes to Net.cfg, the Novell NetWare configuration file that specifies settings for the adapter, protocol, and client.

This section presents some technical information related to the network adapter drivers used when configuring Windows 98 to run with Novell-supplied network clients. The topics include configuring Windows 98 with ODI drivers and setting options in Net.cfg.

For information about how to ensure your network adapter card and drivers work with your real-mode client, see "Verifying Drivers for Real-Mode Clients After Windows 98 Setup" earlier in this chapter. For information about installing ODI drivers, see "Installing Windows 98 with ODI drivers" earlier in this chapter. For information about the format and contents of Net.cfg, consult your Novell documentation.

Note Windows 98 does not support the monolithic IPX configuration. You should use ODI drivers with real-mode clients. Also, Windows 98 does not support ArcNet network adapters. For information about ArcNet network adapters, see the Microsoft Windows 95 Resource Kit.

Configuring Windows 98 with ODI Drivers

The Open Datalink Interface (ODI) specification was defined by Novell and Apple Computer to provide a protocol and a consistent API for communicating with a network adapter driver and to support the use of multiple protocols by a network adapter driver.

Figure 17.2 shows the architecture for ODI drivers.

Cc768187.wrk0y03(en-us,TechNet.10).gif

Figure 17.2 Architecture for ODI drivers

ODI consists of the following components:

An ODI-compliant version of the IPX/SPX protocol. This component provides the network protocol for communicating between NetWare clients and servers. With NETX or VLM clients, this must be the Novell-supplied Ipxodi.com. With Novell Client for Windows 95/98, it must be the 32-bit IPX protocol that ships with it.

For Client for NetWare Networks, you can also use the Microsoft IPX/SPX-compatible protocol.

The Link Support Layer (LSL). This component, provided in the Novell-supplied Lsl.com file, sets the foundation for the network adapter and multiple protocol drivers to communicate.

The ODI driver. Also called the Multiple Link Interface Driver (MLID), the ODI-compliant network adapter driver is created by the adapter manufacturer. This component usually identifies the name of the supported adapter in the file name, such as Ne2000.com for the Novell NE-2000 adapter, 3c5x9.com for the 3Com EtherLink III adapter, and Exp16odi.com for the Intel EtherExpress 16 adapter. Windows 98 supports using these drivers, but they are not included with Windows 98.

For information about required files, see "Obtaining Current Novell-Supplied Files" later in this chapter.

Setting Network Adapter Options in Net.cfg

Because a computer using ODI drivers can have multiple ODI drivers and multiple protocols loaded and bound, the networking software uses Net.cfg to identify the network adapters, protocol configuration, and binding information. Net.cfg is responsible for configuring the network environment for a Novell-supplied client, and is used to configure custom parameters for VLM, NETX, IPX, NetBIOS, or the general NetWare environment. To configure any options, edit Net.cfg as described in your Novell documentation.

NetWare uses Net.cfg as the configuration file name for ODI. You should not use Shell.cfg. If neither file exists, default settings are used.

If you are using ODI drivers, the Novell-supplied Lsl.com file uses information from Net.cfg to configure the ODI driver before the NETX workstation shell does. For the LSL driver to load and initialize information from Net.cfg, the proper Net.cfg file should reside in the same directory as Lsl.com and the Novell-supplied Netx.exe network client, or Lsl.com should take the path to the proper Net.cfg file as a parameter. To verify that there is not more than one Net.cfg file present on a computer, type dir /s net.cfg at the command prompt (or from Start, click Find and search for Net.cfg).

Network adapter configuration information is contained in a "Link Driver" section in Net.cfg, where you can specify the network adapter's interrupt, I/O address, memory address, frame types, and protocols. The following example shows Net.cfg entries for an SMC Ethercard Plus Elite 16 adapter:

show dots=on
file handles=60
preferred server=nw_311
link driver smc8000
int 5
port 240
mem d000
frame ethernet_802.3

Table 17.2 describes selected information commonly found in Net.cfg under the "Link Driver" section. For information not found in Net.cfg, default settings for the network adapter are assumed. For more information, consult your Novell documentation.

Table 17.2 Network adapter driver settings in Net.cfg

Net.cfg setting	Description
DMA	DMA channel number. Can assign up to two DMA channels by designating them DMA #1 x and DMA #2 y.
FRAME	Alternate media access control layer frame encapsulations for the network adapter. Frame types are: ETHERNET_802.3 ETHERNET_SNAP ETHERNET_802.2 TOKEN_RING ETHERNET_II TOKEN_RING_SNAP You must add the ETHERNET_II frame type for Microsoft TCP/IP to work over ODI drivers.
INT	Interrupt Request (IRQ) number. Can assign up to two IRQs by designating them IRQ #1 x and IRQ #2 y.
MEM	Memory address in upper memory area (UMA). Can assign up to two UMA addresses by designating them MEM #1 x and MEM #2 y.
NODE ADDRESS	12-digit media access control address assigned to the network adapter.
PORT	I/O port address. Can assign up to two I/O port addresses by designating them PORT #1 x and PORT #2 y.
PROTOCOL	Protocols to be used with ODI drivers. You do not need to specify this in Net.cfg if NETX is running only the IPX protocol. If other protocols are running, you must specify the protocol, protocol ID, and frame type.
SLOT	Network adapter slot number (MCA, EISA).

Technical Notes for Windows 98 on NetWare Networks

This section contains information about obtaining current Novell-supplied files and technical notes on the IPX/SPX-compatible protocol.

Obtaining Current Novell-Supplied Files

If your computer is not configured with the necessary NetWare software, or if you do not have the support files that Windows 98 Setup requires to configure your computer, several sources are available for these files.

Important Use the latest available version of Novell-supplied driver files. If the latest version of VLM does not work, use version 120.

To obtain current NetWare software files

Check with your NetWare network administrator or your local Novell representative to see if the latest client files are available locally.

– Or –

Over the Internet, obtain files from https://support.novell.com/ .

Required Support Files for Novell-supplied Clients

In addition to the base Novell-supplied NetWare client software required to communicate with a NetWare server, some additional NetWare support files are necessary for the Novell-supplied components to work properly in the Windows 98 environment. When Windows 98 is configured to support a Novell NetWare client, Setup checks to see if the required supporting files for Windows are in the \Windows directory. If the files are not in the \Windows directory, Setup asks for a disk or network drive location for these files.

The required Novell-supplied supporting files for NetWare connectivity under Windows are shown in Table 17.3.

Table 17.3 Novell-supplied files for Windows support

File	Description
Netware.drv, Netware.hlp	Windows-compatible network driver and associated help file to provide access to network redirector functionality from 16-bit applications. Notice that this must be the version 2.x WinNet16 driver for the NETX client. Also, the Novell-supplied version of Netware.drv for NETX is approximately 124 KB in size; for VLM, the size is approximately 144 KB or 162 KB, depending on the version.
Nwpopup.exe	NetWare messaging utility. Used to receive messages and alerts from a NetWare server.
Vnetware.386	Virtual device driver providing virtualization services for the NetWare redirector in the Windows environment and across virtual machines (VMs).
Vipx.386	Virtual device driver providing virtualization services for the NetWare IPX protocol for the Windows environment and across VMs.
Nw16.dll1	A thunk layer for passing 32-bit calls to 16-bit NETX APIs.

1 Required for VLM, but not for NETX.

Required Support Files for ODI Drivers

A computer using Novell-supplied ODI and the IPX/SPX protocol requires certain files, depending on whether you choose to keep the Novell-supplied client when installing Windows 98 on a NetWare network. Table 17.4 lists the required files.

Table 17.4 Required support files for ODI drivers with Novell-supplied client

Type of driver	Support files
Windows 98 drivers	Vnetbios.386
Novell-supplied NETX drivers	Ipxodi.com Lsl.com Netware.drv Netware.hlp Netx.exe	Nwpopup.exe Vipx.386 Vnetware.386 A network adapter driver, such as Ne2000.com.
Novell-supplied VLM drivers	Netx.vlm version 4.0 or later. VLM client supporting files, version 1.02 or later.
Windows 98 driver	Msodisup.vxd1 Ndis.vxd Nwlink.vxd Nwnblink.vxd Nwnet32.dll	Nwnp32.dll Nwredir.vxd Odihlp.exe Vnetbios.386
Novell-supplied drivers	Lsl.com A network adapter driver, such as Ne2000.com.

1 Msodisup.vxd is the ODI support layer that maps NDIS 3.1 and later protocols to an ODI driver, and Odihlp.exe is the real-mode stub that allows LSL to complete its binding process in real mode.

Search Mode with Windows 98 on NetWare Networks

Many applications, when started, also open a number of other files (such as overlay files and data files) that are used as application resources. To find these files, older NetWare-aware applications, such as the FILER version 3.x NetWare utility look for files in NetWare search drives in two ways:

Using the PATH environment to search for executable files.
Using a NetWare search path to find supporting files, such as required data files.

Under Windows 98, the search mode defines how files are found, depending on the network client you use, as described in Table 17.5.

Table 17.5 Search mode for NetWare networks

Client	Search mode
Client for NetWare Networks	Search from a drive mapped to the server where the utility is stored.
Novell-supplied Novell Client for Windows 95/98	Configured in the client's properties.
Novell-supplied NETX	Search from any local drive or any network drive.
Novell-supplied VLM	Search from any network drive. Cannot search from a local drive.

Technical Notes on Client for NetWare Networks

This section presents some technical issues you should be aware of when using Client for NetWare Networks, including a summary of configuration settings and required support files, and configuration notes, as well as notes about NetWare API support and running NetWare utilities with Client for NetWare Networks.

Summary of Settings for Client for NetWare Networks

Client for NetWare Networks does not require you to change any settings in Autoexec.bat, Startnet.bat, or Config.sys. However, it does modify some configuration files automatically. For information about configuration files that are modified automatically, see "Required Support Files for Client for NetWare Networks," later in this chapter.

Login.exe is not loaded from any configuration file. Windows 98 Setup removes this entry automatically. If you install Client for NetWare Networks over a real-mode client, Setup does not always remove references to the real-mode client from Autoexec.bat or another batch file. If either NETX or VLM is initialized from Autoexec.bat or another batch file, Client for NetWare Networks will not be loaded, and your computer might lock up. Therefore, you should remove real-mode clients before installing Client for NetWare Networks.

No real-mode drivers are needed if a network adapter driver appears in the list of installed components in the Network option in Control Panel.

Table 17.6 summarizes the minimum settings that you should see in the Network option in Control Panel after you install Client for NetWare Networks.

Table 17.6 Required network settings for Client for NetWare Networks

Network component	Configuration options
Client for NetWare Networks	If the computer will be downloading system policies or user profiles from NetWare servers, Client for NetWare Networks should be selected in the Primary Network Logon box. In the General properties for Client for NetWare Networks, Preferred Server should show the name of the NetWare server to be used for initial logon. If login scripts are used, the option that enables login scripts should be checked.
Network adapter	In the properties for the adapter, the driver type should be Enhanced mode (32 bit and 16 bit) NDIS.1
IPX/SPX-compatible protocol	In its Advanced properties, the Frame Type should be Auto, or 802.2 if you have problems connecting to a NetWare server. If any network applications at your site require support for NetBIOS over IPX, that option should be checked in the NetBIOS properties.

1 You can also specify 16-bit ODI drivers. You do not need to load such drivers from Config.sys or another configuration file.

Required Support Files for Client for NetWare Networks

Table 17.7 summarizes the support files required for Client for NetWare Networks. All of these files are found in the \Windows\System directory and are provided with Windows 98; no Novell-supplied components are required. For more information about these components, see Chapter 29, "Windows 98 Network Architecture."

Table 17.7 Required files for Client for NetWare Networks

File	Description
Netware.drv	Emulates a WinNet driver required by some NetWare-aware applications that check for this file, such as Lotus Notes. Notice that this file is supplied with Windows 98, and is not the same as the similarly-named Novell-supplied file and, therefore, does not support applications that make direct function calls to Novell's Netware.drv. (The Windows 98 version is approximately 2 KB in size.)
Nwlink.vxd	Provides the IPX/SPX-compatible protocol.
Nwlsproc.exe, Nwlscon.exe	Optionally, provides the 32-bit login script processor and console used by Client for NetWare Networks.
Nwnet32.dll	Provides common NetWare networking functions for the 32-bit network provider and print provider.
Nwnp32.dll	Provides access to NetWare network resources using Windows Explorer, Network Neighborhood, and so on. This 32-bit network provider for NetWare networks is the service provider interface to the Multiple Provider Router.
Nwpp32.dll	Provides the print provider interface to the print router in Spoolss.dll. This 32-bit print provider supports the ability to print to NetWare printing resources.
Nwredir.vxd	Provides a 32-bit file system driver (redirector) to support applications that use the NCP file sharing protocol.

1 These files are all supplied on the Windows 98 product disks. Netware.drv in this configuration replaces an identically named Novell-supplied file.

Tables 17.8 and 17.9 summarize entries that are changed automatically in configuration files when Client for NetWare Networks is installed with Windows 98.

Table 17.8 Configuration file deletions for Client for NetWare Networks

File	Deletions
Autoexec.bat	bnetx brequest emsnetx emsnet5 emsnet4 emsnet3 int2f ipxodi	ipx lsl msipx netbios net3 net4 net5 netx	odihlp odinsup startnet vlm xmsnet3 xmsnet4 xmsnet5 xmsnetxp
System.ini	[386enh] network= uniquedospsp= pspincrements= timercriticalsection= reflectdosint2a=	[Boot] network.drv=	[boot.description] network.drv=
Net.cfg	msipx	Protocol.ini	[nwlink$] DriverName=nwlink$ Frame_Type=4 cachesize=0 bindings=device driver(s) ; for adapters that support NDIS 2

The following list shows files that are renamed in the Windows and System directories when Client for NetWare Networks is installed. Files are renamed to file name.??~. (For example, the file Nwuser.exe is renamed to Nwuser.ex~.)

Nwuser.exe
Netware.drv
Netware.hlp
Nwgdi.dll
Nwpopup.exe
Vnetware.386
Vipx.386

Client for NetWare Networks Configuration Notes

This section presents some configuration notes for Client for NetWare Networks.

When Windows 98 attempts to connect to a NetWare server, it first silently tries to use the user's logon name and password to make the connection. If you use system policies, you can set a policy that turns off this behavior for Client for NetWare Networks. For information, see Chapter 8, "System Policies."
If you are running both the Client for NetWare Networks and the Client for Microsoft Networks, Windows NT logon scripts always run before NetWare login scripts.
Client for NetWare Networks is always bound only to the IPX/SPX-compatible protocol. This is the only protocol this network client can use. If you require an additional protocol for your network, such as TCP/IP, you must install an additional network client, such as Client for Microsoft Networks.

Notice, however, that you can install Microsoft TCP/IP to connect to the Internet without installing an additional network client.
With Client for NetWare Networks, you cannot map drives for individual virtual machine (VM) sessions; drive mappings are always global. This is the equivalent of the behavior specified in versions of Windows earlier than Windows 95 by the System.ini setting NWShareHandles=True (when using NETX or VLM). Notice, however, that with Client for NetWare Networks, each VM can have a different current directory on network drives, unlike versions of Windows earlier than Windows 95.
If you are using File and Printer Sharing for NetWare Networks, Config.sys should not have a LastDrive= statement.
The NWPopUp messaging utility is not supported with Client for NetWare Networks. You can use WinPopup to broadcast pop-up messages, as described in Chapter 14, "Introduction to Networking Configuration."

Additional Settings for Client for NetWare Networks

This section describes some additional settings that can be added to the registry for Client for NetWare Networks or for File and Printer Sharing for NetWare Networks. For information about how to add registry values, see Chapter 31, "Windows 98 Registry."

Setting maximum IPX packet size for the LIP protocol. You can set a global value for the maximum IPX packet size for the LIP protocol. To do this, add a registry entry named MaxLIP and specify a binary or DWORD value that is the greatest value allowed on any one network segment. The value should be a binary value entered in hexadecimal in reverse order. This global setting is also used on the local network. For example, if a client on a token-ring segment (which allows 4 KB packet sizes) communicates over an Ethernet segment (which allows 1.5 KB packets) to a server on another token-ring segment, the size specified for MaxLIP should be limited to the lowest packet size allowed.

Add MaxLIP as an entry under the following registry key:

Hkey_Local_Machine \System \CurrentControlSet \Services \VxD \Nwredir

To continue the earlier example, you would specify a value for 1.5 KB (0x000005DC in hexadecimal). The actual optimal value depends on theframe-header size, which is the IPX portion of the packet. You might want to experiment to get the right size, but in general, specifying a size that is too small is better than too large, because you want to make sure that the echo packet goes through on the first try.

Turning off support for packet-burst protocol. If you want to turn off support for the packet-burst protocol (which is enabled by default for File and Printer Sharing for NetWare Networks), set SupportBurst=0 in the following registry key:

Hkey_Local_Machine \System \CurrentControlSet \Services \VxD \Nwredir

Setting the shell version for OVL files. The versions of NetWare available for the United States that run on x86-based computers use Novell-supplied Ibm*.ovl (overlay) files to present the NetWare shell. This is the default assumed by Windows 98. However, other locales use other versions of OVL files to account for different architecture. For example, Table 17.10 shows the overlay files that NetWare 3.x J (for Japan) uses for various computer types.

Table 17.10 Overlay Files

Overlay file	Computer architecture
Pc98$run.ovl	NEC PC9800
Dosv$run.ovl	IBM PC-compatible
J31$run.ovl	Toshiba J3100
Fmr$run.ovl	Fujitsu FMR
Ps55$run.ovl	IBM Japan

For real-mode clients, alternate OVL files are specified in Net.cfg as the SHORT MACHINE TYPE. For Microsoft Client for NetWare Networks, you can specify alternate OVL files as the ShellVersion value in the following registry key:

Hkey_Local_Machine \System \CurrentControlSet \Services \VxD \Nwredir

The default value is MDOS\0V7.00\0IBM_PC\0IBM\0, where \0 indicates a binary zero (null value). This value represents the four concatenated strings returned by the INT 21 function 0xEA. You must replace the last string (0IBM) with the one used to generate the *$Run.ovl name. The value in the registry must have a binary type; however, you can enter the required combination of raw ASCII and binary data in the Enter Binary Data dialog box.

NetWare API Support in Client for NetWare Networks

Client for NetWare Networks includes built-in support for MS-DOS -based APIs defined by Novell for NetWare 3.x, as summarized in Table 17.11.

Table 17.11 APIs for MS-DOS

API for MS-DOS	Description
INT21H	Used by applications for NetWare information, bindery services, and so on.
INT64 and INT7A	Used by applications to submit IPX/SPX requests.

Client for NetWare Networks supports MS-DOS-based API calls documented in the Novell NetWare Client SDK. If problems occur with applications that make proprietary or undocumented API calls, then you should use a real-mode Novell-supplied client. Also, please report this problem to both Microsoft and the application vendor.

The Windows 3.x APIs for NetWare consist of a series of DLLs provided by Novell with the version 3.x WinNet16 driver for the VLM client. The 16-bit Novell-supplied DLLs for Windows can run with Client for NetWare Networks. This ensures that Windows-based applications and utilities that are NetWare-aware will run with Microsoft Client for NetWare Networks.

If any of your applications requires one or more of these DLLs when running on a real-mode Novell-supplied client (NETX or VLM), you must also run the same DLLs when using that application under Client for NetWare Networks. For example, you need the DLLs listed in Table 17.12 to run Novell's NWAdmin utility. You also need access to these files if you want to change passwords for a bindery server by using the Passwords option in Control Panel.

Table 17.12 NetWare dynamic-link libraries (DLLs)

API for Windows	Description
Nwcalls.dll	APIs for NCP communication between the file server and the client computer.
Nwgdi.dll	NetWare Graphical Device Interface.
Nwipxspx.dll	APIs for IPX/SPX communication.
Nwlocale.dll	APIs for localization of applications.
Nwnetapi.dll	Network API support for NDS.
Nwpsrv.dll	Print server services APIs.

Microsoft Service for NetWare Directory Services searches for these files in locations in the user's search path statement. If you put these files in a directory on a server, make sure the directory is in each of your users' search path statements. Microsoft recommends that you place these files in the SYS:PUBLIC directory of your users' preferred servers.

These Novell-supplied DLLs are not provided with Windows 98. They are provided by Novell with NetWare versions 3.12 and 4.x, and are updated on https://support.novell.com/ . To install these files, you must follow the directions provided in your Novell documentation. For information about obtaining the most recent files, see "Obtaining Current Novell-Supplied Files" earlier in this chapter.

Technical Notes on Novell Client for Windows 95/98

This section provides technical information about Novell Client for Windows 95/98. It describes the files Novell's Setup program copies to your computer and the changes the Setup program makes to system files. It also briefly discusses changes the Setup program makes to your registry.

File Locations

Setup.exe copies or creates the listed Client files into the folders shown in Table 17.13.

Table 17.13 Files copied during Novell Client installation

Folder	Files copied
\Novell\Client32	Client32.nlm Cmsm.nlm Cne2000.lan Cne3200.lan Ethertsm.nlm Fdditsm.nlm Ipx.nlm Loginw95.exe Lslc32.nlm Nios.log Nmr.nlm (if NMR is installed) NWIP95.NLM (if NetWare/IP is installed)	Nwpopup.exe Nwsipx32.nlm Pc32mlid.lan phasers.wav Readme.txt Setupnw.cnt Setupnw.hlp Spx_skts.nlm Sroute.nlm Tokentsm.nlm Vmlid.nlm
\Novell\Client32\Install	Admin.cfg Net2reg.log (created during install)	Nwlinks.exe Nwsetup.ini
\Windows\NLS\language1	Login.dat Login.msg
\Novell\Nwclient2	Driver.com Lsl.com N16odi.com Nesl.com	Net.cfg Route.com (if a token-ring driver)
\Windows\Help3	Loginw95.hlp Nwcfg95.hlp Nwover95.hlp Nwtips95.hlp Nwtsg95.hlp Nwuse95.hlp
\Windows\Inf	Ne1000.inf Ne15_21.inf Ne2.inf Ne2_32.inf Ne2000.inf Ne3200.inf Netdef.inf	Ntr2000.inf Nwclient.inf Nwip.inf Nwlayout.inf Nwserv.inf Nwtrans.inf Odinsup.inf
\Windows\NLS\language4	Novelnpr.dll
\Windows\System	Calwin16.dll Calwin32.dll Clnwin16.dll Clnwin32.dll Clnwinth.dll Clxwin16.dll Clxwin32.dll Lgnw9532.dll Locwin16.dll Locwin32.dll Ncpwin16.dll Ncpwin32.dll Netware.drv Netwin16.dll Netwin32.dll Nios.vxd Nioslib.dll Novellnp.dll Novpp32.dll Nwcalls.dll	Nwdrvlgo.bmp Nwgdi.dll Nwipxspx.dll Nwlink2.vxd Nwlocale.dll Nwnet.dll Nwpasswd.dll Nwpsrv.dll Nwrrnsp.dll Nwsetup.dll Nwshellx.dll Nwsipx32.dll Odiload.vxd Odinsup.sys Odipage.dll Prtwin16.dll Prtwin32.dll Tli_spx.dll Tli_win.dll

1 The name of this folder varies depending on the language being used. For example, for English, the folder name is ENGLISH.
2 Setup adds the following files to the NWCLIENT folder on workstations that use 16-bit ODI LAN drivers.
3 Each of these help files might also have files with the following file types associated with them: *.cnt ,*.fts*.gid.
4 The name of this folder varies depending on the language being used. For example, for English, the folder name is ENGLISH.

Changes to System Files

Table 17.14 shows the changes Novell Client installation makes to Windows 98 system files.

Table 17.14 Changes to Windows 98 system files

System file	Changes
Autoexec.bat	Removes lines that reference the following: IP NETX SERVER STARTNET VLM Removes the NWCLIENT folder from the SET PATH statement.
Config.sys	Removes LASTDRIVE=drive letter
System.ini	Adds the following lines to the [386Enh] section: NWHOMEDIR=[drive]\NOVELL\CLIENT32 FileSysChange=Off NWEnableLogging is a feature that logs status messages from the Novell Client. You can set the path and file name for the log from the Log File parameter in the Network Control Panel Advanced Settings page.
Netdef.inf	Sets the NetClient= line to NOVELL32.

Changes to the Windows Registry

Novell Client makes several changes to the registry. You can reverse these changes by removing the Novell Client software. The INF files document all changes Setup makes to the registry.

Technical Notes on Novell's NETX

This section provides technical information about using the Novell-supplied NetWare 3.x client software (NETX) with Windows 98.

When running NETX with Windows 98, you keep all the same functionality that you had when running NETX with MS-DOS, Windows 3.x, and Windows 95.

Using NETX with Client for MS Networks

If you are using NETX as the network client, you might also choose to install the 32-bit, protected-mode Client for Microsoft Networks if you want to connect to other Microsoft network computers, such as computers running Windows for Workgroups 3.x, LAN Manager, or Windows NT.

When you run the NetWare NETX client with Windows 98 in this configuration, you should continue to load the necessary Novell-supplied client components and MS-DOS- based TSR programs (LSL, ODI driver, IPXODI, and NETX) in Autoexec.bat or Startnet.bat, just as you did with MS-DOS, Windows 3.1, or Windows 95. Windows 98 Setup automatically adds the configuration settings if they are not present. For information about required configuration settings, see your Novell documentation.

You will need a Microsoft Windows NT Client Access license if the computer will be connecting to servers running Windows NT Server. For information, see Chapter 16, "Windows 98 on Microsoft Networks."

Figure 17.3 shows the architecture for this configuration. Novell-supplied components appear in bold.

Cc768187.wrk0y05(en-us,TechNet.10).gif

Figure 17.3 Architecture for Novell-supplied NETX with Client for Microsoft Networks

In this configuration, the Novell-supplied version of Netware.drv is installed and loaded only for applications that call it directly. Because this driver is not used by Windows 98, all access to NetWare resources occurs by using the Windows 98 user interface, not the Netware.drv dialog boxes provided by Novell. The Nw16.dll component translates 32-bit network calls to 16-bit network calls that can be passed to Vnetware.386.

Using NETX as the Sole Client

You might want to use NETX as the sole client if you do not need to connect to other computers running Windows for Workgroups 3.x, LAN Manager, or Windows NT.

If you use NETX as the sole client, you can still connect to computers running Microsoft File and Printer Sharing Services for NetWare.

To use only NETX client support, use the Network option in Control Panel to remove Client for NetWare Networks and Client for Microsoft Networks, if either of these clients is installed. Then add the Novell NetWare (Workstation Shell 3.x [NETX]) client, as described in "Installing or Upgrading a Real-Mode NetWare Client" earlier in this chapter.

Figure 17.4 shows the architecture for this configuration. Novell-supplied components appear in bold.

Cc768187.wrk0y06(en-us,TechNet.10).gif

Figure 17.4 Architecture for Novell-supplied NETX as the sole client

Table 17.15 lists the required settings for Config.sys and Autoexec.bat files if you use NETX as the sole network client.

Table 17.15 Configuration file settings for NETX as the sole network client

Filename	Required settings
Config.sys	lastdrive=*drive letter*
Autoexec.bat1	lsl.com *odi_driver* ipxodi.com netx.exe q: ; that is, lastdrive+1 login c:

1 Or this could be the name of a batch file called from Autoexec.bat.

Table 17.16 summarizes the minimum settings that you should see in the Network option in Control Panel if you use NETX as the sole network client.

Table 17.16 Network settings for NETX as the sole network client

Component	Options
NetWare (Workstation Shell 3.x [NETX])	Novell NetWare (Workstation Shell 3.x [NETX]) appears in the list of installed components. All other settings are configured in Net.cfg.
Network adapter	In the properties for the adapter, the Real mode (16 bit) ODI Driver option should be selected.
Novell IPXODI	Settings are configured in Net.cfg.

Setting the LastDrive Parameter for NETX

Windows 98 uses the value of the LastDrive= entry in the registry (or in Config.sys) to allocate enough storage space in the internal memory structures to recognize drive letters for devices. For example, a setting of LastDrive=Z tells Windows 98 to recognize drive letters from A to Z. Windows 98 uses all drive letters up to the letter assigned as the last drive.

In contrast, NETX clients can use only the drive letters following the last drive. For example, if you specify LastDrive=P, you will be able to map NetWare volumes only to drives Q-Z. This can cause problems if you have a setting of LastDrive=Z, because you will then have no drives available for mapping to NetWare servers.

NETX clients always use the drive letters following the drive specified in the LastDrive= entry, even if they are local drives. Also, when you install NETX, Windows 98 adds LastDrive=E to the registry. This can cause problems: for example, if you have a local drive F: and a network drive is mapped to F:, you will no longer be able to access the local drive. If this happens, you will need to modify the LastDrive= entry in Config.sys.

Setting Show Dots and File Access Limits

A NetWare file server does not include the directory entries dot (.) and double dot (..) as MS-DOS and Windows 98 do. However, the NetWare Workstation Shell client version 3.01 or later can emulate these entries when applications attempt to list the files in a directory.

To turn on the Show Dots feature

If you have problems listing files or deleting directories, add the following line to the beginning of Net.cfg:
```
show dots=on
```

By default, NetWare client software allows you access to only 40 files at a time. When you are running many applications under Windows 98, it is possible to exceed this limit, so you will want to increase the settings for file limits.

To increase the file access limit

Add the following line to the beginning of Net.cfg:
```
file handles=60
```

Add the following line to Config.sys for the local computer:
```
files=60
```

Technical Notes on Novell's VLM

VLM, the network client provided with Novell NetWare version 4.x, provides the same support and behavior under Windows 98 as it does under MS-DOS or Windows 3.1.

If the computer is using VLM, you should still load the Novell-supplied client components and TSR programs and log on from either Autoexec.bat or Startnet.bat. Logon scripts also work in the same way they do with MS-DOS, Windows 95, and Windows 3.x. After Windows 98 starts, you can use the Windows 98 user interface to make drive and printer connections, or you can run NetWare utilities by running NWUSER or other commands at the command prompt. Notice, however, that you cannot use NDS names in Windows 98 dialog boxes.

This section presents specific notes related to using the Novell-supplied NetWare 4.x client software with Windows 98.

Using VLM with Client for MS Networks

If you are using VLM as the network client, you might also choose to install the 32-bit, protected-mode Client for Microsoft Networks if you want to connect to other Microsoft networking computers, such as computers running Windows for Workgroups 3.x, LAN Manager, or Windows NT. Figure 17.5 shows the architecture for this configuration. Novell-supplied components appear in bold.

Cc768187.wrk0y07(en-us,TechNet.10).gif

Figure 17.5 Architecture for Novell-supplied VLM with Client for NetWare Networks

In this configuration, the Novell-supplied version of Netware.drv is not used by Windows 98. It is installed and loaded only for applications that call it directly. All access to NetWare resources is through the Windows 98 user interface, not the Netware.drv dialog boxes. The NWUSER utility calls Netware.drv directly to bring up the central NetWare Version 3.0 WinNet16 dialog box.

Notice that this configuration requires a Microsoft Windows NT Client Access License if this computer will be connecting to servers running Windows NT Server. For more information, see Chapter 16, "Windows 98 on Microsoft Networks."

Using VLM as the Sole Client

You can use VLM as the sole client if you do not need to connect to other computers that are running Windows for Workgroups 3.x, LAN Manager, or Windows NT. (If you use VLM as the sole client, you can still connect to a Windows 98 computer running Microsoft File and Printer Sharing for NetWare.)

Figure 17.6 shows the architecture for this configuration. Novell-supplied components appear in bold.

Cc768187.wrk0y08(en-us,TechNet.10).gif

Figure 17.6 Architecture for Novell-supplied VLM as the sole client

Table 17.17 lists the required settings for Config.sys and Autoexec.bat files if you use VLM as the sole network client.

File name	Required settings
Config.sys	lastdrive=*drive_letter*
Autoexec.bat	startnet.bat
Startnet.bat	lsl.com odi driver ipxodi.com vlm.exe f: ; that is, first network drive in net.cfg login c:

Table 17.18 summarizes the minimum settings that you should see in the Network option in Control Panel if you install Windows 98 with VLM as the sole network client.

Table 17.18 Network settings for VLM as the sole network client

Component	Options
NetWare (Workstation Shell 4.x [VLM])	Novell NetWare (Workstation Shell 4.x [VLM]) appears in the list of installed components. All other settings are configured in Net.cfg.
Network adapter	In the properties for the adapter, the Real mode (16 bit) ODI Driver option should be checked.
Novell IPXODI	Settings are configured in Net.cfg.

Setting the LastDrive Parameter for VLM

Windows 98 uses the value of the LastDrive= entry in the registry to allocate enough storage space in the internal memory structures to recognize drive letters for devices. For example, a setting of LastDrive=Z tells Windows 98 to recognize drive letters from A to Z.

The Novell-supplied NetWare 4.x redirector handles the LastDrive= entry the same way that Windows 98 does. That is, both the NetWare 4.x redirector and Windows 98 allow drive letters to be used to connect to redirected network drives up through the drive letter specified by the LastDrive= entry. For example, a setting of LastDrive=Z tells the NetWare 4.x redirector to recognize drive letters up through Z.

The NetWare 4.x redirector uses the First Network Drive= entry in the Net.cfg file to identify the first network drive that can be mapped. For more information about this setting, consult your Novell documentation.

Overview of Windows 98 on Other Third-Party Networks

In addition to its support for Novell's network clients, Windows 98 includes built-in support for 32-bit, protected-mode clients and for several types of 16-bit, real-mode network clients.

Tip for Using Protected-Mode Network Clients from Other Vendors

The network provider interface defines a set of APIs used by Windows 98 to access the network for actions, such as logging on to the server, browsing and connecting to servers, and so on. Microsoft has made this set of APIs widely available to network vendors so that they can develop new protected-mode network providers that are compatible with Windows 98.

For example, Windows 98 can support Microsoft networks, Novell NetWare, and Banyan VINES 32-bit connectivity at the same time through Network Neighborhood.

Multiple network support in Windows 98 consists of the following components:

Win32 WinNet API.
Multiple provider router and service provider interface.
Network providers, including the WinNet16 interface, as described in "Using Real-Mode WinNet16 Drivers" later in this chapter.

This section describes how to install and configure Windows 98 on third-party networks other than Novell NetWare. It discusses the following network software:

Artisoft LANtastic version 7.0 (client and server).
Banyan Enterprise Client version 7.32 and later.
Banyan VINES version 7.1 and later (a 16-bit, real-mode client).
Digital PATHWORKS 32 client.
IBM Networks Client for Windows 95.
Solstice NFS Client version 3.1 and later.

It also includes information about host (that is, mainframe) connectivity for Windows 98.

For information about the system components that provide multiple network support, see Chapter 29, "Windows 98 Network Architecture." For information about networking printing and support for printing when using a 16-bit network client, see Chapter 11, "Printing, Imaging, and Fonts."

Issues with Windows 98 on Other Third-Party Networks

Both protected-mode, 32-bit, and real-mode, 16-bit network clients are available for most network clients. You should use 32-bit, protected mode network clients whenever possible. Protected-mode, 32-bit clients offer the following benefits:

Easy installation and configuration using built-in Windows 98 tools.
Performance enhancements, such as Plug and Play networking support, long file names, client-side caching, and automatic reconnections.
Greater stability than with real-mode clients.
Ability to run additional 32-bit, protected-mode clients simultaneously.
Integration with the Windows 98 environment, including the Windows 98 unified logon, Network Neighborhood, and Windows 98 network management tools.

You should install 32-bit clients after you have finished Windows 98 Setup. If you have a 16-bit client on your computer before Windows 98 Setup, contact your network vendor for information about how to upgrade to the 32-bit clients.

Contact your network vendor for their latest installation INF file.

Note Be sure to read the Windows 98 Readme.txt, Setup.txt, and Network.txt notes on networking. Also check the Microsoft WinNews forums on online services for specific information about your network and about particular adapters.

Overview of Installing Support for Other Networks

This section gives an overview of installing both 32-bit clients and 16-bit clients, and it describes how to install Microsoft Client for Microsoft Networks after another network client has been installed.

Installing 32-bit Clients

You should install 32-bit clients after you have run Windows 98 Setup. For installation details related to your specific network, see the section for that network.

Installing 16-bit Clients

This section describes how to install Windows 98 16-bit clients from another vendor. For installation details related to your specific network, see the section for that network or contact your network vendor.

You can add real-mode, third-party support to Windows 98 in one of two ways:

Add network support before upgrading to Windows 98. In most cases, Setup retains networking components. (One exception is Novell NETX. For more information about upgrading Novell NETX, see "Installing or Upgrading a Real-Mode Novell Client" earlier in this chapter.) You should be sure that the network client is installed correctly under MS-DOS, Windows 3.1, Windows for Workgroups, or Windows 95.
Add network support after upgrading to Windows 98.

On most computers running multiple clients, Windows 98 Setup stores all real-mode networking components, including Protocol.ini, in the \Windows directory. (For computers running Novell's VLM, Windows 98 Setup stores these components in the Nwclient directory.) On computers running a real-mode client as the primary network, the networking components are left in place. The settings in Protocol.ini affect only real-mode NDIS drivers. Changing these values has no effect on protected-mode NDIS drivers. If you need to change settings in Protocol.ini, use the Network option in Control Panel whenever possible. For information about Protocol.ini entries, see Chapter 16, "Windows 98 on Microsoft Networks."

Note Microsoft does not support upgrading over any real-mode clients other than NETX, VLM, and Banyan VINES 7.1 or later. Consult the Network.txt file for more information about support boundaries for real-mode clients.

Installing Client for MS Networks with Other Networks

If you want to install the 32-bit, protected-mode Client for Microsoft Networks in addition to a network client from another vendor, and if the client is not already installed, follow these steps. For more information about configuring and using Client for Microsoft Networks, see Chapter 16, "Windows 98 on Microsoft Networks."

To install Client for Microsoft Networks after another client has been installed

After Windows 98 Setup, in Control Panel double-click Network.
In the Network dialog box, click Add. In the Select Network Component Type dialog box, double-click Client.
In the Select Network Client dialog box, click Microsoft in the Manufacturers list, and click Client for Microsoft Networks in the Network Clients list. Click OK.
Usually hardware detection detects the correct network adapter and selects the corresponding driver. If you must add a network adapter, follow the steps in Chapter 14, "Introduction to Networking Configuration."
In the Network dialog box, double-click the network adapter in the list of components. Verify the settings in the properties for the network adapter. Then click OK. For information, see Chapter 15, "Network Adapters and Protocols." See also the documentation for your network adapter to verify its software settings.

Setup automatically installs a protected-mode version of any protocol that the installed network clients are using. If you need to install another protocol, follow the steps in Chapter 14, "Introduction to Networking Configuration."
Shut down and restart the computer.

Using Real-Mode WinNet16 Drivers

In addition to multiple 32-bit Windows 98 network providers, Windows 98 can also support a single 16-bit WinNet driver. This is the basic configuration that must be used for a network product that does not offer a 32-bit network provider.

If the 16-bit network provider from another network vendor does not provide a browsing scheme, Network Neighborhood will be empty. This indicates that it is not a browsable network. You must use the Map Network Drive dialog box for network access. Also, notice that a drive connected through the Windows 98 user interface is accessible in all command prompt boxes. (However, it is accessible only from Windows 98 command prompt boxes, not when you reboot in MS-DOS mode.) A connection made at a command prompt, however, will be available in that command prompt box only and will not be available throughout the Windows 98 user interface.

Table 17.19 summarizes the components for the 16-bit, real-mode network drivers.

Table 17.19 Components for real-mode network drivers

Component	Description
Winnet16.dll	Provides a 32-bit to 16-bit thunk and translation between the 32-bit Windows 98 network provider interface and the 16-bit WinNet API.
Winnet16.drv	A 16-bit Windows 3.x network driver that provides a basic Map Network Drive dialog box.
Network.vxd (or .386)	A Windows 3.x virtual device driver that allows virtualized access to the real-mode network software for all virtual machines (including Winnet16.drv).
Real-mode network software	This can include proprietary network adapter drivers, protocol drivers, client (redirector), and network utilities loaded through Config.sys and Autoexec.bat (or another batch file).

Artisoft LANtastic 7.0

This section describes how to install Windows 98 with the protected-mode client and server for Artisoft LANtastic 7.0. Microsoft recommends that you do not use any earlier versions of Artisoft LANtastic.

If you want to run Windows 98 with Artisoft LANtastic for Windows 95, contact Artisoft at https://www.artisoft.com/ .

Note Real-mode versions of Artisoft LANtastic do not work with Windows 95. Also, If you are running Windows 98 Setup from a Windows for Workgroups computer that has a real-mode version Artisoft LANtastic, Setup will fail. You should remove the real-mode version of Artisoft LANtastic before running Windows 98 Setup.

Artisoft LANtastic 7.0 includes the following components:

A client component.
A server component.
The Artisoft NetBIOS protocol.
File and printer sharing.
Modem sharing, which enables several users to share one modem.
The Internet Gateway Server, which enables several users to share the same Internet connection.

You should install Artisoft LANtastic 7.0 after Windows 98 Setup is complete. You can also install LANtastic on Windows 95, and then upgrade to Windows 98.

Artisoft has patches and other program updates, which you should apply after installing Artisoft LANtastic. Contact Artisoft for more information.

Artisoft LANtastic can be run in conjunction with Client for Microsoft Networks and Client for NetWare Networks. However, in some cases you might not be able to get Artisoft LANtastic to work with non-Artisoft networking components. If so, disable multicast addressing on all computers running LANtastic. See the section "Correcting Problems with Other Third-Party Networks" later in this chapter, or contact Artisoft for more information.

LANtastic servers appear in Network Neighborhood and Windows Explorer. You can map to a network drive as you normally do. You can also use the LANtastic Custom Control Panel. However, network drive mappings made through the LANtastic Custom Control Panel will not show the universal naming convention (UNC) extension label when viewed through Explorer, My Computer, or the LANtastic Custom Control Panel utilities.

To install Artisoft LANtastic after Windows 98 Setup

If you have a previous real-mode version of Artisoft LANtastic, contact Artisoft for information about how to uninstall it.
Double-click the Setup.exe file provided by Artisoft.
Follow the instructions on the screen.

Note LANtastic Setup asks you for Msrrdir.vxd approximately 6 to 8 times. To move past this more quickly, click Skip File or Cancel at each prompt. The file is an Artisoft Modem Sharing component and has already been copied to its proper location, in your \Windows\System directory.
Restart the computer.
In the Start menu, click Programs and then click LANtastic 7.0. Follow the instructions on the screen. This sets up the LANtastic Custom Control Panel.

To configure Artisoft LANtastic

You configure most Artisoft LANtastic options from the LANtastic Custom Control Panel icon. You can also configure the LANtastic NetBIOS protocol from the Network option in Control Panel.

You can uninstall Artisoft LANtastic in one of two ways.

To uninstall Artisoft LANtastic completely

In Control Panel, double-click Network.
Remove all LANtastic components.
Click OK.
In Control Panel, double-click Add/Remove Programs.

This method is not recommended if you plan to reinstall Artisoft LANtastic later, because it also removes any security and share information you have set up.

To uninstall Artisoft LANtastic but preserve settings

Remove LANtastic by running LANtastic's setup utility. The setup utility detects the LANtastic components from the Network option in Control Panel and then asks you if you want to remove LANtastic from your system.

This method preserves your security and share information in case you want to reinstall later.

Banyan Enterprise Clients and Banyan VINES

Windows 98 can be installed and run with the following Banyan clients:

Banyan Enterprise Clients for Windows 95, protected-mode, 32-bit clients.
Banyan VINES 7.1 and later, real-mode, 16-bit clients.

You should run a protected-mode client rather than a real-mode, 16-bit client.

This section discusses how to run Windows 98 with Banyan Enterprise Client 7.32 or later and Banyan VINES 7.1 and later. For information about running Windows 98 with Banyan Enterprise Clients for Windows 95, contact Banyan.

If you are using a 16-bit client, Banyan VINES servers do not show up in Network Neighborhood or Windows Explorer. You must use the Map Network Drive dialog box in Windows 98 to connect to servers.

However, if you are using a Banyan Enterprise 32-bit client, you can view Banyan file and print services from within Network Neighborhood.

Banyan Enterprise Client 7.32 or later supports system policies, and Banyan Enterprise Client 8.02 or later supports user profiles. Refer to your Banyan documentation for more information.

Banyan Enterprise Clients

This section describes how to install, uninstall, and configure Banyan Enterprise Clients on Windows 98. For information about how to upgrade to Banyan Enterprise Client from real-mode versions of Banyan clients, contact your Banyan vendor.

Installing Banyan Enterprise Client on Windows 98

This section describes how to install and uninstall Banyan Enterprise Client.

To install Banyan Enterprise Client after Windows 98 Setup

In Control Panel, double-click Network.
On the Configuration tab, click Add.
In the Select Network Component Type dialog box, select Client.
Click Add.
In the Select Network Client dialog box, click Have Disk.
Enter the directory where your installation files are located, and then click OK.
Follow the instructions on the screen.

To uninstall Banyan Enterprise Client after Windows 98 Setup

In Control Panel, double-click Network.
On the Configuration tab, select Banyan Client for Windows.
Click Remove.
Select Banyan Vines Protocol for 95.
Click OK.
When prompted, reboot the computer.

Configuring Banyan Enterprise Client

Banyan Common Logon is enabled by default. If you want to disable it, you must do so from the Network option in Control Panel.

The following example shows a sample Autoexec.bat entry when Banyan Enterprise Client protected-mode network support is installed with Client for Microsoft Networks either as a primary network or as a secondary network:

c:\win95\system\bansvc

Table 17.20 shows Banyan system files and their functions.

Table 17.20 Banyan system files and functions

Primary Banyan system files	Function
Bancom.vxd	Banyan IP communications stack
Vinesifs.vxd	Network redirector
Bansvc.com	MS-DOS interface enabler
Vsnet32.dll	Net provider
Vnsprn32.dll	Print provider
Vnsapi32.dll	Banyan Toolkit API

Banyan VINES 16-bit Client

You should use the 32-bit clients Banyan Enterprise Client version 7.32 or later instead of the Banyan VINES 16-bit client. For information about the benefits of using 32-bit, protected-mode clients see "Issues with Windows 98 on Other Third-Party Networks" earlier in this chapter. Also, Banyan no longer supports the 16-bit client.

If you are already using the Banyan VINES 16-bit client and you want to upgrade to the 32-bit client, you cannot do so using Msbatch.inf. Instead, you should wait until after Windows 98 Setup to upgrade to the 32-bit client.

If you do choose to use the Banyan VINES 16-bit client, you should upgrade to version 7.1 or higher. Microsoft no longer supports versions lower than 7.1. You should upgrade before you run Windows 98 Setup.

To upgrade to version 7.1

Obtain a patch from Banyan and apply it to at least one Banyan server on your network.
Run Newrev to upgrade all the Banyan clients on which you will be installing Windows 98.
Run Windows 98 Setup.

Banyan can be installed as an additional 16-bit network client, and you can install 32-bit, protected-mode clients, such as Client for Microsoft Networks or Client for NetWare Networks.

Installing the Banyan VINES 16-bit Client

If you want to set up Windows 98 with Banyan VINES real-mode network client support on an Ethernet network, make sure that the Banyan VINES client is already installed and working under MS-DOS, Windows 3.1, Windows for Workgroups, or Windows 95 before you run Windows 98 Setup.

Note If you are running Banyan VINES with monolithic drivers, you must use the PCCONFIG utility provided by Banyan to change Banyan drivers to NDIS drivers. Make sure that the section name matches the driver name.

Configuring the Banyan VINES 16-bit Client

Tables 17.21 and 17.22 show the entries required in configuration files when Banyan VINES real-mode network support is installed with Windows 98, depending on whether Banyan VINES is installed as the primary network only (connecting to a Banyan server) or is installed with Client for Microsoft Networks. These entries are for NDIS drivers.

Table 17.21 Banyan VINES as primary network, using NDIS

Configuration file	Entries
Autoexec.bat	cd \*banfiles* ban ndisban ; ndtokban for token ring redirall netbind arswait z:login c: cd\
Config.sys	device=c:\*banfiles\protman.dos /i:c:\banfiles* device=c:\**banfiles\ndis2driver** eg: exp16.dos
Protocol.ini	[PROTOCOL MANAGER] drivername=protman$ [VINES_XIF] drivername=ndisban$ ; ndtokban$ for token ring bindings=MS$EE16 [MS$EE16] drivername=EXP16$ interrupt=5 ioaddress=0x300 iochrdy=late

Table 17.22 Banyan VINES with Client for Microsoft Networks

Configuration file	Entries
Autoexec.bat	c:\windows\net initialize cd \*banfiles* ban ndisban ; ndtokban for token ring redirall c:\windows\net start arswait z:login c: cd\
Config.sys	rem device=c:\*banfiles\protman.dos /i:c:\banfiles* rem device=c:\**banfiles\ndis2driver** eg: elnkii.dos
Protocol.ini	[NDISBAN$] ; NDTOKBAN$ for token ring drivername=NDISBAN$ ; NDTOKBAN$ for token ring bindings=ELNKII$ [NWLINK$] drivername=NWLINK$ frame_type=4 cachesize=0 bindings=ELNKII$ [NETBEUI$] drivername=NETBEUI$ lanabase=0 sessions=10 ncbs=12 bindings=ELNKII$
	[ELNKII$] drivername=ELNKII$ transceiver=external interrupt=2 ioaddress=0x280 maxtransmits=12 datatransfer=pio_word xmitbufs=2 [PROTMAN$] priority=ndishlp$ drivername=protman$ [NDISHLP$] drivername=ndishlp$ bindings=ELNKII$

DIGITAL PATHWORKS 32

This section describes how to install and run Windows 98 with the protected-mode client DIGITAL PATHWORKS 32. Digital Equipment Corporation (DEC) does not support any earlier versions of PATHWORKS, and it might not be possible to make earlier versions work with Windows 98.

DIGITAL PATHWORKS 32 is a set of communication software products that enables users and applications to connect to nodes on the network that are running the DECnet protocol. It includes the following components:

DECnet protocol and related utilities and APIs, including Windows Sockets 2 support.
LAT service.
VT Terminal emulation.
File transfer.
X server software.
Print services.
Remote access services including support for asynchronous links using digital data communications message protocol (DDCMP), support for Point-To-Point Protocol (PPP), and support for Microsoft Dial-Up Networking.

To install DIGITAL PATHWORKS 32 after Windows 98 Setup

Insert the PATHWORKS 32 compact disc into your CD-ROM drive.
If you have not disabled the Autoplay function, the CD-ROM Autoplay displays a banner window with several options. Click Install.

– Or –

If you have disabled the Autoplay function, double-click the executable file Autoplay.exe provided by DEC on the PATHWORKS 32 CD-ROM.
Follow the instructions on the screen.
After installing DIGITAL PATHWORKS 32, shut down and restart your workstation.

For information about uninstalling DIGITAL PATHWORKS 32, consult the Release Notes included in version 7.0a or later, or contact Digital Equipment Corporation.

IBM Networks Client for Windows 95

Users must be running Client for Microsoft Networks in order to take advantage of all the features that IBM Networks Client for Windows 95 offers. If users are running Client for Microsoft Networks alone, they can access non-secure shares on IBM OS/2 LAN Servers and IBM OS/2 Warp Servers. Using the IBM Networks Client for Windows 95 with Client for Microsoft Networks, they can also log on to IBM OS/2 LAN Servers and IBM OS/2 Warp Servers, access secure shares, and execute scripts.

Users can connect to servers using the Map Network Drive dialog box or the command prompt. Users can also browse OS/2 Warp Servers as long as those servers have been configured as browse masters. They can be configured as browse masters using the IBM Neighborhood Browser Enabler for OS/2 Warp Server, which is available from IBM.

Important Client for Microsoft Networks must be installed before you install IBM Networks Client for Windows 95.

To set up Windows 98 with IBM Networks Client for Windows 95 after Windows 98 Setup

Make sure that the Client for Microsoft Networks and other standard networking components are already installed.
Make sure that a NetBEUI or TCP/IP network protocol is installed.
In Control Panel, double-click Network, and then click Add.
In the Select Network Component Type dialog box, select Client, and then click Add.
In the Select Network Client dialog box, click Have Disk.
Enter the directory path where your IBM Networks Client for Windows 95 installation files are located, and then click OK three times. You must restart the computer for the changes to take effect.

Solstice NFS Client

Windows 98 can be installed and run with Solstice NFS Client version 3.1 and later. Solstice NFS Client uses the Microsoft TCP/IP network protocol for its network connection and can be supported as either the primary network client or as an additional 32-bit client.

The installation process consists of the following three procedures:

Installing and configuring Microsoft TCP/IP.

For information about how to install and configure Microsoft TCP/IP, see Chapter 15, "Network Adapters and Protocols."
Installing Solstice NFS.
Optionally, verifying the installation.

Note If you want to access NetWare servers, install Microsoft Client for NetWare Networks before installing the Solstice NFS Client.

To install Solstice NFS

Insert the Solstice Network Client compact disc into your CD-ROM drive.
If you have not disabled the Autoplay function, the CD-ROM Autoplay displays a banner window with several options. Click Install.

– Or –

If you have disabled the Autoplay function, at the command prompt type
```
<drive_letter>:\pcpro3\setup
```

where \<*drive\_letter*\> is the letter of your CD-ROM drive.

Click Next and follow the instructions on the screen. The installation program copies files from the compact disc to your computer and enters information into your system files.

Note During installation, Solstice Setup asks you which name service to use and lists Windows Default as the default. Do not change this configuration unless you are using an NIS server. If you are using an NIS server, contact your network administrator for configuration information.
After installing Solstice NFS, shut down and restart your computer. When the computer reboots, you can log on.

You can change your configuration later, from the Network option in Control Panel.

To configure Solstice NFS from the Network option in Control Panel

In Control Panel, double-click Network.
Click each Solstice component and then click the Properties button, to view its properties.
Make any necessary changes. For more information, contact Sun Microsystems.

After you have installed and configured it, make sure your configuration works properly.

To verify your configuration

Use the Ping utility to make sure you can connect to another computer on the network. If not, you have a problem with your TCP/IP configuration.
Use the Winipcfg utility to verify TCP/IP configuration information.
In Network Neighborhood, double-click the Entire Network icon, click the NFS Servers icon, and then select a remote computer to make sure you can browse it. If no remote computers appear, try adding a computer by following the procedure "To add NFS hosts to Network Neighborhood," later in this section.

For information about using the Ping and Winipcfg utilities, see the section "Troubleshooting TCP/IP" in Chapter 15, "Network Adapters and Protocols."

After you have installed and configured Solstice NFS, you will see the following new workgroups in Network Neighborhood:

NFS Automount Maps

This workgroup includes all the NFS Automount Maps on the network that have been predefined by the network administrator.
NFS Servers

This workgroup includes all the NFS hosts on your subnet and all other hosts on your network that you have added to Network Neighborhood.

To add NFS hosts to Network Neighborhood

In Network Neighborhood, double-click the Entire Network icon, and then click the NFS Servers icon.
In the File menu, select Add/Remove NFS Servers.

To uninstall Solstice NFS

In Control Panel, double-click Add/Remove Programs.
Click Solstice and then click Add/Remove.
When you are asked whether you want to completely remove the selected application, click Yes.
When you are asked whether you want to delete shared files, click No unless you know that no other program is using the files.
Click OK.

Host Connectivity and Windows 98

Host connectivity in this section refers to connecting to legacy IBM System 370/390-compatible mainframe computers, the mid-range IBM AS/400 computers, DEC VAX/VMS, UNIX, and HP 3000 computers. Host terminal emulation applications running in Windows 98 require network protocols to connect to their respective hosts.

The common network protocols used to support host connectivity include the following:

IPX/SPX. The IPX/SPX-compatible transport provided with Windows 98 is compatible with Novell NetWare IPX/SPX, and can be installed to support host connectivity using terminal emulation programs and gateways supporting an IPX/SPX interface.
NetBEUI. The NetBEUI protocol provided with Windows 98 supports a NetBIOS programming interface and conforms to the IBM NetBEUI specifications. It also includes performance enhancements related to NetBIOS 3.0. Microsoft NetBEUI can be installed on computers running Windows 98 to provide NetBIOS support for host connectivity using terminal emulation programs and gateways supporting a NetBIOS interface.
TCP/IP. The TCP/IP protocol provided with Windows 98 is a complete implementation of the most common and accepted protocol available. It allows connectivity between interconnected networks with different operating systems and hardware architectures, such as UNIX, IBM mainframes, and Microsoft networks. Usually, host connectivity with the TCP/IP protocol is provided using Telnet services, such as TN3270 connecting to legacy mainframes, TN5250 connecting to an IBM AS/400, and using gateways supporting a TCP/IP interface. Microsoft TCP/IP supports the Windows Sockets 2.0 interface.
Data Link Control (DLC). Windows 98 includes both a protected-mode DLC driver (Dlc.vxd), which supports 32-bit and 16-bit DLC applications, and a real-mode DLC driver (Msdlc.exe), which supports only 16-bit applications. It is used primarily to access IBM mainframe computers and Hewlett-Packard network-ready printers. Microsoft recommends that you use the protected-mode driver in most cases. However, some 16-bit DLC applications will work only with the real-mode DLC driver. For more information about applications that require the 16-bit DLC, see "Using 32-bit DLC for Connectivity" in Chapter 15, "Network Adapters and Protocols."

This section provides tips for using TCP/IP, terminal emulation applications, and gateways for connectivity.

For information about using Microsoft TCP/IP, Microsoft NetBEUI, the IPX/SPX-compatible protocol, and Microsoft DLC, see Chapter 15, "Network Adapters and Protocols."

Using TCP/IP for Host Connectivity

Many utilities and terminal emulation programs from other vendors allow direct communication with a mainframe or host computer using a TCP/IP protocol stack. The protected-mode version of Microsoft TCP/IP included with Windows 98 relies on the Windows Sockets version 1.1 or 2.0 interface. Any terminal emulation program or utility that you use to connect to a mainframe or host computer over Microsoft TCP/IP must support Windows Sockets 1.1 or 2.0. If the application does not support Windows Sockets 1.1 or 2.0, contact the application vendor to obtain a version that does; otherwise, do not use Microsoft TCP/IP.

If you want to connect to a host computer using Telnet or TCP/IP and you are running an application that emulates an IBM 3270 or 5250, or a DEC VT xx computer terminal, you can use Microsoft TCP/IP.

Some third-party TCP/IP stacks cannot be installed after Windows 98 Setup due to conflicts with Windows Sockets 2.0, which is installed with Microsoft TCP/IP. If you want to use a third-party TCP/IP stack with Windows 98, you should install it before running Windows 98 Setup. In almost all cases, this ensures that your third-party stack is successfully upgraded. If you do not do install the stack before running Setup, you can try restoring Windows Sockets 1.1, then installing the third-party TCP/IP stack. However, this method does not always work, and Microsoft does not support it. Also, if you restore Windows Sockets 1.1, you will not be able to use features, such as Quality of Service. For more information, see Chapter 15, "Network Adapters and Protocols."

To restore Windows Sockets 1.1

In Control Panel, double-click Add/Remove Programs.
On the Install/Uninstall tab, click Restore Winsock 1.1 Configuration, and then click Add/Remove.
When asked whether you want to restore your original configuration, click Yes.

Note Microsoft does not support using 16-bit TCP/IP stacks.

If your emulation software requires a TSR to communicate with another vendor's TCP/IP protocol stack, you must remove the TSR and reconfigure the emulation software for Windows Sockets in order to communicate using Microsoft TCP/IP in Windows 98. To determine the proper configuration with Windows Sockets, see the documentation for the emulation software.

For more information about TCP/IP, see Chapter 15, "Network Adapters and Protocols."

Using Terminal Emulation Applications

Terminal emulation applications offer several different connectivity options for connecting to an IBM System 370/390-compatible mainframe host, IBM AS/400, or DEC VAX computer. This section describes configuration and other issues related to using terminal emulation programs.

Connecting to a NetWare for SAA gateway. For most 32-bit terminal emulation applications, configuring Windows 98 with the Microsoft IPX/SPX-compatible protocol enables connectivity to a NetWare for SAA gateway or to any gateway supporting IPX/SPX connectivity. If you are using a token-ring network with source routing, use the Network option in Control Panel to make sure that Microsoft IPX/SPX-compatible protocol appears in the list of network components. In Advanced properties for the protocol, set the Source Routing property to a 16-entry cache size.

Connecting to a Windows NT SNA 2.0 or later server. Windows 3.x client software supports connectivity to a Windows NT SNA 2.0 or 2.1 server. The Windows NT 32-bit client for SNA should not be used; it was designed to work only with client computers running Windows NT Workstation.

Connecting to an IBM AS/400 with IBM PC Support software. You can use Windows 98 to connect to an AS/400 using the IBM PC Support software. To do so, configure the PC Support application for Basic Mode; do not use Extended Mode. If the PC Support application was configured to connect using DLC, make sure that Microsoft DLC or IBM Lan Support is already installed on the computer.

You can also use Windows 98 to connect to an AS/400 using the NetWare for SAA gateway and the IBM PC Support application. Configure the PC Support application for Basic Mode; do not use Extended Mode. The IBM-supplied Dos16m.386 file is not compatible with Windows 98.

If Windows 98 is configured to use the IPX/SPX-compatible protocol, then you must create a Winstart.bat batch file in the \Windows directory and add entries in this file to run Pcswin.com and Strnrtr.exe (the Novell-compatible router). If you encounter problems using the protected-mode IPX/SPX-compatible transport with the Novell-compatible PC Support router, then configure Windows 98 to use the Novell-supplied NETX or VLM client with IPXODI, as described in "Configuring Network Adapter Drivers for Real-Mode Novell Clients" earlier in this chapter.

For information about using TCP/IP with IBM 3270 terminal emulation, see "Using TCP/IP for Host Connectivity" earlier in this chapter.

Using Gateways for Connectivity

When your network uses a gateway to communicate with a host computer, the client computer running Windows 98 communicates with the gateway computer just as it does with any other computer on the network. The gateway computer translates requests from the client into a form that can be understood by the host, then communicates with the host, and returns the information to the client. In this configuration, the client computer can connect to the gateway using any protocol that the gateway supports. The gateway uses some form of the DLC protocol to communicate with the host.

Table 17.23 shows commonly used gateways and the supported operating systems.

Table 17.23 Commonly used gateways and supported operating systems

Gateway	Operating system
Microsoft SNA Server 2.0 or later	Microsoft Windows NT 3.x and later
NetWare for SAA	Novell NetWare server 3.x and 4.x
Attachmate Gateway 4.0 or later	MS-DOS Microsoft Windows NT 3.x and later
Attachmate IRMALAN SNA Gateway	MS-DOS

Many of the gateways in the preceding table have MS-DOS versions, which run only under MS-DOS, not under Windows. Windows 98 does not support running the MS-DOS-based gateways in a VM. For information about support for a particular gateway under Windows 98, contact your gateway vendor.

Troubleshooting Windows 98 on Third-Party Networks

This section presents troubleshooting tips for some common problems that might occur when using Windows 98 on third-party networks.

As a general troubleshooting step, you should upgrade to 32-bit clients whenever possible. You should also apply all the latest patches for your network software.

For information about general troubleshooting issues, see Chapter 27, "General Troubleshooting."

Important For the most current information about problems that might occur, consult the Relnotes.doc and Network.txt files included with Windows 98.

For more troubleshooting tips related to system logon and browsing on NetWare networks, and for information about File and Printer Services for NetWare Networks, see Chapter 18, "Logon, Browsing, and Resource Sharing."

Correcting Problems with Client for NetWare Networks

This section discusses some common problems that might occur while installing, configuring, or using Microsoft Client for NetWare Networks.

As a general troubleshooting step, make sure that the Netware.drv has a size of about 2 KB. If it is much larger, remove Client for NetWare Networks in the Network option in Control Panel, and then reinstall it.

Microsoft Service for NetWare Directory Services Installation over Novell Client for Windows 95/98 fails.

If you install Novell Client for Windows 95/98, the Novell setup program removes and renames the setup files Netdef.inf and Nwnds.dll, making it impossible to install Microsoft Service for NetWare Directory Services later. Follow the procedure outlined below to install Microsoft Service for NetWare Directory Services over Novell Client for Windows 95/98.

To install Service for NetWare Directory Services after installing Novell Client for Windows 95/98

In Control Panel, examine the list of installed components.
If present, remove the Novell Client for Windows 95/98 and all instances of the IPX 32-bit Protocol for the Novell Client for Windows 95/98, and then click OK. Windows 98 deletes Novell Client for Windows 95/98.
When prompted to reboot, do so.
Insert your original Windows 98 installation media.
Extract the files Netdef.inf and Nwnds.dll by using System File Checker. For information about System File Checker, see "Using System File Checker," in Chapter 27, "General Troubleshooting."
Reboot your computer.
Install Service for NetWare Directory Services by following the procedure in the section "Setting Up Microsoft Service for NetWare Directory Services" earlier in this chapter.

For more information, see Knowledge Base article 150925: "How to Uninstall Novell's 32-bit Client."

Upgrade from NETX to Client for NetWare Networks fails.

If you upgrade from NETX to Client for NetWare Networks without first logging on to a NetWare server, the Client for NetWare Networks installation might fail. Microsoft does not support upgrading over NETX before first logging on using Autoexec.bat (or a batch file called by Autoexec.bat). If your installation does fail, you can try one of the following fixes:

Change the frame type in the IPX/SPX-compatible protocol from Auto to the frame type in use on your network.
Verify that the correct preferred server is listed.

No network is available after Windows 98 starts.

Use the Network option in Control Panel to view a list of installed clients, protocols, and services. Verify that Client for NetWare Networks is installed and that the IPX/SPX-compatible protocol is in the list of installed components.

The login script does not run.

Make sure the correct preferred server is set and that Enable logon script processing is checked in the properties for Client for NetWare Networks.

Passwords do not work in NetWare 4.1 environment.

In a NetWare 4.1 environment, Microsoft Client for NetWare does not support passwords that use certain lowercase extended characters. Users must change their passwords to use all uppercase characters.

Cannot disable default password in Policy Editor.

Microsoft Service for NetWare Directory Services uses the Windows 98 logon password as the master password for both the bindery and the NDS tree logon attempts. You cannot disable this feature in Policy Editor. Instead, you must modify the DisableDefaultPassword registry entry with a value of 1 in the following registry location:

HKEY_LOCAL_MACHINE \System \CurrentControlSet \Services \NWNP32 \NetworkProvider

You are asked for a Windows 98 password and a NetWare password at each logon.

Client for NetWare Networks might ask you for a Windows 98 password after you log on to the network. This can happen if the user name and password for your NetWare preferred server differs from your Windows 98 password, because in some cases the password is not stored in the cache. You can solve this problem in either of two ways:

You can make the passwords the same for both the NetWare preferred server and Windows 98.
You can save the password in the cache by using "attach as" from the server's context menu.

NetWare servers cannot be found.

You might not be able to see NetWare servers if you are using an incorrect frame type for the servers. To ensure that you are using the correct frame type for the server, verify the frame type set in the Advanced properties for the IPX/SPX-compatible protocol in the Network option in Control Panel. You can switch the setting from Auto to the specific frame type used on the server.

Client for NetWare Networks supports NetWare 4.x bindery emulation. Be sure that the bindery context you set for your NetWare server directory includes the Windows 98 users who should have access to the servers. To view and set your bindery context on NetWare 4.x servers, load the SERVMAN NetWare Loadable Module (NLM) and then view and set the SET BINDERY CONTEXT parameter. Or, you can type set at the command prompt to view the miscellaneous SET parameters. For more information, see your NetWare 4.x server documentation. Client for NetWare Networks also supports NDS, if you are running Service for NetWare Directory Services. Be sure that you have specified the correct context for your NetWare 4.x servers. Also, be sure that you have set your preferred server to be a 4.x server in the NDS tree you are logging onto.

Access to NetWare servers is denied.

By default, Client for NetWare Networks uses the credentials provided for preferred server authentication to access other NetWare servers. To see files on NetWare servers for which you have access, synchronize your credentials on all the NetWare servers, using the Novell SETPASS command at the command prompt.

You cannot map drive to SYS volume in login script with Microsoft Service for NetWare Directory Services.

With Microsoft Service for NetWare Directory Services, if you are using a login script to map a drive to a SYS volume, the drive might not map correctly. You must edit your login script. Replace the following text

map n server\sys:

with

#MAP N server\sys

Cannot open Nwadmn3x.exe using Microsoft Service for NetWare Directory Services.

If you are using Microsoft Service for NetWare Directory Services and you try to open Nwadmn3x.exe, you will see the error message "This program has performed an illegal operation and will be shut down." To work around this problem, you should instead use Nwadmin.exe, the version of NetWare Administrator that gives you access to the NDS tree.

To install Nwadmin.exe

Install version 4.10.2 or later of Nwadmin.exe on the NetWare server. For information about how to install Nwadmin.exe, contact Novell.
Make sure that you have the required DLL files on the public folder from which you are running Nwadmin.exe. These DLL files are supplied by Novell.
Make sure that the Netware.drv file you are using is the one included with Microsoft Service for NetWare Directory Services.
Make sure that you have the latest DLL files from Nwdll2.exe in your Windows\System folder. Nwdll2.exe is supplied by Novell.

For more information, see Knowledge Base article 124712.

You cannot access NDS drives after making dial-up connection.

With Microsoft Service for NetWare Directory Services, you might not be able to access NDS drives from Windows Explorer after making a dial-up connection. To solve this problem, you can either connect to the drives using Network Neighborhood or modify your Dial-Up Networking connection.

To modify your Dial-Up Networking connection

From the Start menu, point to Programs, point to Accessories, and then click Dial-Up Networking.
In the Dial-Up Networking folder, right-click the connection.
Click the Server Type tab.
Clear the Log on to Network box.

Note Clearing the Log on to Network box on a Dial-Up Networking connection will prevent you from logging on to Windows NT and NetWare servers for that connection.

You experience problems opening files on NetWare 3.11 servers.

Programs that open a large number of files in rapid succession might not work properly on NetWare 3.11 servers. Also, you might have problems when opening a file in a folder for which you do not have file scan rights. To solve this, obtain the file Os2opnfx.nlm from Novell.

Passwords do not function in NetWare 4.1 environment.

If users have problems logging on to NetWare 4.1 servers, check that their passwords use only uppercase characters. Microsoft Client for NetWare does not support passwords that use certain lowercase extended characters.

Cannot print to NDS printers.

If you install Microsoft Service for NetWare Directory Services and your NDS printers appear to be offline, remove and reinstall Service for NetWare Directory Services.

Experience problems with Packet Burst.

You may experience dropped connections, decreased performance, or file copy fails if you are connecting to NetWare 3.12 and 4.01 servers and packet burst is turned on. Novell provides a fix for this problem. To solve it, download the file Pburst.exe from the Novell Web site https://www.novell.com/ .

Correcting Problems with Novell NetWare Clients

This section provides general troubleshooting steps for running a Novell-supplied client with Windows 98, then describes some common problems that might occur.

As a general troubleshooting step for Novell Client for Windows 95/98, try using NDIS drivers instead of ODI drivers, and make sure you are using the latest version of your ODI or NDIS driver.

As a general troubleshooting step for VLM, verify that your computer is not using the Netware.drv file version 3.10.96.201. One version of Netware.drv that is known to work is Netware.drv 3.03.94.280.

As a general troubleshooting step for NETX, verify that your computer is using the Netware.drv file 2.02 or later.

If necessary, restore this file from the Novell-supplied installation source. The following list provides other general troubleshooting steps.

Check the version numbers of all Novell-supplied NetWare workstation shell components, including IPX, NETX, VLM, LSL, IPXODI, and the ODI driver files. Make sure the latest versions are being used.

To get the version number for the Novell-supplied software you are using, run driver_name i or driver_name ? at the command prompt. For example, type netx i to get the version number for the Novell-supplied Net*.com or Net*.exe file.

If you are not using the latest software, upgrade as described in "Obtaining Current Novell-Supplied Files" earlier in this chapter.
Check for multiple instances of the NetWare files, specifically the ODI driver and Net.cfg. If there are multiple instances, remove all but the most recent version.
Verify that IPXODI is binding to the network adapter by running the NetWare NVER utility, using the same settings as Net.cfg and the same [link driver ODI_driver] name. If IPXODI is not bound to the network adapter, change the entries in Net.cfg to correct this problem.

The following section describes common problems that might occur.

You see Hardware Troubleshooting Agent with ODI drivers.

With versions of Novell Client for Windows 95/98 2.2 and earlier, if you upgrade Windows 98 over a Novell-provided 32-bit ODI driver, you might see the Hardware Troubleshooting Agent every other boot. Novell has solved this problem with an ODI update pack available from https://www.novell.com/ . For more information, contact Novell.

Network adapter drivers will not load with Novell Client for Windows 95/98.

TSRs that need to be loaded after a network connection is established or after IPX loads should be loaded from the Winstart.bat file. Otherwise, they will not load. If they fail to load, load the TSRs from the Winstart.bat file. If the file does not already exist, you can create it in the subfolder where Windows 98 is installed.

Novell Client for Windows 95/98 installation fails.

If the Novell Client for Windows 95/98 installation fails, make sure that all installation files have been placed in folders that conform to the standard MS-DOS 11-character (8.3) naming convention.

NetWare 4.11 server is missing DLL files needed for Nwadmn3x.exe.

You might have trouble opening Nwadmn3x.exe when you are using the Novell Client for Windows 95/98. You can solve this problem by in two different ways:

Run Install.nlm on the server and selecting the option that lets you install the legacy NWADMIN utility. This installs Nwadmin.exe on the server, which works as documented by Novell. Contact Novell for technical support for this procedure.
Use Nwunpack to expand the DLL files to a location in your MS-DOS path, such as a NetWare search drive or the \Windows\System directory. Do no overwrite existing DLL files. This procedure is not supported by Microsoft.

Setup requires Novell Workstation Shell Installation Program.

If, during installation, Setup fails to load Novell drivers and displays a message that it requires the Novell Workstation Shell Install Program for installing the VLM network client with Windows 98, follow the instructions presented in "Technical Notes on Novell's VLM" earlier in this chapter.

You cannot attach to the NetWare file server after installing Windows 98.

Verify the frame type being used by the NetWare server. If the NetWare server is using a different frame type from the one configured for the computer running Windows 98, the user cannot see the server. The Novell-supplied IPXODI protocol binds only to the first logical board, which is the first frame type in the link driver ODI_driver section in Net.cfg.

To correct this problem, manually edit Net.cfg so that the correct frame type is first in the link driver ODI_driver section.

You cannot see other computers running Windows 98 or NetWare servers.

Determine which frame type is used at your site, and then verify that the correct frame type you want to use on the network is listed in Net.cfg. The frame type that IPXODI will use must be first or must be set explicitly.
Verify that the correct Net.cfg is being processed by Lsl.com. To do this, check the local drive for other Net.cfg files. There should be only one, and it should be in the same directory as the NetWare driver files. If you are loading these files from Autoexec.bat or another batch file, modify the batch file to change to this directory, run the necessary ODI drivers, and change back to the directory you want. This ensures that the current directory is the same as the location of the Lsl.com file when it is being loaded.
Verify that Net.cfg contains the correct settings for the network adapter. If necessary, restore this file from a correct backup version, or edit it to include correct settings.
Verify that you are running the latest version of the Novell-supplied ODI drivers and support files. Check with your network adapter manufacturer to determine whether a newer ODI driver is available.
Verify that both client computers are running the same protocols. If the client computers are on different sides of a router, make sure that an IPX/SPX-compatible protocol is being used on both computers.

You cannot access the logon drive after installing Windows 98.

A common misconception is that users must log on to their NetWare server using the drive letter F. However, this is not true. For a client computer using the NETX workstation shell, the NetWare logon drive is the next drive letter available after the LastDrive= statement in Config.sys.

You can alter the LastDrive= statement to change the logon drive, but you must leave enough drives before the LastDrive= that Windows 98 can use for its own connections.

You see an error message after you install VLM support under Windows 98.

If a message says that the system cannot find a device file needed to run Windows, make sure that the VLM client has been installed using the Network option in Control Panel. To do so, double-click the Network option after running Setup. This step ensures that the correct VLM information is placed in System.ini.

The Windows directory contains Nwsysvol\Login\login.???.

This stub file is installed with File and Printer Sharing for NetWare Networks to prevent the computer from incorrectly responding as the preferred server for other NetWare clients.

You cannot connect to the network using TCP/IP when ODI drivers are installed.

If you are using a Novell NetWare ODI driver and you can use the Ping tool to ping your own computer, but you cannot access the network using TCP/IP, check to make sure that the Ethernet_II frame type is listed properly in Net.cfg. If not, add it.

To add the Ethernet_II frame type to Net.cfg

Use any text editor (such as WordPad) to open the Net.cfg file.

Note Make sure you edit the correct Net.cfg file. It is usually read from the same directory as Lsl.com.
Add Ethernet_II so that it is the last frame type listed in the LINK DRIVER <MLID> section.
Save and close the Net.cfg file.
Restart your computer.

Correcting Problems with Artisoft LANtastic

This section lists problems you might experience while using Artisoft LANtastic. As a general troubleshooting step, if you are using the 16-bit version, you should upgrade to the 32-bit version. This will solve most problems.

For the most current troubleshooting steps, see Relnotes.doc and Network.txt.

Installing Windows 98 disables LANtastic Internet Gateway Client.

If installing Windows 98 disables the LANtastic Internet Gateway Client, remove and reinstall LANtastic using LANtastic's setup utility.

Caution Do not uninstall LANtastic using Add/Remove Programs in Control Panel if you think you might reinstall LANtastic later. If you uninstall LANtastic using Add/Remove Programs, you will lose your user and resource settings.

You see a LANtastic Modemshare error during Windows 98 upgrade.

If you have LANtastic 7.0 installed on your Windows 95 computer and you upgrade to Windows 98, you might see a Modemshare error message stating that the modem is not responding. Press a key, and Setup continues normally. When Setup is finished, LANtastic Modemshare will work properly.

You cannot access files on LANtastic servers.

If LANtastic 7.0 uses your computer name for its file and printer sharing capabilities, you might have problems accessing files on the system if you also have File and Print Sharing for Microsoft Networks installed. To solve this problem, you can either change the name that LANtastic 7.0 uses for its server in the LANtastic Custom Control Panel, or change your computer name in the Network option in Control Panel.

You cannot see servers with LANtastic 7.0.

You may have problems seeing other computers on the network. If so, disable Multicast using the following procedure:

To disable Multicast

In Control Panel, double-click Network.
Double-click the Artisoft LANtastic NetBIOS protocol and then click the Advanced tab.
In the Property field select Multicast, and in the Value field select Off, and then click OK.

You must restart your computer for the changes to take effect.

Drives mapped to LANtastic shares appear without names.

When you map a drive to a LANtastic share, the drive name does not appear anywhere in the LANtastic or Windows graphical user interface. However, you can still use the mapped drive as you usually would.

You cannot disconnect mapped drives from within LANtastic utility.

If you map a drive to a LANtastic share, you will not be able to disconnect that mapped drive using LANtastic's Custom Control Panel utilities. You can still disconnect mapped drives using the Windows 98 user interface, by right-clicking the mapped drive in My Computer and selecting Disconnect.

You cannot print to a LANtastic network printer.

If you are using LANtastic 7.0 and you cannot print to a LANtastic network printer, you might need to change the properties for the network printer.

To change the printer's properties

In the Printers folder, right-click the printer's icon, and then select Properties from the context menu.
In the printer's properties, click the Details tab.
Examine the printer's name in the Print to the following port: box.
If the name uses a syntax similar to the following:
```
Port: \\Server\Share
```

change that syntax to the following: 

<pre IsFakePre="true" xmlns="https://www.w3.org/1999/xhtml">\\Server\Share

Correcting Problems with Other Third-Party Networks

This section lists problems you might experience while using a third-party network client. As a general troubleshooting step, if you are using a 16-bit client, you should upgrade to a 32-bit client. This will solve most problems.

For the most current troubleshooting steps, see Relnotes.doc and Network.txt.

You see a "Reinstall Windows" error message while installing 16-bit Banyan VINES client, or Windows constantly restarts.

If you are installing Windows 98 and the setup program is interrupted, you might see the error message "Cannot connect to Z:\Wnewrev.exe, you must reinstall Windows." During the installation program for the Banyan VINES 16-bit client, you might also encounter an error in which Windows 98 constantly restarts. If this happens you will need to edit your System.ini file.

To edit your System.ini file

Reboot your computer.
During startup, press the left CTRL key until the Microsoft Windows 98 Startup Menu message appears.
Select Safe mode command prompt only.
Open System.ini and change the entry Shell=Z:\Wnewrev.exe to read Shell=Explorer.exe.
Reboot the computer.

You see an error message asking you to run Newrev.

If you are installing the 16-bit Banyan VINES client and you do not install the latest version, you will see an error message stating that you are not running the latest VINES version and that you need to run Newrev. If this happens, type the following line from the Banyan subdirectory:

Newrev /I

This command copies the latest Banyan files to your local drive.

You cannot install Banyan VINES 16-bit Client with Msbatch.inf.

Windows 98 does not support the following lines in Msbatch.inf setup files:

Clients=vines552
Protocols=ndisban, ndistok

If you wish to install support for Banyan VINES networking, you must do so after Windows 98 setup is complete.

You cannot map a drive using Banyan VINES 16-bit client.

If you lose graphical user interface functionality for the Banyan VINES 16-bit client (for example, if you can no longer map a drive from within Windows 98 or view a previously mapped Banyan VINES drive), your path might be lost or corrupt. You must have Z:\ set to the end of their path. You can either do so from Autoexec.bat or ask a VINES administrator to place the path in the VINES login script.

You lose Windows functionality after overwriting Ver.dll during Banyan VINES 16-bit installation program.

The installation program for the Banyan VINES 16-bit client prompts you to overwrite the file Ver.dll. If you do so, you will lose Windows functionality such as printing or using the Control Panel. To restore Windows functionality, manually extract Ver.dll from your original installation media and add it to your \Windows and \Windows\System directories. For information about how to manually extract files, see Knowledge Base Article 129605, "How to Extract Original Compressed Windows Files."

Third party TCP/IP stack does not work with Windows Sockets 2.

Many third-party TCP/IP stacks, such as FTP Software's OnNet32 TCP/IP stack, do not support Windows Sockets 2. If you want to use one of these stacks with Windows 98, you should install the TCP/IP stack before installing Windows 98. In some cases, you can also remove Windows Sockets 2 after upgrading to Windows 98, then install the third-party stack. However, this second method does not always work.

Note that if you install the third-party TCP/IP stack before installing Windows 98, Windows Sockets 2 will not be installed. For information about removing Windows Sockets 2, see Chapter 5, "Setup Technical Discussion."

Samba server does not accept your password.

For security reasons, Windows 98 no longer allows you to send plain text passwords. It sends only encrypted passwords. However, Samba servers require plain text passwords, so you will not be able to connect to Samba servers unless you change a registry entry to enable plain text passwords.

Caution Enabling plain text passwords will decrease your computer's security.

To enable plain-text passwords, add the registry entry EnablePlainTextPassword (as a Dword) and set the value to 1 in the following registry location:

HKEY_LOCAL_MACHINE \System \CurrentControlSet \Services \VxD \Vnetsup

Additional Resources

For more information about	See this resource
Any third-party networking product	Your network vendor's documentation
Artisoft products	https://www.artisoft.com/
Digital Equipment Corporation (DEC) products	https://www.digital.com/
IBM products	https://www.ibm.com/
Novell products	https://www.novell.com/
Microsoft products	https://www.microsoft.com/
Sun products	https://www.sun.com/

Chapter 17 - Windows 98 on Third-Party Networks

See Also

Overview of Windows 98 on Third-Party Networks

Overview of Windows 98 on NetWare Networks

Planning for Windows 98 on NetWare Networks

Choosing the Network Client

Issues with MS-supplied NetWare Clients

Issues with Novell-supplied NetWare Clients

Choosing Protocols on NetWare Networks

Setting Up Windows 98 for NetWare Networks: An Overview

Configuring NetWare Servers to Support Windows 98

Installing Windows 98 Source Files on NetWare Servers

To set up Windows 98 source files on a NetWare server

Automating Setup for NetWare Workstations

Supporting Long File Names on NetWare Servers

To enable long file names on NetWare servers running versions 4.10 or earlier

To enable long file names on NetWare servers running versions later than 4.1x

To verify that long file names have been added

Supporting Pass-Through Security for Peer Resource Sharing

Placing Profile and Policy Files on NetWare Servers

Installing and Configuring MS Client for NetWare Networks

Setting Up MS Client for NetWare Networks

To add Client for NetWare Networks after installing Windows 98

Setting Up MS Service for NetWare Directory Services

Adding MS Service for NetWare Directory Services after Installing Windows 98

To add Microsoft Service for NetWare Directory Services after installing Windows 98

Automated Installation of MS Service for NetWare Directory Services

To include the Service for NetWare Directory Services in an automated installation

Configuring MS Client for NetWare Networks

Configuring Protected-Mode NDIS Network Adapter Drivers for Client for NetWare Networks

To switch to a 32-bit, protected-mode network adapter driver

Configuring Client for NetWare Networks with ODI Network Adapter Drivers

To use ODI drivers with Client for NetWare Networks

Running NetWare Utilities with Client for NetWare Networks and MS Service for NetWare Directory Services

To run NetWare utilities from an MS-DOS prompt

To run NetWare utilities from Network Neighborhood

Installing and Configuring Novell NetWare Clients

Removing Incompatible Software

Preparing NetWare servers for the Installation

Installing Novell Client for Windows 95/98

Removing Novell Client for Windows 95/98

Configuring Network Adapter Drivers for Novell Client for Windows 95/98

Installing or Upgrading a Real-Mode Novell Client

Installing Windows 98 with ODI Drivers

To configure the network adapter driver manually

Verifying Drivers for Real-Mode Clients After Windows 98 Setup

To determine whether the correct adapter driver is installed after Windows 98 Setup

Upgrading Windows 98 with VLM

To retain VLM during Windows 98 upgrade

Installing VLM for the First Time After Windows 98 Setup

To install VLM after Windows 98 Setup

Upgrading Windows 98 with NETX

To select Novell-supplied NETX client support during Windows 98 Setup

To reinstall NETX after Windows 98 Setup

Configuring Network Adapter Drivers for Real-Mode Novell Clients

Configuring Windows 98 with ODI Drivers

Setting Network Adapter Options in Net.cfg

Technical Notes for Windows 98 on NetWare Networks

Obtaining Current Novell-Supplied Files

To obtain current NetWare software files

Required Support Files for Novell-supplied Clients

Required Support Files for ODI Drivers

Search Mode with Windows 98 on NetWare Networks

Technical Notes on Client for NetWare Networks

Summary of Settings for Client for NetWare Networks

Required Support Files for Client for NetWare Networks

Client for NetWare Networks Configuration Notes

Additional Settings for Client for NetWare Networks

NetWare API Support in Client for NetWare Networks

Technical Notes on Novell Client for Windows 95/98

File Locations

Changes to System Files

Changes to the Windows Registry

Technical Notes on Novell's NETX

Using NETX with Client for MS Networks

Using NETX as the Sole Client

Setting the LastDrive Parameter for NETX

Setting Show Dots and File Access Limits

To turn on the Show Dots feature

To increase the file access limit