Copyright: Copyright © Novell, Inc.


$Version and Copyright Notices
Version and Copyright Notices

The following text strings are included to enable the NDIR utility to report version and copyright information for this Help file. This topic should not be translated, except for possibly the actual version and copyright strings below (if these are also translated).

VeRsIoN=Version 2.5

CoPyRiGhT=(c) Copyright 1997, Novell, Inc. All rights reserved.


32-Bit LAN Driver Parameters

32-bit ODI* LAN drivers do not use NET.CFG for configuration parameters. Type configuration parameters on the load line. Most ISA drivers require at least the following parameters:

FRAME=frame_type

IRQ=interrupt

PORT=number

Example:

LOAD CNE2000.LAN FRAME=Ethernet_802.2 IRQ=3 PORT=300

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Add Local Device for Host MIB

The Host MIB agent reports inventory information for the workstation to an SNMP management console. Because DOS does not keep track of local devices such as printers, modems, and tape drives, the Host MIB agent relies on user input to describe these items.

Enter the name of the printer, modem, or tape drive physically attached to your workstation. Settings are kept in the Host MIB section of NET.CFG.

To add a device:

1.	Select the type of device

2.	Type in the device name.

3.	Click "OK".

The device name is displayed in the Devices field in the Configure Host MIB (1 of 2) dialog box.


Add Trap Target Addresses
Add Trap Target Addresses Dialog Box

To add a device:

1.	Select the type of device

2.	Type in the address in the appropriate format.

3.	Click OK.

The address is displayed in the in the corresponding list box in the Configure SNMP (2 of 2) dialog box.


Adding Search Paths
Add New Search Path Dialog Box

This dialog box allows you to specify the path to a directory you want included in Host MIB inventory scans. You need to type a specific path only if the directory you want to scan is deeper in the directory structure than the number indicated in the Maximum Directory Levels to Search from Root field.

1.	In the New Search Path box, type the path to the directory you want the Host MIB agent to inventory.

Note:  You can search all subdirectories by typing "\*.*" after the directory name. For example, the path "C:\WINDOWS\*.*" makes the Host MIB agent search all subdirectories below the WINDOWS directory.

2.	Click OK.

Resources

Overview of SNMP and Host Resources MIB

Configuring SNMP

Listing Devices for Host MIB

Desktop SNMP Section (NET.CFG)

Configuring Additional Options


Adding a New Modem to the Database

Adding a New Modem/Bus Adapter to the Database

Adding a New Model for an Existing Manufacturer

Adding a New Manufacturer and Model

Optimization Contents


Changes Setup Makes to All Clients
Changes Made During Client Software Installation

This topic explains what happens during installation of the IntranetWare* Client* on a client workstation. Depending on whether any or all of the optional components were selected, not all the following will apply on every client workstation.

When you install the IntranetWare Client, a temporary directory is created on the disk you are installing to and files are copied there. The required final directories are created (if they do not already exist) and the software is copied to these directories. In addition, various configuration files are created or updated and changes are made to the Windows** interface.

User Interface Additions

An IntranetWare Client program group is created in the Windows 3.x Program Manager. The name of the group is determined during installation.

IntranetWare Client Directories

SETUP.EXE searches for an existing IntranetWare client. If it finds one, it sets the directory containing the existing client as the destination directory for the IntranetWare Client for DOS/Windows 3.x. Otherwise, it creates C:\NOVELL\CLIENT32 as the destination (working) directory.

A number of subdirectories are created:

DATA, containing the Phone Book files

MODEMS, containing modem .INI and .ISD files

PROFILE, containing the LOCATION.INI file and a subdirectory for each location.

README, containing the release notes

TCP, containing the TCP/IP configuration files

NLS\language directory containing language-specific files.

Note:  If you install Netscape, the subdirectory BROWSER is created, which contains the Novell* Netscape** Navigator** files.

Configuration Files

Within these directories (and other directories -- see the Related Topics) a number of configuration files are created and updated. Normally, you do not need to edit any of these configuration files.

AUTOEXEC.BAT File

A line is added to the end of the AUTOEXEC.BAT file to run STARTNET.BAT:

@CALL drive:\client_home_dir\STARTNET.BAT

The Client working directory is added to the PATH variable in the AUTOEXEC.BAT file.

NET.CFG File

If the workstation has a NET.CFG file, the NET.CFG is copied to directory for the current location profile and the following changes are made:

If the workstation uses a 16-bit driver, the Link Driver section of the NET.CFG file is added or edited.

The following two lines are added to the NetWare* DOS Requester* section:

FIRST NETWORK DRIVE = F

NETWARE PROTOCOL = NDS BIND

Sections in NET.CFG are added or edited based on the configuration information the user supplies during installation.

Related Topics

Changes SETUP.EXE makes to Windows Software

Windows Configuration Files

Changes SETUP.EXE makes to TCP/IP Software

Changes SETUP.EXE makes to SNMP Software

Changes SETUP.EXE makes to TSA Software

DOS Configuration Files

Location Configuration Files

Administrator Snap-in Files

NetWare Mobile for Windows 3.x Phone Book Entries

What Happens During Installation

Uninstalling the IntranetWare Client Software

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Changes Setup Makes to SNMP Software
Changes SETUP.EXE Makes to SNMP Software

System Files

The Desktop SNMP section in NET.CFG is added or edited. If the workstation also runs support for Host MIB, a Host MIB section is added to NET.CFG.

The following lines are added to STARTNET.BAT to load the SNMP NLM* programs:

LOAD drive:\client_home_dir\SNMP.NLM

LOAD drive:\client_home_dir\SNMPIPX.NLM

LOAD drive:\client_home_dir\SNMPUDP.NLM

Related Topics

Overview of SNMP and Host Resources MIB

Configuring SNMP

Configuring Host Resources MIB

Desktop SNMP Section (NET.CFG)

Configuring Additional Options

What Happens During Installation

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Changes Setup Makes to TCP/IP Software
Changes SETUP.EXE Makes to TCP/IP Software

General Changes

All instances of WINSOCK.DLL and WLIBSOCK.DLL in the Windows** root and Windows SYSTEM directories are renamed by changing the .DLL extension to .OLD.

WINSOCK.DLL and WLIBSOCK.DLL are installed to the Client working directory (by default, NOVELL\CLIENT32).

System Files

The Protocol TCPIP section in the NET.CFG file is added or edited.

The following lines are added to the RESOLV.CFG file:

DOMAIN domain_name_entered

NAMESERVER address_entered

Note:  If RESOLV.CFG is not already on the workstation, SETUP.EXE creates the file in the TCP directory of the Client working directory.

The following line is added to in STARTNET.BAT to load the TCP/IP NLM:

LOAD drive:\client_home_dir\TCPIP.NLM

NetWare/IP

The following line is added to STARTNET.BAT to load the NetWare/IP* NLM* program:

LOAD drive:\client_home_dir\NWIP.NLM

Related Topics

Overview of TCP/IP and NetWare/IP

Configuring TCP/IP

Protocol TCP/IP Section (NET.CFG

NetWare/IP Section (NET.CFG)

Configuring Additional Options

What Happens During Installation

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Changes Setup Makes to TSA Software
Changes SETUP.EXE Makes to TSA Software

System Files

The NetWare* DOS TSA section in NET.CFG is added or edited and includes the following parameters:

TSA Server Name, Password, Disk Buffers, Drives

The following line is added to STARTNET.BAT to load the workstation TSA:

drive:\client_home_dir\TSASMS.COM

Note:  This line loads a TSR (under 10 KB, depending on the Disk Buffers parameter) that communicates with SBACKUP.NLM on the SMS* server.

Related Topics

Overview of TSA for SMS

Configuring TSA for SMS

NetWare DOS TSA Section (NET.CFG)

Configuring Additional Option

What Happens During Installation

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Changes Setup Makes to Windows Software
Changes SETUP.EXE Makes to Windows Software

This topic describes the changes made when you install the IntranetWare* Client* for DOS/Windows software. Other changes might occur depending on the optional components you choose to install.

Files and Directories

Files to the Windows** SYSTEM directory (normally C:\WINDOWS\SYSTEM).

IntranetWare* files are deleted from the Windows root directory.

Unicode tables are copied to the winroot  \NLS directory.

Program Manager

SETUP.EXE creates a group file (NW.GRP) called NetWare Tools that contains icons for NetWare User Tools and NetWare Login and adds the following line to PROGMAN.INI:

GROUP# =C:\WINDOWS\NW.GRP

WIN.INI

The following line is added to the [Windows] section of the workstation's WIN.INI file:

Load=NWPOPUP.EXE

SYSTEM.INI

All instances of "*DOSNET," "VTCPIP.386," and "VIPX.386" are removed from the Network= line of the [386 Enh] section.

All instances of "Device = VTCPIP.386" are removed from the [386 Enh] section.

The Network= line is modified in the [386 Enh] section to include "VNETWARE.386."

If installing a 16-bit ODI LAN driver, the following line is added to the [386 Enh] section:

device = VLANINT.386

SETUP.EXE makes the following changes to Windows for Workgroups 3.11 clients:

The following line is added to the [boot] section:

secondnet.drv = netware.drv

The following line is added to the [boot.description] section:

secondnet.drv = Novell NetWare (4.0)

SETUP.EXE makes the following changes to clients running Windows 3.1 (not WFW 3.11):

The following line is added to the [boot] section:

network.drv = netware.drv

The following line is added to the [boot.description] section:

network.drv = Novell NetWare (4.0)

Related Topics

Changes Made during Client Software Installation

Changes SETUP.EXE Makes to TCP/IP Software

Changes SETUP.EXE Makes to SNMP Software

Changes SETUP.EXE Makes to TSA Software

What Happens During Installation

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Choose Destination Directory
Choose Destination Directory Dialog Box

This dialog box allows you to specify the directory for the IntranetWare* Client* program files.

Accept the default C:\NOVELL\CLIENT32 unless you already have a version of the IntranetWare Client installed in a different directory on your workstation. In this case, use that directory instead.

To change the default directory:

1.	Select the text box and type in the directory where you want client files installed.

2.	Click Next to go to the next dialog box.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Choose First Network Drive
Choose First Network Drive Dialog Box

This dialog box allows you to specify your first network drive. The default is F: unless another device is already using it.

Specify the first drive letter that is not used by any other device, such as a CD-ROM. The drive you specify will contain your login commands to enable you to log in to the network. It also specifies the first drive you can start mapping network drives to. For example, if you specify F: as your first network drive, you can map network drives to any drive letters from F: to Z:.

To change the default first network drive:

1.	Use the drop-down list to select the drive letter you want to use as your first network drive.

2.	Click Next to continue to the next dialog box. (Click Previous to go back to the previous dialog box.)

You can exit SETUP.EXE at any time by clicking Exit Setup.


Choose Optional Modules
Choose Optional Modules Dialog Box

This dialog box allows you to select the optional modules of the IntranetWare* Client* to install.

Select the check boxes of those modules you require. Then click Next.

Novell Dial-in Services

Installs the Remote Access Dialer. Select this option if you want to dial in to the network or if you require more than one configuration for your LAN connection.

Novell IP Gateway

Installs support for NetWare/IP*. You should install NetWare/IP only if you use applications that require IPX* across a network that requires IP.

Novell Target Service Agent

Installs NetWare* Target Service Agent (TSA) support for Storage Management Services* (SMS*). TSA software enables SMS to back up client workstations on diverse operating systems. If you have an SMS server, you can back up information on the workstation to the SMS server by installing the TSA for SMS support.

SNMP and Host MIB

Installs Simple Network Management Protocol (SNMP), a cross-protocol language that allows network supervisors to manage computers across diverse network platforms.

If the management console supports Management Information Base (MIB) files, you might also want to load Host Resources MIB support on the client workstation. Host Resources MIB support enables the management console to poll the workstation for inventory information.

Novell Distributed Print Services

Installs NDPS*. NDPS is a distributed print service for networked environments providing comprehensive management and control of printers from multiple vendors through a graphical interface.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Choose Program Group Name
Choose Program Group Name Dialog Box

This dialog box allows you to select which Windows** program group you want the IntranetWare* Client* software installed to. SETUP.EXE creates the specified program group and installs the program icons into it.

The default program group is displayed as IntranetWare Client. However, you can select from the list of all your existing program groups or enter a new program group name.

To change the default group name:

1.	Select the text box and type in the name.

2.	Click Next to go to the next dialog box.

You can click Previous to go back to the previous dialog box or exit SETUP.EXE at any time by clicking Exit Setup.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Choosing a Hardware Interrupt

In most cases, you can use IRQ3 or IRQ5 for your network board if these are not already used by COM2 and LPT2. If neither IRQ3 nor IRQ5 is available, see the manufacturer’s documentation.

Note:  If you specify an interrupt for the network board that is already being used by another device, you can still install the network board but the network software will not run successfully.

The following table shows the IRQ settings that are commonly used by other devices, and the settings that might be available.

IRQ	Device
0	Timer output 0
1	Keyboard
2	EGA/VGA
3	COM2
4	COM1
5	LPT2
6	Diskette
7	LPT1
8	Real time clock
9	Available
10	Available
11	Available
12	Available
13	Co-processor
14	Hard disk
15	Available
Related Topics

Choosing an ODI LAN Driver

Installing Unlisted LAN Drivers

Configuring the LAN Driver

Modifying Driver Settings


Choosing an Input/Output Port

The base input/output port is a channel used by the network board to transfer information to the CPU. Each hardware device included in your client workstation must have a different base I/O port setting. For more information, see the manufacturer’s documentation.

The following table shows a list of standard I/O ports and the devices that commonly use them. If a workstation does not have any one of these devices, the I/O port given in the table for that device might be available for other use.

I/O Port	Device
1F0	AT* disk controller
200	Game controller/joystick (200-20F)
220	Novell* network keycard
240	Available
260	LPT2 (278-27F)
280	LCD display on WYSE* 2108 PC
2A0	Available
2C0	Available
2E0	COM4 GPIB-Adapter 0 (2E1); COM2 Information collection from external devices
300	Available
320	XT* hard disk interface
340	Available
360	LPT1 (378-37F)
380	SLDC/Sec BiSync interface (380-38C)
3A0	Primary BiSync interface (3A03A9); Monochrome display (3B0-3BB)
3C0	EGA display control (3C0-3CF); CGA display control (3D0-3DF)
3E0	COM3 (3E8-3EF); Diskette controller (3F0-3F7); COM1 (3F8-3FF)
Related Topics

Choosing an ODI LAN Driver

Installing Unlisted LAN Drivers

Configuring the LAN Driver

Modifying Driver Settings

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Choosing an ODI Driver

Use the ODI Driver Selection dialog box to specify the ODI* LAN driver your network board uses.

To specify an ODI LAN driver:

1.	Select 32-bit or 16-bit to specify the type of driver you want to use.

32-bit drivers improve the client's speed and reliability over 16-bit drivers. You should use the 32-bit driver if one is available for your LAN board.

2.	Select the driver you want to use.

If the name of the driver you want to use appears in the Board list, select it from the list.

If the driver does not appear in the list, select a different driver type (16-bit or 32-bit) and look again for the driver.

If the board you want to set up is not listed in the Board list and you have a copy of the driver, click Other Boards and install the driver from a local or network drive.

3.	(Optional) Click Driver Settings to configure the LAN board.

4.	Click Next when you are finished.

To reset values to the driver

Select Reset to Detected Driver.

Note:  SETUP.EXE discovers the current network boards and LAN driver settings by requesting the information from LSL.COM or NIOS.EXE. It does not display information for an installed network board if LSL.COM or NIOS.EXE is not loaded.

Related Topics

Installing Unlisted ODI LAN Drivers

Configuring the LAN Driver

Modifying Driver Settings

Changes Made during Client Software Installation

Link Driver Section (NET.CFG)

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Client Overview

The IntranetWare Client is 32-bit software that provides workstations running DOS and Windows** 3.1x  a stable connection to IntranetWare networks.

It has an advanced architecture that departs from VLM* software enabling Windows** 3.1x and DOS client workstations to run the client software in protected mode, so other programs running on the workstation cannot interfere with memory reserved for the client.

The client replaces Virtual Loadable Module* (VLM) software with NetWare* Loadable Module* (NLM*) software. The NLM format is similar to the server format and enables workstations to use the same 32-bit ODI* LAN drivers that NetWare servers use, ensuring compatibility with existing LAN drivers.

The following architectural advances make the Client easier to use, faster, and more reliable than previous NetWare clients.

GUI Login

It’s never been easier to log in to a NetWare network. Windows 3.x client workstations can log in to a network and run login scripts from a Windows interface as well as from a DOS prompt.

Automatic Reconnect/Retry

The Client can detect changes in the network environment and restore connections or reconnect to the network when the network service comes back online. It can also use multiple network boards on a workstation, so if one board fails, the workstation can continue to access the network from another board. This makes this Client the most reliable NetWare client available. Even if the workstation loses its connection to the network, it continues to run without having to reboot.

Network Application Launcher

The Client includes Network Application Launcher, a program that enables network supervisors to use NetWare Administrator (NWAdmin) to define application objects available to desktops.

Lower Memory Requirements

The Client caches frequently used data, such as file content and network information, resulting in less traffic on the network and faster response times.

It requires less than 5 KB of conventional memory and 500 KB of extended memory. Depending on how much memory a workstation has installed, the Client can use up to 50% of free memory as cache memory. You can set the Client to use up to 75% of free memory for caching.

Full NDS Support

The client enables full support of Novell Directory Services* (NDS*). Using the client, you can browse for network services across multiple trees and use such services as printing and running applications.

Protocol Support

The client includes native support for IPX*/SPX*, TCP/IP, NetWare/IP*, and SNMP (including Host Resources MIB).

LAN Driver Support

The client can use 32-bit or 16-bit LAN drivers and supports the following LAN drivers:

32-bit ODI LAN drivers that comply with the latest NetWare driver specifications (Some certified drivers for NetWare 4.1 are compatible with the IntranetWare* Client)

16-bit ODI LAN drivers

NetWare DOS Requester

The NetWare DOS Requester software has been enhanced in the following ways:

With the 16-bit version of the NetWare Application Launcher*  utility, workstations using the NetWare DOS Requester software can access Application objects in the Directory.

The NetWare DOS Requester software has been enhanced to comply with the Controlled Access implementation (Class C2) requirements of the Trusted Network Interpretation [NCSC-TG-005] of the Trusted Computer System Evaluation Criteria [DoD5200.28-STD].

A version of the NetWare DOS Requester software that includes support for a 16-bit TCP/IP transport, the Dynamic Host Configuration Protocol (DHCP), and the NetWare/IP software is included.

Related Topics

What's New

Product Overview

Overview Contents

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Client System Requirements

In order to use the IntranetWare* Client* for DOS/Windows , the client workstation must be an IBM** compatible with the following specification.

Installed Components

Intel** (or compatible) 80386 (or later) processor

A hard disk with at least 15 MB of free disk space (more if you are installing all the components). SETUP.EXE checks for available disk space during installation.

At least 8 MB of RAM

At least 500 KB of free lower memory (to run the SETUP.EXE program only)

A memory manager such as HIMEM.SYS, EMM386.EXE, QEMM, or 386MAX

A network board with the appropriate LAN driver

A physical connection to a NetWare* network:

- a suitable network adapter card (with the appropriate software and cabling)

- a Standard or ISDN modem, or

- an ISDN bus adapter

A supported operating system

Supported Operating Systems

Novell* DOS* 7

MS-DOS** 5.x or 6.x

PC-DOS 5.x , 6.x , or 7.0

Windows** 3.1x  (or later) or Windows for Workgroups 3.11

Related Topics

Client Computer Configuration Requirements

Preparing for Installation

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Configure Host MIB (2 of 2)
Configure Host MIB (2 of 2) Dialog Box

1.	Enter the number of subdirectory levels below the root directory that you want the Host MIB agent to scan for installed software.

2.	List the paths to any directories you want to include in the inventory scan that are more levels away from the root than the number entered in Step 1.

3.	Click Add to display the Add New Paths dialog box.

3a.	Type the path to the directory you want Host MIB to inventory.

3b.	Click OK.

The new paths are displayed in the Additional Search Paths box.

Note:  You can search all subdirectories by typing "\*.*" after the directory name. For example, the path "C:\WINDOWS\*.*" makes the Host MIB agent search C:\WINDOWS and all subdirectories below the WINDOWS directory.


Configure SNMP (2 of 2)
Configure SNMP (2 of 2) Dialog Box

Trap Target Address

The network addresses of SNMP management consoles. The SNMP agent on the client workstation sends SNMP information to the network addresses listed.

IPX* addresses are two hexadecimal numbers separated by a colon (9FA:C01). IP addresses are four numbers from 1 to 255 separated by periods (111.222.33.44).

To add a new address:

1.	Click Add.

The Add Trap Target Address dialog box is displayed.

2.	Select the type of address.

3.	Type in the address in the appropriate format.

4.	Click OK.

The new address is displayed in one of the Addresses boxes.

Related Topics

Overview of SNMP and Host Resources MIB

Configuring Host Resources MIB

Listing Devices for Host MIB

Changes to SNMP Clients

Configuring Additional Options

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Configuring Host MIB (1 of 2)
Configure Host MIB (1 of 2) Dialog Box

Note:  All settings in this dialog box are optional.

To set up support for Host Resources MIB:

1.	If your workstation has a local device such as a printer, tape drive, or modem that you want to record in the Host Resources MIB inventory database, click Add.

The Add Local Device dialog box is displayed.

2.	 Type any information you want to record for the device connected to your workstation.

3.	Click OK.

4.	Click Next to display the Configure Host MIB (2 of 2) dialog box.

Related Topics

Overview Host Resources MIB

Listing Devices for Host MIB

Changes to SNMP Clients

Overview of HOSTMIB.NLM

Configuring Additional Options


Configuring LAN Driver in Windows_p
Configuring the ODI LAN Driver in Windows

2a.	Remove any existing LAN drivers from the dialog box by selecting a LAN driver and clicking Remove.

When prompted to make sure you want to remove the selected LAN drivers, click Yes.

2b.	Click Add Adapter.

2c.	From the Add Network Adapter dialog box, select the appropriate ODI* LAN driver for your network board.

SETUP.EXE might prompt you to direct it to the location of the correct ODI LAN driver. The LAN driver should exist in the directory you used when installing the IntranetWare* Client*.

2d.	Click OK.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Configuring NetWare/IP

Enter the following information in the NetWare/IP Configuration dialog box.

NetWare/IP Domain Name

Enter the NetWare/IP* domain name (for example, NWIP.ATLANTIC.COM).

Preferred DSS

(Optional) Enter the names or addresses of preferred domain servers running Service Advertising Protocol (SAP) or Router Information Protocol (RIP). For example:
222.33.0.0 DSSSERV.ALTANTIC.COM

You can enter up to five servers by separating the names or addresses by a space.

Nearest NWIP Server

(Optional) Type the name or address of the server you want NetWare/IP to communicate with first (for example, SERV1.ATLANTIC.COM).

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Configuring Protocols in Windows

3a.	 To add a protocol, click Add Protocol, select the protocol you want to use, and then click OK.

You can use the following protocols with the IntranetWare* Client*:

IPX*/SPX* Compatible Transport

IPX/SPX Compatible Transport with NetBIOS

Microsoft** NetBEUI

3b.	To remove a protocol, select the protocol and click Remove.

3c.	If you load more than one protocol, select the protocol you want to use as default and click Set As Default Protocol.


Configuring SNMP (1 of 2)
Configure SNMP (1 of 2) Dialog Box

You can set up the workstation's SNMP environment to report the following optional parameters:

Your Computer's Name

A label that identifies the client workstation.

Your Computer's Location

A description of where workstation is. You can place any information in this field, up to 80 characters.

Your Name

The name of the person responsible for supporting the workstation. For example, you might want to type the manufacturer's name and phone number.

Related Topics

Overview of SNMP and Host Resources MIB

Configuring Host Resources MIB

Listing Devices for Host MIB

Changes to SNMP Clients

Configuring Additional Options

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Configuring Startup Files in Windows

8a.	From Program Manager, click Run from the File menu.

8b.	Type "SYSEDIT" and click OK.

8c.	In the AUTOEXEC.BAT window, highlight the line that loads ODIHLP.EXE.

8d.	From the Edit menu, click Cut.

8e.	From the File menu in Program Manager click Run.

8f.	Type "NOTEPAD" and the path to the STARTNET.BAT file. For example:

NOTEPAD C:\NOVELL\CLIENT32\STARTNET.BAT

8g.	Click OK.

8h. In the STARTNET.BAT file, paste the ODIHLP.EXE line above the line that loads PC32MLID.LAN.

8i.	Save your changes and close NOTEPAD and SYSEDIT.


Configuring Support for SMS
Configure Novell TSA

Enter the following information to install NetWare* Target Service Agent (TSA) support for backing up workstation files to a Storage Management Services* (SMS*) server:

TSA Server Name

The name of the server that backs up the client workstation. Up to 48 characters are allowed.

Your Computer Name

The description of the workstation for SMS services. Up to 48 characters are allowed.

Password

A 1 to 10 character password that a network supervisor must provide before backing up the workstation's local drives. (This field is optional.)

Local Drives to Back Up

The drive letters of the drives that the TSA server backs up.

Transfer Buffers

The amount of memory reserved for storing data before it is sent over the network.

Related Topics

Overview of TSA for SMS

Changes to TSA Clients

Configuring Additional Options

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Configuring TCP/IP

The TCP/IP protocol stack requires information that defines the workstation's network environment. If you do not know the information for some of the fields, accept the defaults and continue with the installation. You can edit these parameters in the NET.CFG and RESOLV.CFG files after SETUP.EXE completes or by running the installation program again.

SETUP.EXE requires the following information to install support for TCP/IP:

Client IP Address

Default Router Address

DNS Domain Name

Domain Name Server Address

Subnetwork Mask

Related Topics

Overview of TCP/IP and NetWare/IP

Changes to TCP/IP Clients

Protocol TCP/IP Section (NET.CFG)

Configuring NetWare/IP

Configuring Additional Options


Configuring the Client for the IPX/IP Gateway
Configuring the Client for the Novell IP Gateway

During installation, any existing Client files under the \WIN95 and \WIN31 subdirectories of SYS:\PUBLIC\CLIENT are updated. There are two options available to update the client:

Install the updated client directly from the product CD-ROM

Install the client from SYS:\PUBLIC\IWCLIENT on a server that has the IntranetWare* Client* for DOS/Windows** installed

Once the client is installed, users can specify a preferred gateway server.

Users can configure a preferred Novell* IP gateway server if there are multiple gateways installed on the network. If a preferred gateway server is configured, the gateway client attempts to attach to that gateway server. If the specified gateway server is not available because the server is down or it has all licensed connections in use, the gateway client searches for other gateway servers in the following manner:

1.	Starting with the current NDS* context, the client searches down the Directory tree for a Novell IP Gateway server.

2.	If no server is found, the client searches the bindery of the attached file server.

3.	If no server is found, the client queries for Service Advertising Protocol (SAP) broadcasts of the nearest gateway server.

Note:  that there is no linkage between the preferred file server and the preferred gateway server. A user can be attached to file server A while using a gateway server that resides on file server B.

Related Topics

Using IntranetWare Client Contents

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Configuring the LAN Driver

The Driver Settings dialog box lists the parameters for the driver you are installing. Most drivers require values for the interrupt request line (IRQ), the frame type, and the the number of retries. Other possible parameters include base I/O port and node address.

All of the configurable parameters for the driver are listed. Default values listed are determined in this order: from NET.CFG, from the LSL* module, or from the defaults specified by the driver.

Note:  You should accept the default driver settings unless you are aware of settings that can increase the performance of your LAN board.

To change driver settings:

1.	Double-click the parameter you want to change.

2.	Set the value of the parameter.

3.	Click OK.

4.	Click OK to exit the Driver Settings dialog box.

Related Topics

Choosing an ODI Driver

Installing Unlisted LAN Drivers

Modifying Driver Settings

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Connecting to the Internet

Overview of IPX/IP Gateway

Configuring the Client for the IPX/IP Gateway

Gateway Switcher Operation


Contacting Novell

Technical support direct from Novell* is a fee-based service.

You can also use Novell's Technical Services Web Site (www.support.novell.com) to access the most up-to-date technical information about Novell products and technologies. It includes the following features:

Downloadable files, patches and drivers

Thousands of Technical Information Documents (TIDs)

Product documentation

Novell Application Notes*

GroupWare Professional’s Guide

Novell Labs* certification bulletins

Related Topics

Troubleshooting Contents

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Contacting a Novell Partner

The Novell* program PartnerNet* allows customers to contact Novell Partners that can assist them with their service needs. PartnerNet integrates key Novell programs sales, consulting, and technical service enabling Novell Partners to provide quality solutions. Novell Platinum Partner* representatives provide enterprise solutions and Novell Gold Partner* representatives specialize in specific product areas. Novell authorizes partners who are committed to providing quality service and support to customers.

To find a Novell Partner in your area, call Novell.

Related Topics

Troubleshooting Contents

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


ControlCommunity

Specifies the name of the SNMP community that has rights to control the workstation when the EnableControlCommunity parameter is set to SPECIFIED.

Syntax: ControlCommunity = name

Default: public

Example:

[SNMP]

ControlCommunity = public

Related Topics

EnableMonitorCommunity

Desktop SNMP Section (NET.CFG)


Copy Files
Copy Files Dialog Box

You are now ready to copy the program files onto your workstation.

If you want to go back through the dialog boxes to change any information, click Previous.

Click Begin Copy to start copying IntranetWare* Client* files onto your workstation.

You might be prompted to replace existing files during copying. We recommend that you replace existing files; otherwise, the IntranetWare Client might not work correctly.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Core Modules

Overview

The core modules are the modules that a workstation must load to connect to a network. These modules must be loaded in the following order:

Modules

CLIENT32.NLM

IPX.NLM

LSLC32.NLM

NIOS.EXE

Examples

Example of Loading 32-bit ODI LAN Drivers

Example of Loading 16-bit ODI LAN Drivers

Related Topics

Reference Information Contents


Create New Location Profile
Create a New Location Profile Dialog Box

A location profile specifies your workstation's configuration parameters. When installing the Remote Access Dialer, you will probably require at least one LAN-based location profile and a dial-in profile. Even if you do not dial-in, you might require more than one LAN-based configuration.

When installing the Remote Access Dialer, you must create at least one location profile during installation. Click Create Location Profile to start the series of dialog boxes that help you create a location profile. For each location profile, you will be prompted to provide information such as how you connect to the network and dialing details if you use a modem or ISDN bus adapter.

When you have created one location profile, you can create more location profiles before continuing. At the Create Another Location dialog box, click Next to continue the installation program, or click Create Location Profile to create another location profile.

When you reboot

When you restart your workstation, select a location profile so that your workstation is configured correctly for your current location.

After installation

You can edit the properties of existing location profiles using the Locations program in the Client Control Panel. You can also create other location profiles.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Creating User Groups for ACU

Consider the following rules when creating a user group for ACU:

The workstations should have similar memory configurations and TSRs.

All workstations in a group should use the same path naming conventions for IntranetWare* and Windows** software.

The workstations should be running the same version of IntranetWare* Client* software.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


DNS_domain Option

Syntax: DNS_domain = DOMAIN_NAME

Default: None

Example:

DNS_domain = company.com

Related Topics

Protocol TCPIP Section (NET.CFG)


Deleted Windows Files

SETUP.EXE deletes these files from the Windows** root directory (normally C:\WINDOWS) and replaces some of these files in the Windows SYSTEM directory.

NETWARE.DRV	NWPOPUP.EXE
NETWARE.HLP	NWPSRV.DLL
NWCALLS.DLL	PNW.DLL
NWIPXSPX.DLL	TASKID.COM
NWGDI.DLL	TBMI2.COM
NWLOCALE.DLL	VIPX.386
NWNET.DLL	VNETWARE.386
NWPSERV.DLL
* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Disk Space Warning
Disk Space Warning Dialog Box

SETUP.EXE has estimated that you might not have enough free disk space to install the IntranetWare* Client* for DOS/Windows**. The estimate has taken into account your current free disk space and any free space that would be available when files that you already have are replaced with the ones being installed.

However, it is only an estimate and you might want to continue with the installation. If you want to continue, click Continue.

If you do not want to continue, click Stop and you will return to the Choose Destination Directories dialog box. You can either select a different destination with more disk space available or click Exit Setup to exit the installation program.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


DiskBuffers

Specifies the amount of memory TSA reserves for transferring data to the SMS* server.

Syntax: DiskBuffers = number_kilobytes

Default: 10

Example:

[TSA]

DiskBuffers = 20

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Downloading the IntranetWare Client
Downloading the IntranetWare Client from the Internet

If you have an Internet connection on the workstation, you can download disk images of the IntranetWare* Client* installation files and run SETUP.EXE from the workstation's hard drive. You can also copy the downloaded files to the network so other users can install from the network.

To download disk images:

1.	Launch your Internet browser.

2.	Point the browser to a Novell* Support Connections website (support.novell.com).

3.	Locate the DOS/Windows** Client download area.

4.	Download the IntranetWare Client software as a Network Installation to either your workstation or a network drive.

All the installation files are copied to a common directory.

5.	Close your browser.

Note:  The IntranetWare Client for DOS/Windows can also be downloaded from NetWire if you have a CompuServe account.

Related Topics

Installing from a Local Drive

Installing from the Network

Getting Information from NetWire

Installation Contents

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


ENABLE/DISABLE

Switches the client modules on or off.

Syntax: ENABLE | DISABLE function

Example:

ENABLE LOGGING

Notes

Currently, LOGGING is the only parameter available to use with ENABLE/DISABLE.

Enabling LOGGING creates or appends to a NIOS.LOG file in the working directory. The log file contains information about client software events.

You can specify another name and path for the log file in the NET.CFG file.

You can also enable LOGGING by adding a /L to the NIOS.EXE command line.

Related Topics

Reference Information Contents


EnableControlCommunity

Specifies which SNMP communities can access the workstation.

Syntax: EnableControlCommunity = specified | any | off

Default: off

Example:

[SNMP]

EnableControlCommunity = any

Related Topics

EnableMonitorCommunity

Desktop SNMP Section (NET.CFG)


EnableMonitorCommunity

Specifies which SNMP communities can query the workstation for inventory information.

Syntax: EnableMonitorCommunity = specified | any | off

Default: Specified

Example:

[SNMP]

EnableMonitorCommunity = any

Related Topics

EnableControlCommunity

Desktop SNMP Section (NET.CFG)


EnableTrapCommunity

Specifies which SNMP communities can capture alerts from the workstation.

Syntax: EnableTrapCommunity = specified | off

Default: Specified

Example:

[SNMP]

EnableTrapCommunity = off

Related Topics

EnableMonitorCommunity

Desktop SNMP Section (NET.CFG)


Ensuring Data Integrity

If the users on your network require maximum data integrity, you can set several parameters in NET.CFG to avoid data loss. The client modules function more slowly when maximized for data integrity than when maximized for speed.

Note:  There is a NET.CFG file for each location profile on a workstation. Edit the NET.CFG file for the location profile you are using. If you did not create a location profile during installation, this is the NET.CFG file in the default location profile subdirectory, \PROFILE\LOC_0.

To increase data integrity of the IntranetWare* Client*:

1.	Open the NET.CFG file in a text editor.

Hint: The simplest way to ensure that you are opening the NET.CFG file for the correct location profile, is to run the Locations program. Select the profile, and then click on Advanced. Click Edit NET.CFG. The NET.CFG file is opened in an editor.

2.	Set the following parameters to specified values, using the NET syntax information in the topic Overview of NET.CFG:

Parameter	Value
Auto-reconnect Level	4 or 5
Checksum	2 or 3
Close Behind Ticks	0
True Commit	on
3.	Save your changes and exit the editor.

4.	Unload and reload the IntranetWare Client software, or reboot the workstation, to make the changes effective.

Related Topics

Increasing Speed

Minimizing Memory Usage

Loading LAN Drivers

Editing the NET.CFG file

Optimizing STARTNET.BAT

Optimization Contents


Example STARTNET.BAT file

A STARTNET.BAT which has loaded the minimum IntranetWare* Client* for DOS/Windows components might include the following:

NIOS.EXE

LOAD LSLC32

LOAD CMSM

LOAD ETHERTSM

LOAD CNE2000 INT=3 PORT=300 FRAME=ETHERNET_802.2

LOAD CNE2000 INT=3 PORT=300 FRAME=ETHERNET_SNAP

LOAD CNE2000 INT=3 PORT=300 FRAME=ETHERNET_II

LOAD CNE2000 INT=3 PORT=300 FRAME=ETHERNET_802.3

If IPX and CLIENT32.NLM are also desired, add:

LOAD IPX

LOAD CLIENT32

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Gateway Switcher Operation

The gateway client includes a switcher program for Windows** 3.x  that switches between Novell* IP Gateway operation and standard WINSOCK operation. The purpose of this program is to switch the client workstation for TCP/IP to TCP/IPX*.

Switcher for Windows 3.1

This Switcher (GWSW16.EXE) uses the NOVWS.INI file by changing the gateway parameter under the [STACK] heading. To enable TCP/IP, the gateway parameter must be set to zero (0). This instructs the WINSOCK.DLL to use IP. If the gateway parameter is set to one (1), WINSOCK.DLL launches the gateway task to establish a control connection using TCP/IPX.

The following is an example NOVWS.INI file for Windows 3.1:

[stack]

gateway=x

ipxGateway=y

Related Topics

Using IntranetWare Client Contents

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Getting Information from NetWire

NetWire*, the Novell* technical information forum, provides one way to access the most up-to-date technical information about Novell products and technologies. When logged on to NetWire, you can search for and download information or troubleshoot your questions with help from other experienced users. Novell system operators (Sysops) monitor the CompuServe** forums and have direct access to Novell support engineers when necessary. The only fee for NetWire is the standard connect charge of the online service you use.

NetWire includes the following features:

Downloadable files, patches and drivers

Thousands of Technical Information Documents (TIDs)

Product documentation

Novell Application Notes*

GroupWare Professional’s Guide

Novell Labs* certification bulletins

If you have a CompuServe account, you can visit NetWire by entering GO NETWIRE at the CompuServe prompt.

You can also use Novell's Technical Services Web Site (www.support.novell.com).

Related Topics

Troubleshooting Contents

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


IP Address (definition)
IP Address

The IP address of the workstation. The IP address is a set of four numbers from 1 to 255 separated by periods. For example, 111.222.233.24.


Increasing the Speed of the Base Client
Increasing the Speed of the IntranetWare Client Software

By default, the IntranetWare* Client* is configured for optimum speed with good data integrity. You can modify the following parameters in the NET.CFG file to maximize the speed at which the client software performs network operations.

Note:  There is a NET.CFG file for each location profile you create. Edit the NET.CFG file for the location profile you are using. If you did not create a location profile during installation, this is the NET.CFG file in the default location profile subdirectory, PROFILE\LOC_0.

To increase the speed of the client software:

1.	Open theNET.CFG file in a text editor.

Hint: The simplest way to ensure that you are opening the NET.CFG file for the correct location profile, is to run the Locations program. Select the profile, and then click on Advanced. Click Edit NET.CFG. The NET.CFG file is opened in an editor.

2.	Set the parameters to specified values, using the information about NET.CFG syntax in the topic, Overview of NET.CFG.

3.	Save your changes and exit the editor.

4.	Unload and reload the client software, or reboot the workstation, to make the changes effective.

Related Topics

Minimizing Memory Usage

Ensuring Data Integrity

Loading LAN Drivers

Editing the NET.CFG file

Optimizing STARTNET.BAT

Optimization Contents

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Installation Contents

Preparing for Installation

Installation Instructions

Installing from a Local Drive

Installing from the Network

What Happens during Installation

Setting Up Additional Software

Uninstalling the IntranetWare Client Software

IntranetWare Client Help Contents


Installing From Floppy Disks
Installing from a Floppy Drive

If you have a workstation that does not have a CD-ROM drive and is not connected to the network, you can create a set of installation diskettes. You can then install from a floppy drive using the Windows-based program SETUP.EXE.

To create installation diskettes:

1.	Prepare blank formatted diskettes to use as installation diskettes.

2.	Do one of the following:

On a workstation with a CD-ROM drive, insert the IntranetWare* Client* CD-ROM.

On a workstation with an Internet connection, download the IntranetWare Client files to the workstation.

3.	Change to the root of the Client directory.

4.	From a DOS prompt, type "MAKEDISK driveletter:" and press Enter.

The driveletter is the letter of the disk drive where you will insert the diskettes.

5.	Insert a blank formatted diskette into the drive you indicated.

6.	Press any key to begin copying files to the disk.

7.	Place additional diskettes in the disk drive as you are prompted.

8.	Label the diskettes as directed.

9.	When you are finished making installation diskettes, place DISK1WIN into the workstation's floppy drive.

10.	 Run Windows and start the IntranetWare Client Setup program, SETUP.EXE.

Related Topics

Overview of installing from a local drive

Running SETUP.EXE from Windows

Installing from downloaded disk images

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Installing ODINSUP.386

To install ODINSUP.386:

1.	From the Program Manager, double-click the Network program group.

2.	Double-click Network Setup.

3.	(Conditional) If the Microsoft Networking is not already installed, click Networks and install it as directed.

4.	Click Drivers.

5.	(Conditional) If you have an NDIS* driver loaded, select it in the Network Drivers list and then click Remove.

6.	Click Yes.

ODINSUP replaces the NDIS driver.

7.	Click Add Adapter.

8.	In the Select a Network Adapter to Install list, select Unlisted or Updated Network Adapter, and then click OK.

9.	When asked for the location of the driver, enter the location of ODINSUP.386 and its corresponding OEMSETUP.INF file.

These files are located on the IntranetWare* CD-ROM in the following directory:

PRODUCTS\DOSWIN32\IBM_6\WINDRV

10.	Verify that the ODINSUP driver type is NDIS3.

If the driver type is something other than NDIS3, complete the following steps:

a. Click Setup.

b. Select Enhanced Mode NDIS Driver from the Driver Type list.

c. Click OK.

11.	Verify that the protocol stacks available on your network appear in the Network Drivers list.

If the protocol stacks available on your network do not appear, complete the following steps:

a. Click Add Protocol.

b. Select the missing protocol from the list.

c. Click OK.

12.	Finish the installation by clicking OK until the Network Setup is closed.

When Windows is started, ODINSUP will be loaded and it binds to the first ODI driver registered with the LSL.  The Microsoft client and NDIS protocols are channeled through ODINSUP and the ODI driver.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Installing Unlisted ODI LAN Drivers

You can install a LAN driver that is not included in the installation files by providing the driver and the .LDI or .INS files on diskette or on a network drive.

To use an unlisted driver:

1.	In the ODI* Driver Path dialog box, type the path to the directory containing the unlisted driver.

Drivers with a .LAN extension are 32-bit. Drivers with .COM extension are 16-bit.

2.	Click OK.

3.	Select the name of the network board your workstation uses.

4.	Click OK.

Related Topics

Choosing an ODI Driver

Configuring the LAN Driver

Modifying Driver Settings

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Installing from CD-ROM

The installation program, SETUP.EXE, is located on the IntranetWare* Client* CD-ROM in the following directory:

PRODUCTS\DOSWIN32\IBM_6.

To install from a local CD-ROM drive:

1.	Insert the IntranetWare Client* CD into the CD-ROM drive.

2.	Run Windows**.

3.	Run SETUP.EXE from Windows using the CD-ROM directory. For detailed instructions see , Running SETUP.EXE from Windows.

Related Topics

Overview of Installing from a Local Drive

Installation Contents

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Installing from a Local Drive

If you need to install the IntranetWare* Client* on only one or two workstations, or if the workstations are not yet connected to a network, run SETUP.EXE from your workstation. Use one of the following methods

If the workstation has a CD-ROM drive, install from the IntranetWare Client CD. Follow the instructions in the topic, Installing from CD-ROM.

If the workstation has an Internet connection, download the IntranetWare Client to a directory on the hard drive.

If the workstation has a CompuServe account, download from NetWire* to a directory on the hard drive. You can visit NetWire by entering GO NETWIRE at the CompuServe prompt.

Steps

1.	Download the IntranetWare Client to a directory on the hard drive using one of the methods above.

2.	Start Windows**.

3.	Run SETUP.EXE from the workstation's hard drive. For detailed instructions, see Running SETUP.EXE from Windows.

Related Topics

Installing from the Network

Getting information from NetWire

Installation Contents

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Installing from the Network

Installing from the network is the most efficient way to upgrade several existing client workstations. It also allows you to edit SETUP.INI before users installing to influence how the installation runs.

To do this, you must first place the files onto a server, then use one of the methods described below to carry out the installation.

Creating a network installation directory

To install from the network, you must place the installation program SETUP.EXE and all the installation files onto a directory on a server that users can access.

You can do this in a number of ways:

Creating a network install directory from CD-ROM.

Downloading the IntranetWare Client from the Internet.

Downloading from NetWire*, if you have a CompuServe** account. See Getting information from NetWire.

Note:  Be sure to grant users Read and File Scan rights to the directory you use.

You can also mount the IntranetWare Client CD-ROM as a volume of a network server and allow users to run SETUP.EXE from the CD-ROM. For instructions, see Mounting a CD-ROM Volume. However, you cannot edit the SETUP.INI file on the CD-ROM.

Preinstallation customization

You can set some default values and determine the amount of user interaction during installation by editing the SETUP.INI file in the network install directory. Do this before users start to install from the network. For detailed information, see Preinstallation Customization - Editing SETUP.INI.

Choosing a network installation method

You can:

Use Network Application Launcher (NAL). NAL can be used to upgrade a Windows** 3.x NDS* client.

Run SETUP.EXE from the network.

Use Automatic Client Upgrade (ACU). ACU is designed to upgrade systems currently using one of the following clients; VLM, NetX, or Client32. ACU allows network supervisors to edit users' login scripts so that the IntranetWare Client is automatically installed when the users next log in.

Related Topics

Installing from a Local Drive

Installation Contents

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


IntranetWare Client Help Contents

Overviews

Read about IntranetWare Client for DOS/Windows concepts and features.

Installation

Find out about system requirements, installation options and changes made during installation.

Optimization

Read about advanced configuration options to tailor your system.

Using IntranetWare Client for DOS/Windows

Find out how to perform a task. Step-by-step instructions can be displayed.

Reference Information

Read about dialog boxes, property tabs, menu commands ,and file parameters.

Troubleshooting

Obtain information to help you when a message is displayed or the IntranetWare Client does not behave as expected.


LOAD/UNLOAD

Loads a client module onto the NIOS core.

Syntax: LOAD | UNLOAD module_name

Example:

UNLOAD CLIENT32.NLM

Note:  STARTNET.BAT uses LOAD commands to load NLM* software on the workstation.

Related Topics

Reference Information Contents

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Loading 16-Bit ODI Drivers

16-bit ODI* drivers require two modules (N16ODI.COM and PC32MLID.LAN) that enable the 32-bit NIOS to communicate with the 16-bit ODI LAN driver. The modules are loaded in STARTNET.BAT after LSL.COM.

The following example illustrates a typical load order of modules in STARTNET.BAT for a workstation that runs a 16-bit ODI LAN driver with the IntranetWare* Client* software:

NIOS.EXE

LH LSL.COM

LH N16ODI.COM

LH NESL.COM

LH 16-bit ODI LAN driver .COM

LOAD LSLC32.NLM

LOAD PC32MLID.LAN

LOAD IPX.NLM

LOAD CLIENT32.NLM

Note:  Unlike the 32-bit ODI LAN drivers, 16-bit ODI LAN drivers access NET.CFG when loading to find configuration information.

Related Topics

Overview of LAN Drivers

Loading 32-bit ODI Drivers

Using 16-bit Protocols with IntranetWare Client

Core Modules

ODI LAN Drivers

Modifying Driver Settings

Optimization Contents

Core Modules

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Loading 32-bit ODI Drivers

The following example illustrates the load order of modules in STARTNET.BAT for a workstation using a 32-bit ODI* LAN driver:

NIOS.EXE

LOAD LSLC32.NLM

LOAD CMSM.NLM

LOAD [ether  | token  | fddi]TSM.NLM

LOAD 32-bit ODI_driver .LAN [configuration parameters ]

LOAD IPX.NLM

LOAD CLIENT32.NLM

Related Topics

Overview of LAN Drivers

Loading 16-bit ODI Drivers

Using 16-bit Protocols with the Client

Core Modules

Modifying Driver Settings

Optimization Contents

Core Modules

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Loading LAN Drivers

Overview of LAN Drivers

Loading 32-bit ODI Drivers

Loading 16-bit ODI Drivers

Using 16-bit Protocol Stacks with the IntranetWare Client

Modifying Driver Settings


Location Configuration

Configuring Network Device Drivers

Optimizing STARTNET.BAT

PCMCIA Card Support

Including a Dial-in Service

Location Selection Dialog Box Timeout

Loading Location Dependent Devices using CONFIG.SYS

Creating Locations for others

Send or Export a Location Profile

Import a Location Profile

Optimization Contents


Logging In to a NetWare Network

You can log in to a NetWare* network from a DOS prompt or from Windows**. If you want to log in every time you boot the workstation, you can add the LOGIN command line in the AUTOEXEC.BAT file or, for Windows workstations, you can place the Login icon in the Startup group or add LOGIN.EXE to the load line in the WIN.INI file.

For more information on logging in from Windows, see the NetWare Login Help.

Prerequisites

An account on a NetWare server or Directory tree.

Client software running on the workstation.

Preferred Tree or Preferred Server setting. This information is stored in a NET.CFG file.

During installation, the current settings are displayed as the default values; you can edit the settings if required. If it cannot find the settings, SETUP.EXE prompts you for this information. If you are creating a location profile, this information is stored in the NET.CFG file for the location profile.

(You can also, make the change in NET.CFG manually and reboot the workstation.)

To log in to an NetWare network from DOS

1.	At the DOS prompt, change to the first network drive (usually F:) by typing the drive letter and pressing Enter.

2.	Type "LOGIN username " and press Enter.

For example, to log in to context "sales.corp" as user "User_1," enter the following:

LOGIN user_1.sales.corp

Related Topics

Overview of Using the Client

Using Network Resources

Location Configuration Files

Overview Contents

Using IntranetWare Client Contents

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


MODULES

Lists and displays information about the Client modules loaded on the workstation.

Syntax: MODULES

Example:

MODULES

Related Topics

Reference Information Contents


Minimizing Memory Usage

You can limit the amount of memory theclient uses by adjusting several parameters in the NET.CFG file used by your workstation's current configuration.

Note:  There is a NET.CFG file for each location profile you create. Edit the NET.CFG file for the location profile you are using. If you did not create a location profile during installation, this is the NET.CFG file in the default location profile subdirectory, PROFILE\LOC_0.

To decrease memory usage of the client software:

1.	Open the NET.CFG file in a text editor.

Hint: The simplest way to ensure that you are opening the NET.CFG file for the correct location profile, is to run the Locations program. Select the profile, and then click on Advanced. Click Edit NET.CFG. The NET.CFG file is opened in an editor.

2.	Set the following parameters to specified values, using the information on NET.CFG syntax in the topic Overview of NET.CFG.

Parameter	Value
Max Cache Size	0 to 1000
Cache Writes	Off
Max Buffer Size	If your network board uses bus-mastering, increasing this setting increases system memory usage. Otherwise, system memory usage is usually unaffected by this setting. See the Related Topics for more information.

3.	Save your changes and exit the editor.

4.	Unload and reload the client software, or reboot the workstation, to make the changes effective.

Related Topics

Increasing Speed

Ensuring Data Integrity

Loading LAN Drivers

Editing the NET.CFG file

Optimizing STARTNET.BAT

Optimization Contents


Modifying Driver Settings

The installation program, SETUP.EXE, uses the driver settings from the workstation's current driver as the defaults for the driver you are installing. You can edit these settings in the Driver Settings dialog box. Driver settings vary, but most drivers include settings for the following:

Parameter	Description
Hardware Interrupt (IRQ)	The hardware interrupt the driver uses to access the processor. Network boards typically use interrupt 3, but if you have multiple LAN boards or if you have other boards installed, you might need to change this number to avoid interrupt conflicts.
Base I/O Port	The address of the Input/Output port.
Frame Type	The frame type or types the network is using.
Retries	The number of times the LAN driver attempts to attach to the network before sending an error code to NIOS.
Node Address	The address of the LAN board uses on the network.
Related Topics

Choosing an ODI LAN Driver

Installing Unlisted LAN Drivers

Configuring the LAN Driver

Changes Made during Client Software Installation

Link Driver Section (NET.CFG)

Optimization Contents


MonitorCommunity

Specifies the name of the SNMP community that has rights to query the workstation for inventory information. This parameter is used only if EnableMonitorCommunity is set to Specified.

Syntax: MonitorCommunity = name

Default: public

Example:

[SNMP]

MonitorCommunity = private

Related Topics

Desktop SNMP Section (NET.CFG)


Mounting a CD-ROM Volume

If you have a CD-ROM drive attached to a NetWare* server, you can mount the IntranetWare* Client* for DOS/Windows** CD-ROM as a server volume. Mounting a CD-ROM volume is the fastest way to create a network installation directory if you plan to allow users to run SETUP.EXE directly from a server.

Note:  If you plan to use ACU (Automatic Client Update) to upgrade clients on the network, you should run SETUP.EXE from a network directory instead of from a CD-ROM volume. See Installing from the network.

To run SETUP.EXE from a CD-ROM volume:

1.	At a NetWare server with a CD-ROM attached, mount the IntranetWare Client CD-ROM as a volume of the server.

For example, to mount a CD-ROM volume labeled CSETUP, enter the following at the server console:

CD MOUNT CSETUP

2.	Grant the users that need to install the IntranetWare Client Read and File Scan rights to the root directory of the CD-ROM.

For example, to grant the group "Upgrade" access to the CSETUP volume, change to the root of the volume and enter the following at a DOS prompt:

RIGHTS CSETUP: RF /NAME=Upgrade.

Related Topics

Setting up a network install directory from CD-ROM

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


NET.CFG Parameters Affecting Speed

The following NET.CFG parameters affect the speed of the IntranetWare* Client* software:

Parameter	Value
Cache Writes	On
Close Behind Ticks	>18
Delay Writes	On
File Cache Level	3 or 4
Large Internet Packets	On
LIP Start Size	576 for WAN connectivity; 65535 for LAN connectivity
Max Cache Size	Depends on RAM free memory available
Opportunistic Locking	On
PB Buffers	1 to 10
Pburst Read Window Size	24 for most networks
Pburst Write Window Size	24 for most networks; 64 for small LANs
Signature Level	0 or 1 (Before changing this setting, make sure your users do not require high security.)
True Commit	Off (unless you require a high level of data integrity)
Use Video BIOS	Off
IPX Frame Types	Bind only to the necessary frame types (Note that 32-bit drivers do not use NET.CFG--the frame type must be specified on the driver's load line.)
* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


NWIP_Domain_Name

Syntax: NWIP_Domain_Name = domain_name

Default: none

Example:

[NWIP]

NWIP_Domain_Name = sales_domain

Related Topics

NWIP Section (NET.CFG)


NameServerAddress Option

Syntax: NameServerAddress = IP_ADDRESS

Default: 000.000.000.000

Example:

NameServerAddress = 1.2.3.4

Related Topics

Protocol TCPIP Section (NET.CFG)


ODI LAN Drivers

Overview

You can use 32-bit ODI* or 16-bit ODI MLID* modules with the IntranetWare* Client* software. MLID software controls the network board and both 32-bit ODI and 16-bit ODI protocols.

Note:  ODI LAN drivers (hardware specific modules) are supplied by network board vendors and are not included in this list.

32-bit Support Module Overviews

CMSM.NLM

ETHERTSM.NLM

FDDITSM.NLM

LSLC32.NLM

PC32MLID.LAN

PDOSMLID.NLM

SROUTE.NLM

TOKENTSM.NLM

16-bit Support Module Overviews

LSL.COM

N16ODI.COM

NESL.COM

PDOSETH.COM

PDOSFDDI.COM

PDOSTOK.COM

ROUTE.COM

Examples

Example of Loading 32-bit ODI LAN Drivers

Example of Loading 16-bit ODI LAN Drivers

Related Topics

Reference Information Contents

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Optimization Contents

The following topics describe how to customize configuration files.

Overview

Minimizing Memory Usage

Ensuring Data Integrity

Loading LAN drivers

Overview of LAN Drivers

Loading 32-bit ODI Drivers

Loading 16-bit ODI Drivers

Using 16-bit Protocol Stacks with the IntranetWare Client

Modifying Driver Settings

Using ODINSUP.386 with Windows for Workgroups

Increasing Speed

Increasing the Speed of the IntranetWare Client Software

Improving Response Times on Modem Connections

Advanced Configuration

Advanced PPP Configuration

Location Configuration

Adding a New Calling Card Service Provider

Adding a New Modem to the Database

IntranetWare Client Help Contents


Optimizing STARTNET.BAT

STARTNET.BAT groups commands that load the programs necessary to attach to a Novell* NetWare* network. SETUP.EXE can edit a workstation's AUTOEXEC.BAT to call STARTNET.BAT so that the network loads automatically each time the workstation boots.

You can edit the STARTNET.BAT to load only the network drivers and programs you want to use or to optimize the way the programs load. Use the following rules when editing STARTNET.BAT to determine the load order for the networking software:

NIOS.EXE should load before any 16-bit TSRs and must load before any NLM* programs.

If you are loading 32-bit ODI* LAN drivers, make sure to specify the interrupt, port, and frame type on the load line for each driver.

If you are using more than one frame type, make a separate LAN driver load line for each frame type.

IPX.NLM binds to all LAN adapters installed at the time it loads.

Related Topics

Changes Made during Client Software Installation

Increasing Speed

Minimizing Memory Usage

Loading LAN Drivers

Location Configuration

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Optional Protocols
Protocols

You can install support for protocols by loading the appropriate module on your workstation.

TCP/IP Overviews

Overview of TCP/IP and NetWare/IP

TCPIP.NLM

NWIP.NLM

SPX_SKTS.NLM

Network Management Overviews

SNMP.NLM

SNMPIPX.NLM

SNMPUDP.NLM

HOSTMIB.NLM

NMR.NLM

TSASMS.COM

Token Ring Source Routing Overviews

Overview of Setting Up Source Routing

SROUTE.NLM

ROUTE.COM

Related Topics

Reference Information Contents


Overview Contents

Read about IntranetWare Client for DOS/Windows concepts and features.

Introduction

What's New?

Product Overview

Remote Access Dialer Components

Remote Access Dialer components

Dialer Assistant

Locations profiles

Phone Book

Calling Card Wallet

Concepts

Logging in to NetWare Network

Overview of What Happens When You Switch on Your Computer

Overview of Location Profile Information

Overview of Dialing and Connecting to the Network

Overview of using Telephone Calling Cards

IntranetWare Client Help Contents


Overview NWIP.NLM
Overview of NWIP.NLM

Description

NWIP.NLM provides NetWare*/IP* support on the workstation. NetWare/IP enables IPX*-based applications to communicate over Internet Protocol (IP) on the network.

Dependencies

Core Modules

TCPIP.NLM

NET.CFG

NWIP Section

Related Topics

Protocols


Overview of Base Client Modules
Overview of Core Client Modules

What Is a Client Module?

Client functionality is divided into separate pieces of software, or modules. A module can be a LAN driver for a network board, a protocol driver, or a driver for other network functions, such network backup.

The client architecture uses the NetWare Input/Output Subsystem (NIOS) to manage modules, so NIOS.EXE must be loaded before you can load any other modules.

What Types of Modules Are There?

The client workstation requires certain core modules to be loaded on the workstation, regardless of the workstation's configuration. These modules are NIOS.EXE, LSLC32.NLM, IPX.NLM, and CLIENT32.NLM.

You load other modules depending on the workstation's network board and network environment.

How Do I Use Modules?

Use the LOAD utility to add modules to NIOS. You should place commands in the STARTNET.BAT file for modules you want to load each time the workstation boots. Many modules require other modules to be loaded before they can load. For information on load order, check the information on the modules you want to use .

You can remove modules from NIOS by using the UNLOAD utility.

Related Topics

Core Modules

ODI LAN Drivers

Protocols

Reference Information Contents


Overview of CLIENT32.NLM

Description

CLIENT32.NLM extends DOS to include network resources, similar to NetWare DOS Requester* (VLM*) software and the NETX shell.

Dependencies

LSLC32.NLM

ODI LAN Drivers

IPX.NLM

NET.CFG

NetWare DOS Requester

Related Topics

IPX.NLM

LSLC32.NLM

NIOS.EXE

Core Modules

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of CMSM.NLM

Description

CMSM.NLM is the Media Support Module* (MSM*) for the ODI* LAN driver. The MSM standardizes and manages primary details of interfacing ODI MLID* software to LSL* and the operating system.

The MSM contains initialization and runtime functions common to all drivers. This module also enables the Hardware Specific Module* (HSM*), the ODI LAN driver, to be used on various platforms.

For more information see "Open Data-Link Interface" in the Concepts manual.

Dependencies

LSLC32.NLM

[ether | token | fddi]TSM.NLM

Configuration Settings

None

Related Topics

ETHERTSM.NLM

TOKENTSM.NLM

FDDITSM.NLM

Overview of ODI

ODI LAN Drivers

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of Client Module Commands

Commands are internal programs in NIOS that help you manage the client software. For example, you can use the LOAD utility to add modules to NIOS.

The commands run from a DOS prompt. You must have NIOS.EXE loaded on the workstation to run the commands.

Related Topics

ENABLE/DISABLE

LOAD/UNLOAD

MODULES

Reference Information Contents


Overview of ETHERTSM.NLM

Description

ETHERTSM.NLM is the Topology Specific Module* (TSM*) for Ethernet networks. TSM software manages operations unique to a specific media type, such as Ethernet, Token Ring, and Fiber Distributed Data Interface (FDDI). ETHERTSM.NLM provides support for all Ethernet frame types.

Dependencies

NIOS.EXE

LSLC32.NLM

CMSM.NLM

Configuration Settings

None

Related Topics

TOKENTSM.NLM

FDDITSM.NLM

Overview of ODI

ODI LAN Drivers

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of FDDITSM.NLM

Overview

FDDITSM.NLM is the Topology Specific Module* (TSM*) for Fiber Distributed Data Interface (FDDI) networks. TSM software manages operations unique to a specific media type, such as Ethernet, Token Ring, and Fiber Distributed Data Interface (FDDI). FDDITSM.NLM provides support for all FDDI frame types.

Dependencies

NIOS.EXE

LSLC32.NLM

CMSM.NLM

Related Topics

ETHERTSM.NLM

TOKENTSM.NLM

Overview of ODI

ODI LAN Drivers

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of HOSTMIB.NLM

Description

HOSTMIB.NLM is an agent that enables the workstation to be managed over SNMP using the Host Resources MIB database format.

Dependencies

SNMP.NLM

NET.CFG

Host MIB Section

Related Topics

Protocols


Overview of Host Resources MIB

The Host Resources MIB agent (HOSTMIB.NLM) can inventory a workstation's hardware and software configuration and send the data to the SNMP management console.

Because the Host MIB agent cannot detect printers, modems, or tape drives, you can type the name of any of these devices you have connected to the workstation. SETUP.EXE saves these values to NET.CFG. During an inventory scan, the agent reads the NET.CFG file for information on these devices. If you do not have any devices to report, leave this field blank.

The Host MIB agent can also scan for software programs on the workstation by searching for .EXE, .COM, and .BAT files. You can increase the speed of this scan by limiting the depth of the search. For example, if you know that the workstation does not have any application executable deeper than three directories from the root directory, you can limit the scan to 3.

If there are a few directories that have applications at a deeper level, you can specify these directories individually.

Related Topics

Configuring Host Resources MIB

Overview of SNMP

Changes to SNMP Clients


Overview of IPX.NLM

Description

IPX.NLM transports data using the Internetwork Packet Exchange* (IPX*) and Sequenced Packet Exchange* (SPX*) protocols.

Dependencies

NIOS.EXE

LSLC32.NLM

NET.CFG

Protocol IPX Section

Related Topics

CLIENT32.NLM

LSLC32.NLM

NIOS.EXE

Core Modules

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of Installing the IntranetWare Client

The program for installing the IntranetWare* Client* for DOS/Windows on Windows** machines is SETUP.EXE. SETUP.EXE copies the necessary software to the workstation's hard disk. It changes existing configuration files such as CONFIG.SYS and WIN.INI.

System requirements

There are minimum requirements for running the IntranetWare Client; you should check that any machines intended to be used as client workstations satisfy these criteria. The topics that describe these requirements are listed in the System Requirements section of Preparing for Installation.

Deciding how to install

There are several ways to install the IntranetWare Client software, so you should determine which installation method works best for you.

If you want to upgrade several existing clients, installing from the network is the easiest way to install. You can edit the SETUP.INI file so users do not need to supply configuration information or use the /ACU switch. By editing SETUP.INI, you can also preset several defaults for installing the software (for example, the default first network drive and whether to prompt the user regarding replacing existing files).

If you intend to use this method, see Installing from the network.

If you need to install the IntranetWare Client only on a few workstations, or if the workstations are not yet connected to a network, you can install from a local drive using the appropriate IntranetWare Client CD-ROM.

If you intend to use this method, see Overview of Installing from a local drive.

Customizing the installation

If you are going to install from a network directory, you can edit the SETUP.INI file before installing to customize the installation to your company's requirements. You can set some default values and determine the amount of user interaction during installation. For detailed information, see Preinstallation Customization - Editing SETUP.INI.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of LAN Drivers

The IntranetWare* Client* supports 16-bit and 32-bit ODI* LAN drivers. For increased performance and stability, you should use a 32-bit ODI LAN driver when one is available for your workstation's network board.

Related Topics

Optimization Contents

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of LSL.COM

Description

LSL.COM is the 16-bit Link Support Layer* (LSL*) for the IntranetWare* Client*. LSL allows one network board to service several communications protocol stacks. It also allows several network boards to service the same protocol stack.

For more information on LSL, see the Concepts manual.

Configuration Settings

Link Support

Related Topics

LSLC32.NLM

ODI LAN Drivers

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of LSLC32.NLM

Description

LSLC32.NLM is the 32-bit Link Support Layer* (LSL*), for the IntranetWare* Client*. LSL allows one network board to service several communications protocol stacks. It also allows several network boards to service the same protocol stack.

For more information on LSL, see the Concepts manual.

Dependencies

NIOS.EXE

NET.CFG

Link Support Section

Note:  LSLC32.NLM uses only the Max Buffer Size parameter in the Link Support section of NET.CFG.

Related Topics

CLIENT32.NLM

IPX.NLM

LSLC32.NLM

NIOS.EXE

ODI LAN Drivers

Core Modules

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of N16ODI.COM

Description

N16ODI.COM coordinates memory access between NIOS and the 16-bit LSL.COM module. This module prevents NIOS from running foreground events while LSL.COM is using real mode interrupts.

Dependencies

NIOS.EXE (can load before or after)

LSL.COM

Note:  N16ODI.COM enables you to load the following modules:

PDOS[eth | tok | fddi].COM

PDOSMLID.NLM

PC32MLID.LAN

Related Topics

Using 16-bit Protocol Stacks with the Client

PC32MLID.LAN

PDOSMLID.NLM

LSL.COM

Loading 16-bit ODI LAN Drivers

Overview of ODI

ODI LAN Drivers


Overview of NESL.COM

Description

NESL.COM manages events for the 16-bit real mode environment. Its function is similar to LSL.COM but it directs event objects instead of data objects.

Dependencies

LSL.COM (can load before of after)

Related Topics

LSL.COM

Protocols

Loading 16-bit ODI LAN Drivers

ODI LAN Drivers


Overview of NIOS.EXE

Description

The NetWare* Input/Output Subsystem (NIOS.EXE) is the first module loaded. NIOS.EXE creates the flat memory environment needed to load other components, and controls the loading and unloading of other client modules. NIOS.EXE also serves as the interface between the operating system and the client.

NET.CFG

NIOS Section

Related Topics

CLIENT32.NLM

IPX.NLM

LSLC32.NLM

Core Modules

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of NMR.NLM

Description

The Network Management Responder module (NMR.NLM) provides information about a workstation to network management utilities such as ManageWise*.

Dependencies

IPX.NLM

Related Topics

Protocols

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of NetWare TSA for SMS

The workstation Target Service Agent (TSA) is a terminate-and-stay-resident program called TSASMS.COM that processes data moving between the client workstation and a Storage Management Server Services* (SMS*) server. The agent makes it possible for an SMS server to back up and restore files on the client workstation.

To install TSA for SMS support, you need to supply some information about the SMS environment on the client workstation. The client workstation maintains this information in the NetWare* DOS TSA section of the NET.CFG file.

Related Topics

Configuring TSA for SMS

Changes to TSA Clients

NetWare DOS TSA Section (NET.CFG)

Configuring Additional Options

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of Novell IP Gateway
Overview of the Novell IP Gateway

What is Novell* IP Gateway?

The Novell IP Gateway is server software that enables IPX*-based NetWare* LANs to connect to the Internet. The server then enables IntranetWare* Clients* to use the Internet without having an individual IP address on the workstation. The gateway also acts as a barrier between the Intranet and the Internet, providing protection against unauthorized intrusion into your network.

How does the gateway reduce administration cost?

The Novell IP Gateway alleviates the administrative difficulties of maintaining an IP address on each client workstation. IPX does not require a network supervisor to assign network addresses manually. But TCP/IP requires a number of items be configured individually for each workstation, such as the IP address, subnet mask, and the IP address of the default router. Since each workstation must have a unique IP address, supervisors must keep accurate lists to avoid address duplication. If duplication does occur, it can cause serious problems on the network that are difficult to diagnose and resolve.

With Novell IP Gateway, only the gateway server uses an IP address. When clients request information from the Internet, the gateway translates the request to IP and forwards the request to the Internet. The gateway also translates IP responses into IPX data and sends the data to the appropriate client workstation on the IntranetWare* network. This allows an IPX client to access the Internet without loading a TCP/IP stack.

How does the gateway work?

IPX and IP actually perform similar functions in a network. An IP gateway exploits the similarities of IP and IPX by replacing IP with IPX on the Intranet, while using IP to communicate with the Internet. The LAN runs in effect, over "TCP/IPX" (see Figure 1).

Figure 1: When the Novell IP Gateway is operating, the gateway server uses the TCP/IP protocol to communicate with the remote host, but each client workstation uses IPX instead of IP to communicate with the gateway server.

Client software required

The Novell IP Gateway requires IntranetWare Client supplied on the IntranetWare CD-ROM. These clients can also be downloaded from the Internet (http://www.novell.com). Earlier versions of the Novell Client do not include IP Gateway.

The IP Gateway client software uses an enhanced version of Windows** Sockets (WINSOCK) that uses TCP/IPX in addition to TCP/IP. The IP Gateway client software supports WINSOCK by establishing and maintaining a connection with a Novell IP Gateway server. The standard implementation of WINSOCK is turned off and the IntranetWare implementation is turned on. You can revert to the original WINSOCK using a utility called the Gateway Switcher which enables or disables the IntranetWare Client’s use of the gateway.

Related Topics

Using IntranetWare Client Contents

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of ODI

The Open Data-Link Interface* (ODI*) specification sets standards for developing Multiple-Link Interface Driver* (MLID*) software and media independent protocol stacks.

The MLID architecture decouples device drivers from protocol stacks. This architecture requires three modules that make up the MLID architecture: the Media Support Module* (MSM*), the Topology Specific Module* (TSM*), and the Hardware Specific Module* (HSM*).

For the IntranetWare* Client*, these modules are loaded in the following order after NIOS.EXE:

LSLC32.NLM

CMSM.NLM

[ether | token | fddi]TSM.NLM

32-bit_LAN_Driver.LAN

For more information, see "Open Data-Link Interface" in Concepts.

Related Topics

CMSM.NLM

ETHERTSM.NLM

TOKENTSM.NLM

FDDITSM.NLM

ODI LAN Drivers

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of Optimizing the Client

You can optimize the IntranetWare* Client* software for your networking environment. By default, the client is configured for high speed with moderate use of memory and data protection. You can adjust the client to optimize its performance in any of these areas. Be aware that optimizing the client in one area can mean a performance cost in other areas, as the following table indicates:

Optimize for	Cost
Speed	Memory, Data Integrity
Data Integrity	Speed
Memory	Speed
Related Topics

Increasing Speed

Minimizing Memory Usage

Ensuring Data Integrity

Loading LAN Drivers

Editing the NET.CFG file

Optimizing STARTNET.BAT

Optimization Contents

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of PC32MLID.LAN

Description

PC32MLID.LAN enables 32-bit ODI* stacks to communicate with 16-bit ODI LAN drivers.

Dependencies

LSL.COM

LSLC32.NLM

N16ODI.COM

NESL.COM

NIOS.EXE

Related Topics

Loading 16-bit ODI Drivers

N16ODI.COM

ODI LAN Drivers

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of PDOSETH.COM

Description

This module enables 16-bit ODI* protocol stacks to use 32-bit ODI LAN drivers.

Dependencies

LSL.COM

LSLC32.NLM

N16ODI.COM

NIOS.EXE

PDOSMLID.NLM

ODILAN Driver Modules

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of PDOSFDDI.COM

Description

This module enables 16-bit ODI* protocol stacks to use 32-bit ODI LAN drivers.

Dependencies

LSL.COM

LSLC32.NLM

N16ODI.COM

NIOS.EXE

PDOSMLID.NLM

ODILAN Driver Modules

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of PDOSMLID.NLM

Description

PDOSMLID.NLM enables the 32-bit ODI* modules to communicate with 16-bit protocol stacks.

Dependencies

LSL.COM

LSLC32.NLM

NIOS.EXE

N16ODI.COM

PDOS[eth | tok | fddi].COM

Related Topics

Using 16-bit Protocol Stacks with the Client

LSL.COM

N16ODI.COM

Overview of ODI

ODI LAN Drivers

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of PDOSTOK.COM

Description

PDOSTOK.COM enables 16-bit ODI* protocol stacks to use 32-bit ODI LAN drivers.

Dependencies

LSL.COM

LSLC32.NLM

N16ODI.COM

NIOS.EXE

PDOSMLID.NLM

ODILAN Driver Modules

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of ROUTE.COM

Description

ROUTE.COM enables the workstation to communicate with network resources across IBM** token-ring network bridges. ROUTE.COM supports 16-bit ODI* LAN drivers.

Dependencies

Core Modules

Token Ring ODI LAN driver

Settings

Configure ROUTE.COM using options on the command line.

Related Topics

Overview of Setting Up Source Routing

Setting up Source Routing

ROUTE.COM Options

ODI LAN Drivers

Protocols

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of Removing the Intranetware Client Software

The IntranetWare Client does not have an uninstall program, so you must edit system files and delete directories if you want to remove the installation.

If you remove the client files from the workstation, you must run the IntranetWare* Client* installation program, SETUP.EXE, to reinstall the client software.

Related Topics

Overview of Turning Off the IntranetWare Client Software

Uninstalling the Intranetware Client Software

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of SNMP

Simple Network Management Protocol (SNMP) is a language that makes it possible to manage different types of computers over a network. When you load the SNMP agent on your workstation, management consoles that use SNMP can perform the following types of management tasks on the workstation:

Configure software settings

Gather information about the workstation

Monitor workstation events

You can control the type of access SNMP management consoles have to a workstation by specifying community names in the NET.CFG file.

Related Topics

Configuring SNMP

Configuring Host Resources MIB

Changes to SNMP Clients

Desktop SNMP Section (NET.CFG)

Configuring Additional Options


Overview of SNMP.NLM

Description

SNMP.NLM enables the workstation to be monitored and controlled by management consoles over Simple Network Management Protocol. It also implements the "system," "interfaces," and "snmp" groups of MIB-II.

This module is an implementation of an extensible SNMP 1.0 agent.

Dependencies

Core modules

NET.CFG

Desktop SNMP Section

Related Topics

Protocols


Overview of SNMPIPX.NLM

Description

SNMPIPX.NLM implements an IPX* transport provider for SNMP. It monitors the IPX socket to receive SNMP request PDUs and to send out the SNMP reply PDUs.

Dependencies

IPX.NLM

SNMP.NLM

NET.CFG

SNMP Transport Provider IPX

Related Topics

Protocols

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of SNMPUDP.NLM

Description

SNMPUDP.NLM implements a UDP transport provider for SNMP. It monitors the SNMP well-known port to receive SNMP request PDUs and to send out the SNMP reply PDUs.

Dependencies

SNMP.NLM

TCPIP.NLM

Note:  Load SNMP.NLM first, then TCPIP.NLM, and then SNMPUDP.NLM.

NET.CFG

SNMP Transport Provider UDP

Related Topics

Protocols


Overview of SPX_SKTS.NLM
SPX_SKTS.NLM

Description

SPX_SKTS.NLM enables the IPX*/SPX* protocols under the Novell* WINSOCK.DLL.

Dependencies

IPX.NLM

Configuration Settings

None

Related Topics

Protocols

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of SROUTE.NLM

Overview

SROUTE.NLM enables communication across IBM** token-ring network bridges. It supports 32-bit ODI* LAN drivers.

Dependencies

Core modules

Configuration

Configure SROUTE.NLM using options on the module's LOAD line.

Related Topics

Overview of Setting Up Source Routing

Setting up Source Routing

SROUTE.NLM Options

ODI LAN Drivers

Protocols

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of Setting Up Named Pipes

The Named Pipes protocol is the basis for communication between the client workstation and advanced client-server applications such as Microsoft** SQL Server and Microsoft Comm Server software.

To set up support for Named Pipes on a workstation, you must install the IntranetWare* Client* and then edit the STARTNET.BAT file to run DOSNP.EXE. The installation program copies DOSNP.EXE to the Client working directory, but it does not set up a workstation to run Named Pipes.

Related Topics

Setting Up a Computer to Run Named Pipes

Named Pipes Section (NET.CFG)

Setting Up Additional Software

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of Setting Up NetBIOS

NetBIOS (Network Basic Input/Output System) is the IBM** standard protocol for applications developed to run peer-to-peer communications on the IBM PC Network and the IBM Token Ring Network. NetBIOS has become widely accepted as a standard for network interfacing.

The IntranetWare* Client* provides a NetBIOS driver that emulates the NetBIOS protocol. This emulator allows the NetWare* IPX* protocol to interface with the NetBIOS Interrupt 5Ch and an alternate interface, Interrupt 2Ah.

The NetBIOS software provided by Novell* is an emulator because it does not transmit NetBIOS packets. Instead, NetBIOS packets are encapsulated in IPX packets which are transmitted.

The NetBIOS protocol was designed for small-scale networks. While Novell has added functionality to the original specification, the NetBIOS emulation still works most effectively with small-scale networks.

If your network contains several thousand workstations and your LAN segments are interconnected with more than one router, use SPX* instead of NetBIOS if your applications support SPX.

To set up support for NetBIOS on a workstation, you must install the IntranetWare Client and then edit the STARTNET.BAT file to run the NetBIOS driver, NETBIOS.EXE. The installation program copies NETBIOS.EXE to the Client working directory, but it does not set up a workstation to run NetBIOS.

Related Topics

Setting Up NetBIOS

Setting Up Additional Software

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of Setting Up Source Routing

The IntranetWare* source-routing drivers (SROUTE.NLM and ROUTE.COM) enable communication across IBM** token-ring network bridges.

SROUTE.NLM supports 32-bit ODI* LAN drivers.

ROUTE.COM supports 16-bit ODI LAN drivers.

To set up support for source routing on a workstation, you must install the IntranetWare* Client* and then edit the STARTNET.BAT file to load SROUTE.NLM. The installation program copies SROUTE.NLM to the Client working directory, but it does not set up a workstation to run source routing. You also need to load source routing on a NetWare server.

Related Topics

Setting Up Source Routing

Setting Up Additional Software

Protocols

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of Support for Windows for Workgroups

You can install support for peer-to-peer networking in Windows** for Workgroups 3.11. Peer-to-peer networking enables you to share and access printers and disk drives attached to a workstation over the network.

You can use the following protocols for Microsoft** peer-to-peer networking with the IntranetWare* Client*:

NetBEUI

IPX*/SPX* Compatible Transport with NetBIOS

IPX/SPX Compatible Transport

Note:  You must set up the IntranetWare* Client to use 16-bit ODI* LAN drivers if you want to use peer-to-peer networking. The peer-to-peer networking software included with Windows for Workgroups does not support 32-bit ODI LAN drivers.

Related Topics

Setting Up Peer-to-Peer Support for Windows for Workgroups

Installation Contents

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of TCPIP.NLM

Description

TCPIP.NLM enables Transmission Control Protocol/Internet Protocol on client workstations.

Dependencies

Core Modules

Important -- Load TCPIP.NLM before loading CLIENT32.NLM.

NET.CFG

Protocol TCPIP Section

Related Topics

Overview of TCP/IP and NetWare/IP

Protocols


Overview of TOKENTSM.NLM

Description

TOKENTSM.NLM is the Topology Specific Module* (TSM*) for token-ring networks. TSM software manages operations unique to a specific media type, such as Ethernet, Token Ring, and Fiber Distributed Data Interface (FDDI). TOKENTSM.NLM provides support for all token-ring frame types.

Dependencies

NIOS.EXE

LSLC32.NLM

CMSM.NLM

Configuration Settings

None

Related Topics

ETHERTSM.NLM

FDDITSM.NLM

Overview of ODI

ODI LAN Drivers


Overview of TSASMS.COM

Description

TSASMS.COM is the Target Service Agent that provides workstation support for NetWare* Storage Management Services* (SMS*). You can use TSA.NLM and SMS to create backup copies of local files on a network storage device.

NET.CFG

NetWare DOS TSA Section

Related Topics

Overview of NetWare TSA for SMS

Protocols

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of Turning Off the IntranetWare Client Software

The Intranetware* Client* software does not have an uninstall program, so you must edit system files and delete directories if you want to remove it.

If you plan to use the IntranetWare Client again on the workstation, you can "turn it off" by commenting out the line in the AUTOEXEC.BAT that calls STARTNET.BAT in the CLIENT32 directory.

The IntranetWare Client does not replace the VLM* or NETX client, so you can revert to these clients simply by specifying the STARTNET.BAT file in the NWCLIENT directory.

Related Topics

Turning off the IntranetWare Client Software

Removing the IntranetWare Client Software

Uninstalling Windows Components

Uninstalling Protocols

Uninstalling the Intranetware Client Software

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of Using the Intranetware Client Software

The IntranetWare* Client* software extends the capabilities of DOS and Windows** programs by adding extra drives to the workstation's environment and redirecting print jobs to network printers.

In Windows, you can access network files through File Manager. Also, you can use NetWare* User Tools in Windows for mapping drives, capturing printer ports to network printers, and sending network broadcast messages.

In DOS, you can use command line utilities such as MAP, CAPTURE, and SEND to perform these functions. Type "/?" on the command line for syntax information on each of these commands.

Related Topics

Logging In to a NetWare Network

Using Network Resources

Using IntranetWare Client Contents

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Password

Sets a password that a network supervisor must provide before SMS* can back up the client workstation's local drives.

Syntax: Password = 1-10_character _word

Default: none

Example:

[TSA]

Password = b@Kup

Related Topics

Password (NET.CFG)

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Preparing for Installation

The following topics describe the decisions you must take about how to install, and things you need to check before you install. Whether you are about to install the IntranetWare* Client* or a network supervisor responsible for setting up for installation, we suggest that you read the Overview and then all other relevant topics.

Overview of Installing the IntranetWare Client

System Requirements

Client Computer Configuration Requirements

Client System Requirements

Configuring Network Devices

Configuring TCP/IP

Preinstallation Customization - Editing SETUP.INI


Product Overview

The IntranetWare* Client* for DOS/Windows provides the following features

The Client

The IntranetWare Client is 32-bit software that provides computers running DOS and Windows** 3.1x  a stable and secure connection to IntranetWare networks. A network or modem connection provides access to the following:

the LAN from virtually anywhere in the world

the Internet

CompuServe**

secure corporate networks (LAN to LAN or LAN to WAN)

Dialing

You can use the IntranetWare Client to access the Internet, dial out to bulletin boards, and to dial in to the network. The IntranetWare Client includes client software for the Novel* IP Gateway as well as the Remote Access Dialer.

Note:  The Remote Access Dialer will only work under Windows, it will not work on a DOS-only machine.

Note:  The Remote Access Dialer will not work with the WIN2NCS redirector. (Windows 95 and Windows NT dialers do work with WIN2NCS.

GUI Login

Users can log in to a network and run login scripts from a Windows interface as well as from a DOS prompt.

NetWare User Tools

The familiar graphical NetWare User Tools utility is available in Windows to enable network users to display and modify the current status of your client workstation, drive mappings, servers, printers, queues, volumes, and other necessary information. NetWare User Tools are compatible with NetWare 2, NetWare 3, and NetWare 4 networks.

Full NDS Support

You can browse for network services across multiple trees and use network services such as printing and running applications.

Protocol Support

The IntranetWare Client includes native support for IPX*/SPX*, Novell's 32-bit TCP/IP transport, NetWare/IP*, and SNMP (including Host Resources MIB).

TSA Support for Storage Management Services

You can install a Target Service Agent (TSA) on workstations that enables a NetWare server to back up the workstation's local drives.

Automatic Client Upgrade

You can distribute IntranetWare Client to the workstations on your network using the Automatic Client Upgrade (ACU) utility.

Related Topics

What's New

Client Overview

Remote Access Dialer Components

Overview Contents

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Protocol Sections in NET.CFG

Section	Protocol
Protocol TCPIP	TCP/IP support
NWIP	NetWare/IP*
Desktop SNMP	SNMP support
Host MIB	Host Resources MIB support
NetWare* DOS TSA	TSA for SMS*
* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


ROUTE.COM Options

ROUTE.COM adds functionality to the ODI* LAN driver to support source routing among Token Ring networks.

Syntax: ROUTE [option1, option2,...]

Example:

ROUTE BOARD=2, DEF

You can use any of the following command line options with ROUTE.COM.

Option	Explanation
BOARD=number	Specifies the number for the network board that ROUTE.COM binds to. The board number is determined by the order in which the LAN drivers are loaded, starting with board number 1. If you do not specify a board number, ROUTE.COM binds to board 1.
DEF	Prevents frames that have unknown destination addresses from being sent across single-route IBM* bridges.
GBR	Sends General Broadcast frames to All Routes Broadcast frames.
MBR	Sends Multicast Broadcast frames to All Routes Broadcast frames.
NODES=number	Specifies number of table entries (between 8 and 255) in source-routing table. The default is 16.
HOPS=number	Specifies the number of bridges (up to 13) a packet can traverse. The default is 7.
TIME=number	The number of seconds (between 1 and 3640) the source router waits for a response before timing out a known route. The default is 10. Enter "0" to disable routing timeouts.
CLEAR	Clears the source-routing table and forces dynamic rebuilding of table by sending default frame type to each computer on the network.
REMOVE=number	Removes the node address from the workstation’s source-routing table. Use this parameter when a bridge has gone down. Replace number with a 12-digit (6-byte) hexadecimal number. If you specify fewer than 9 digits, ROUTE.COM adds a 4000h prefix to the number. For example, REMOVE=2 is interpreted as REMOVE=400000000002.
TRA=number	A number (between 00 and 255) specifying a THIS RING ALTERNATE count for broadcasts. The source router alternates between source-routed and non-source-routed frames. The default is 00.
TRO=number	A number (between 00 and 255) specifying a THIS RING ONLY count for broadcasts. The default is 00.
XTX=number	Specifies the number of times (between 00 and 255) ROUTE.COM transmits on a timed-out route. The default is 02 times.
U	Unloads ROUTE.COM.
?	Displays command line help usage information.
* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Reference Information Contents

Read information about dialog boxes, property tabs, menu commands, and file parameters.

Client Commands

Overview of the Client Module Commands

ENABLE/DISABLE

LOAD/UNLOAD

MODULES

Core Client Components

Overview of Core Client Modules

Core Modules

ODI LAN Driver

Protocols

NET.CFG Parameters

Client NET.CFG Parameters

NET.CFG

Remote Access Dialer Menus, Dialog Boxes and Tabs

Dialer Assistant Menus

Dialer Assistant Dialog Boxes

Locations Program Property Tabs

Location Program Dialog Boxes

IntranetWare Client Help Contents


Removing Intranetware Client Windows Components

Purpose

To reverse the changes the IntranetWare* Client* installation program, SETUP.EXE, makes to Windows** workstations when no optional components have been installed.

Note:  This procedure is generalized for Windows 3.1 and Windows for Workgroups 3.11. Some tasks might not be applicable to removing the client support for Windows from your workstation.

To uninstall client support for Windows:

1.	In Program Manager, switch to the IntranetWare Client window.

2.	Select each icon in the group and press Delete. In each case, press Yes in reply to the prompt.

Each item in the program group is deleted.

3.	With the empty IntranetWare window still highlighted, press Delete. Press Yes, in reply to the prompt.

The program group is deleted.

4.	From the File menu in Program Manager, select Run.

5.	Type SYSEDIT on the command line.

The System Configuration Editor is opened with each system file displayed in a window.

6.	Click the SYSTEM.INI window and do the following:

6a	Delete VNETWARE.386 from the Network = line in the [386 Enh] section.

6b	Delete the device = VLANINT.386 line from the [386 Enh] section.

6c	Delete netware.drv from the "secondnet.drv =" or the "network.drv =" line in the [boot] section.

6d	Delete "Novell IntranetWare Client for DOS/Windows" from the "secondnet.drv =" or the "network.drv =" line in the [boot.description] section.

7.	Click the WIN.INI Window.

7a.	Delete the "load = NWPOPUP.EXE" line from the [Windows] section.

8.	Save your changes to SYSTEM.INI and WIN.INI and close the System Configuration Editor.

9.	Delete the Client Windows files from the Windows root and Windows SYSTEM directories.

10.	If you installed support for TCP/IP, rename WINSOCK.OLD and WLIBSOCK.OLD in the Windows root and Windows SYSTEM directories to WINSOCK.DLL and WLIBSOCK.DLL, respectively.

Related Topics

Overview

Turning Off the IntranetWare Client Software

Uninstalling the IntranetWare Client Software

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Removing the IntranetWare Client Software

Purpose

To reverse all changes made by running the IntranetWare* Client* installation program, SETUP.EXE, without any optional components.

To remove the client software:

1.	Delete the Client working directory.

2.	Open AUTOEXEC.BAT in a text editor.

3.	Delete the line that calls the STARTNET.BAT.

4.	Save the change and exit the editor.

5.	 Remove IntranetWare Client Windows** components installed on the workstation.

Related Topics

Overview

Turning off the IntranetWare Client Software

Uninstalling the IntranetWare Client Software

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Replace File

You already have a copy of the named file in the destination directory that has a more recent time and date stamp than the file that is about to be copied onto your workstation.

You can choose to preserve your existing file or replace it with the new file being installed.

Click Replace if you want to replace your existing file with the new one.

Click Preserve to keep your existing file and not install the new file.

Important -- We recommend that you replace existing files; otherwise, the IntranetWare* Client* might not work correctly.

Do not prompt for future replacements

Select this check box if you do not want to be prompted about future replacements:

If you choose to replace this file and further version conflicts occur, existing files are replaced automatically.

If you choose to preserve your existing file and further version conflicts occur, your existing files are preserved.


Running Setup from NAL
Running SETUP.EXE from NAL

Network Application Launcher (NAL) is an add-on utility to NetWare Administrator that enables network supervisors to create NDS* objects for applications. Network Application Launcher is available on the Internet.

For information on using NAL to install IntranetWare* Client* software, see the README file and the online Help that accompany the NAL software.

Related Topics

Installing from the network

Running SETUP.EXE from the Network

Installation Contents

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Running Setup from the Network
Running SETUP.EXE from the Network

After you have created a network installation directory containing the SETUP.EXE installation program and the installation files, network users can run SETUP.EXE directly from the network.

Prerequisite

Clients must be running GUI login.

To run a user-initiated Setup from the network:

1.	Log in to the network.

2.	Map a drive to the network installation directory.

3.	Start Windows**.

4.	Run the client installation program, SETUP.EXE. For detailed instructions, see Running SETUP.EXE from Windows.

Note:  A network supervisor can influence the amount of user input during installation by editing the SETUP.INI file in the network installation directory.

Related Topics

Installing from the Network

Preinstallation Customization - Editing SETUP.INI

Installation Contents

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


SROUTE.NLM Options

Syntax

LOAD SROUTE [board=number ] [name=board_name ] [def | gbr | mbr] [time=number ] [rsp=ar | nr] [clear | remove=number ] [xtx=number ] [tra=number ] [tro=number ] [unload (board=number )] [?]

Example

LOAD SROUTE BOARD=1 GBR

Option	Purpose
BOARD=number	Specifies the number for the network board you want to modify parameters on or load source routing for. The board number is determined by the order in which the LAN drivers are loaded, starting with board number 1. The default is 1.
NAME=board_name	Specifies the board name.
DEF	Sends all Unknown Unicast frames as All Routes Broadcast frames.
GBR	Sends General Broadcast frames to All Routes Broadcast frames.
MBR	Sends Multicast frames to All Routes Broadcast frames.
TIME=number	Specifies how often the source routing table is updated, in seconds. Enter an integer between 3 and 255. The default is 10.
RSP=AR | NR	Specifies how the workstation responds to a broadcast request. NR responds directly to a broadcast frame. AR responds with an All Routes Broadcast frame. AR is the default.
CLEAR	Clears the source routing table and forces dynamic rebuilding of table. Use CLEAR when an IBM bridge has gone down and an alternate route is available.
REMOVE=number	Removes a specific node address from the workstation's source routing table.
XTX=number	Specifies the number of times (between 00 and 255) SROUTE.NLM transmits on a timed-out route. The default is 02 times.
TRA=number	A number (between 00 and 255) specifying THIS RING ALTERNATE count for broadcasts. The source router alternates between source routed and non-source routed frames. The default is 00.
TRO=	A number (between 00 and 255) specifying a THIS RING ONLY count for broadcasts. The default is 00.
UNLOAD [BOARD=number ]	Removes the source routing support for the specified network board.
?	Displays command line help.


Selecting a Network Board

Specify the type of board installed in the workstation.

1.	Click on the name that matches the type of network board your workstation uses.

2.	Click OK.

Related Topics

Choosing an ODI LAN Driver

Installing Unlisted LAN drivers

Configuring the LAN Driver

Modifying LAN Driver Settings


Setting Up Addtional Software
Setting Up Additional Software

Peer-to-Peer Support for Windows for Workgroups

Overview

Setting Up Peer-to-Peer Support for Windows for Workgroups

WIN2NCS (for use with third party dialers)

Overview

Installing WIN2NCS

NetBIOS

Overview

Setting Up NetBIOS

Named Pipes

Overview

Setting Up Named Pipes

Source Routing

Overview

Setting Up Source Routing

Related Topics

What Happens during Installation

Installation Contents


Setting Up Named Pipes

Prerequisites

Install the IntranetWare* Client* on the workstation

Set up a NetWare* OS/2** client computer to run Named Pipes services (for more information, see the IntranetWare Client for OS/2 User Guide )

To set up a DOS or Windows 3.1x computer to run Named Pipes:

Note:  There is both a STARTNET.BAT and NET.CFG file for each location profile you create. Edit these files for the location profile you are using. If you did not create a location profile during installation, these are the files in the default location profile subdirectory, PROFILE\LOC_0.

1.	Open the STARTNET.BAT file in a text editor.

Hint: The simplest way to ensure that you are opening the STARTNET.BAT or NET.CFG file for the correct location profile, is to run the Locations program. Select the profile, and then click on Advanced. Click one of the following buttons, depending on which file you want to edit: Edit STARTNET.BAT or Edit NET.CFG. The selected file is opened in an editor.

2.	Edit the STARTNET.BAT file by adding a line to run DOSNP.EXE from the Client working directory.

Run DOSNP.EXE after the line that loads CLIENT32.NLM. For example:

IPX.NLM

CLIENT32.NLM

DOSNP.EXE

3.	(Optional) Modify the NET.CFG file in a text editor by making the necessary configurations in the Named Pipes section.

4.	Restart the workstation to load the Named Pipes software.

Related Topics

Overview of Setting Up Named Pipes

Named Pipes Section (NET.CFG)

Setting Up Additional Software

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Setting Up NetBIOS

Prerequisites

Install NetBIOS on an IntranetWare* server.

Install IntranetWare* Client* for DOS/Windows** on the workstation.

To install NetBIOS on a workstation:

Note:  There is both a STARTNET.BAT and NET.CFG file for each location profile you create. Edit these files for the location profile you are using. If you did not create a location profile during installation, these are the files in the default location profile subdirectory, PROFILE\LOC_0.

1.	Open the STARTNET.BAT file in a text editor

Hint: The simplest way to ensure that you are opening the STARTNET.BAT or NET.CFG file for the correct location profile, is to run the Locations program. Select the profile, and then click on Advanced. Click one of the following buttons, depending on which file you want to edit: Edit STARTNET.BAT or Edit NET.CFG. The selected file is opened in an editor.

2.	Edit STARTNET.BAT by adding a line to load NETBIOS.EXE.

Load NETBIOS.EXE after the line that loads IPX*. For example,

IPX.NLM

NETBIOS.EXE

CLIENT32.NLM

3.	(Optional) Modify the NET.CFG file in a text editor by making the necessary configurations for your NetBIOS application in the NetBIOS section.

4.	Restart the workstation to load NetBIOS.

Related Topics

Overview of Setting Up NetBIOS

Setting Up Additional Software

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Setting Up Peer-to-Peer Support for Windows for Workgroups

Prerequisites

Install Windows** for Workgroups 3.11 on the workstation.

Install the IntranetWare* Client* on the workstation.

Note:  You must select 16-bit ODI* LAN drivers during installation.

To set up peer-to-peer support:

1.	Double-click the Network Setup icon in the Windows Network program group,

2.	Click Drivers to configure the ODI LAN driver for Windows for Workgroups.

3.	Set up the protocols you want to use.

4.	Click Close to exit the Network Drivers dialog box.

5.	Click OK in the Network Setup dialog box.

6.	Click No when prompted to overwrite files on the workstation.

7.	Click Continue to return to Windows without restarting the workstation.

8.	Modify the workstation's startup files to load ODIHLP.EXE after LSLC32.NLM.

9.	To activate Windows for Workgroups peer-to-peer networking, restart the workstation.

Related Topics

Installation Contents

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Setting Up Source Routing

Prerequisites

Load source routing (ROUTE.NLM) on an IntranetWare* server.

Install the IntranetWare* Client* on the workstation.

The source-routing driver that a workstation uses depends on the type of ODI* LAN driver the workstation is running. Load SROUTE.NLM for 32-bit ODI LAN drivers. Load ROUTE.COM for 16-bit ODI LAN drivers.

To set up source routing:

1.	Modify the STARTNET.BAT file in a text editor by adding a line to load the appropriate source-routing driver from the Client working directory.

Load SROUTE.NLM after loading the ODI LAN driver but before loading IPX.NLM.

If the workstation loads 32-bit ODI LAN drivers, add a line to load SROUTE.NLM and any options for the driver. For example:

LOAD CNE2000.LAN

LOAD SROUTE.NLM

LOAD IPX.NLM

LOAD CLIENT32.NLM

2.	If the workstation loads 16-bit ODI LAN drivers, add a line to load ROUTE.COM and any options for the driver. For example:

NE2000.COM

LOAD LSLC32.NLM

LOAD PC32MLID.LAN

ROUTE.COM

LOAD IPX.NLM

LOAD CLIENT32.NLM

3.	Save your changes and exit the text editor.

4.	To load source routing, restart the workstation.

Related Topics

Overview of Setting Up Source Routing

Setting Up Additional Software

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Setting Up a Network Install Directory from CD-ROM
Creating a Network Installation Directory from CD-ROM

If you have an IntranetWare* Client* CD-ROM, you can copy its contents to a network directory and run the installation program, SETUP.EXE, from the network. You must set up a network install directory to use Automatic Client Upgrade.

If you have a CD-ROM drive attached to a NetWare* server, you can mount the CD-ROM as a volume of the server. You can use a mounted CD-ROM to run user-initiated installs over the network.

To run SETUP.EXE from a network directory:

1.	Create a directory on the network.

2.	Copy the contents of the IntranetWare Client CD-ROM to the network directory you created.

Important: Make sure you preserve the directory structure of the CD-ROM when you copy files to the network directory. In DOS, you can do this by using the /E option with the XCOPY command.

For example, to copy the contents of the CD-ROM to a directory named "CSETUP" on drive G:, change to CD-ROM drive and enter the following at a DOS prompt:

XCOPY *.* G:\CSETUP /E

Note:  You do not need to copy the ADMIN and DISKETTE directories to the network directory.

3.	Grant the users that need to install the IntranetWare Client software Read and File Scan rights to the network install directory.

For example, to grant the group "Upgrade" access to the CSETUP directory, change to the CSETUP directory and enter the following at a DOS prompt:

RIGHTS CSETUP RF /NAME=Upgrade

4.	Use a network installation method to run SETUP.EXE from the network.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Setting Up a Network Install Directory from Diskettes
Creating a Network Installation Directory from Diskettes

Installing the IntranetWare* Client* from a single directory is faster than installing from diskettes and does not require users to insert diskettes.

To create a network installation directory from diskettes:

1.	Create a directory on the network.

2.	Copy the contents of the diskettes to the network directory you created.

Note:  If you downloaded the Network Installation files, you do not need to copy the image files to the network. Just make sure the files you downloaded are in a network directory.

3.	Grant Read and File Scan rights to the users or groups of users you want to upgrade.

For example, to grant the group "Upgrade" access to the CSETUP directory, change to the CSETUP directory and enter the following at a DOS prompt:

RIGHTS CSETUP RF /NAME=Upgrade

4.	Use a network installation method to run SETUP.EXE from the network.

Related Topics

Running SETUP.EXE from NAL

Running SETUP.EXE from the Network

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


TCP/IP and NetWare/IP
Overview of TCP/IP and NetWare/IP

Transmission Control Protocol/Internet Protocol (TCP/IP) is a protocol suite that enables diverse workstation platforms to share information. One use of TCP/IP is to connect workstations over global networks, such as the Internet. Another use of TCP/IP is to connect workstations and computers in a corporate network.

NetWare*/IP* sends and receives IPX* packets in an IP format. NetWare/IP enables networked applications that use only IPX to run over TCP/IP networks. It also provides a way for separate IPX networks to communicate across IP connections.

Related Topics

Configuring TCP/IP

Changes to TCP/IP Clients

Protocol TCP/IP Section (NET.CFG

NetWare/IP Section (NET.CFG)

Configuring Additional Options

Protocols

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


The Last Step
The Last Step Dialog Box

You have now copied the IntranetWare* Client* for DOS/Windows** files onto your workstation and the program group has been created. You must restart your workstation to be able to use the IntranetWare Client.

Before restarting, remove any diskettes from your workstation, and then click Finish.

When your workstation restarts, do the following:

If you set up location profiles during installation, the Location Selection dialog box is displayed. Select the appropriate location profile.

To log in to the network, start Windows and enter your username and password in the Login to NetWare dialog box.

Note:  We recommend that you restart your workstation because the installation is not complete until you do; some files are not copied and system files are not updated until you restart your workstation. However, if you do not want to restart your workstation now, clear the Restart Computer check box before clicking Finish.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Trademarks
Trademarks, Copyright, and Patent

Copyright © 1995-1997 Novell, Inc.  All rights reserved.  No part of this publication might be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher.

U.S. Patent Nos. 5,157,663; 5,349,642; and 5,455,932.  U.S. and International Patent Pending.

Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.  Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes.

Further, Novell, Inc. makes no representations or warranties with respect to any NetWare/IntranetWare software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.  Further, Novell, Inc. reserves the right to make changes to any and all parts of NetWare/IntranetWare software, at any time, without any obligation to notify any person or entity of such changes.

Novell Trademarks

Hardware Specific Module is a trademark of Novell, Inc.

Internetwork Packet Exchange and IPX are trademarks of Novell, Inc.

IntranetWare is a trademark of Novell, Inc.

Intranetware Client is a trademark of Novell, Inc.

IPX/SPX is a trademark of Novell, Inc.

Link Support Layer is a trademark of Novell, Inc.

LSL is a trademark of Novell, Inc.

ManageWise is a Registered trademark of Novell, Inc., in the United States

MLID is a trademark of Novell, Inc.

MultipleLink Interface Driver is a trademark of Novell, Inc.

NDPS is a trademark of Novell, Inc.

NDS is a trademark of Novell, Inc.

NMS is a trademark of Novell, Inc.

Media Support module is a trademark of Novell, Inc.

NetWare is a registered trademark of Novell, Inc. in the United States and other countries.

NetWare 3 is a trademark of Novell, Inc.

NetWare Application Notes is a trademark of Novell, Inc.

NetWare DOS Requester is a trademark of Novell, Inc.

NetWare/IP is a trademark of Novell, Inc.

NetWare Loadable Module is a trademark of Novell, Inc.

NetWare Management System is a trademark of Novell, Inc.

NetWire is a registered trademark of Novell, Inc. in the United States and other countries.

NLM is a trademark of Novell, Inc.

Novell is a registered trademark of Novell, Inc. in the United States and other countries.

Novell Application Notes is a trademark of Novell, Inc.

Novell Authorized Reseller is a Service mark of Novell, Inc.

Novell Directory Services is a trademark of Novell, Inc.

Novell Distributed Print Services  is a trademark of Novell, Inc.

Novell Gold Partner is a Service mark of Novell, Inc.

Novell Labs is a trademark of Novell, Inc.

Novell Platinum Partner is a Service mark of Novell, Inc.

Novell Technical Services is a trademark of Novell, Inc.

NSEPro is a trademark of Novell, Inc.

Open Data-Link Interface and ODI are trademarks of Novell, Inc.

PartnerNet is a Servicemark/Trademark of Novell, Inc.

Sequenced Packet Exchange and SPX are trademarks of Novell, Inc.

SMS is a trademark of Novell, Inc.

Storage Management Services is a trademark of Novell, Inc.

Topology Specific Module is a trademark of Novell, Inc.

Virtual Loadable Module and VLM are trademarks of Novell, Inc.

Third-Party Trademarks

Intel is a registered trademark of Intel Corporation.

Macintosh is a registered trademark of Apple Computer, Inc.

Microsoft is a registered trademark of Microsoft Corporation.

Netscape is a trademark of Netscape Communications Corporation

Network Driver Interface Specification and NDIS are trademarks of PC-Plus Communications LP.

OS/2 is a registered trademark of international Business Machines Corporation.

Windows is a registered trademark of Microsoft Corporation.

Windows 95 is a trademark of Microsoft Corporation.

Wyse is a registered trademark of Wyse Technology, Inc.


Troubleshooting Contents

General Tips

Trouble Running Windows

Problems When Dialing Using the Remote Access Dialer

Repeated Loss of Signal and Your Modem Hangs up

Modem Does Not Wait for Bong Tone

TCP/IP Connectivity Problems

Purging the Dial-in Service Object Class

Error Messsages

System Messages

Messages Concerning Installation

Locations Program Messages

Dialer Assistant Messages

ISDN Messages

NetWare Administrator Snap-In Messages

Reaching Technical Support

You have a choice of services that put you in touch with all the technical resources you’ll need.

NetWire

Network Support Encyclopedia Professional Volume (NSEPro)

Your local Novell Partner

Novell Technical Services

IntranetWare Client Help Contents


Turning Off Protocol Support

You can remove support for protocols by commenting out the references to the protocols in the STARTNET.BAT file. If you also want to remove the protocol settings as well, you can remove them from the NET.CFG file.

Note:  There is both a STARTNET.BAT and NET.CFG file for each location profile you create. Edit these files for the location profile you are using. If you did not create a location profile during installation, these are the files in the default location profile subdirectory, PROFILE\LOC_0.

To turn off protocol support:

1.	Open STARTNET.BAT in a text editor.

Hint: The simplest way to ensure that you are opening the STARTNET.BAT file for the correct location profile, is to run the Locations program. Select the profile, and then click on Advanced. Click on Edit STARTNET.BAT. The file is opened in an editor.

2.	Comment out the line that loads the protocol you do not want.

For example, if you want to remove support for TCP/IP, place a REM statement before the line that loads TCP/IP:

REM LOAD C:\NOVELL\CLIENT32\TCPIP.NLM

3.	Save your changes and exit the editor.

4.	Reboot the workstation.

To remove protocol settings:

1.	Turn off protocol support.

2.	Open NET.CFG in a text editor.

Hint: The simplest way to ensure that you are opening the NET.CFG file for the correct location profile, is to run the Locations program. Select the profile, and then click on Advanced. Click on Edit NET.CFG. The file is opened in an editor.

3.	Comment out or delete the section that maintains the settings for the protocol you want to remove.

4.	Save your changes and exit the editor.

5.	Reboot the workstation.

Related Topics

Overview of Turning of the IntranetWare Client Software

Turning off the IntranetWare Client Software

Removing the Intranetware Client Software

Uninstalling Windows Components

Uninstalling the IntranetWare Client Software


Turning Off the IntranetWare Client

Purpose

To temporarily remove the IntranetWare* Client* functionality from a workstation.

To turn off the client software:

1.	Open AUTOEXEC.BAT in a text editor.

2.	Comment out the line that calls STARTNET.BAT. For example:

REM @CALL STARTNET

3.	Save the change and exit the editor.

4.	Reboot the workstation.

To revert to a previously installed VLM* or NETX client:

1.	Open AUTOEXEC.BAT in a text editor.

2.	Change the path to STARTNET.BAT to the file you used in the previous installation. For example:

@CALL C:\NWCLIENT\STARTNET.BAT

3.	Save your changes and exit the editor.

4.	Reboot the workstation.

Related Topics

Overview

Removing the IntranetWare Client SoftWare

Uninstalling Windows Components

Uninstalling Protocols

Uninstalling the IntranetWare Client

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Uninstalling the IntranetWare Client

Turning Off the IntranetWare Client

Overview

Turning Off the IntranetWare Client Software

Turning Off Protocol Support

Removing the IntranetWare Client

Overview

Removing the IntranetWare Client Software

Removing IntranetWare Client Windows Components

Related Topics

Client System Requirements

What Happens during Installation

Installation Contents


Using 16-bit Protocol Stacks with IntranetWare Client

16-bit protocol stacks require a shim called PDOSMLID.NLM to communicate with the 32-bit ODI* modules. Load the LSL.COM after NIOS.EXE is loaded. Load the shim and the 16-bit protocols after loading LSL.COM in STARTNET.BAT. For example:

LSL.COM

N16ODI.COM

NESL.COM

PDOS[eth | tok | fddi].COM

Note:  PDOS.COM loads PDOSMLID.NLM.

Then load your 16-bit ODI-compliant protocol stacks. If you are using 16-bit NDIS**-compliant stacks, you must load ODINSUP.COM first and then the 16-bit NDIS stack.

Related Topics

Overview of LAN Drivers

Loading 32-bit ODI Drivers

Loading 16-bit ODI Drivers

Modifying Driver Settings

Optimization Contents

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Using IntranetWare Client Contents

Overviews

Overview of using the IntranetWare Client

Using Network Resources

Logging in

Logging In to a NetWare Network

Log In to IntranetWare from Windows

Remote Access Dialer Programs

Locations Program: Maintaining Location Profiles

Dialer Assistant: Dialing In and Connecting to the Network

Calling Card Wallet: Setting Up Telephone Call Charging Information

Phone Book: Maintaining Frequently Used Dial-in Service Definitions

Connecting to the Internet

Overview of the Novell IP Gateway

Configuring the Client for the Novell IP Gateway

Gateway Switcher Operation

Using NetWare Administrator

Starting NetWare Administrator for the First Time After Installation

Corporate Dial-in Services

Dialing In to and Out of the Network Modem Pool

Using WIN2NCS

IntranetWare Client Help Contents


Using Network Resources

Workstations running the IntranetWare* Client* can connect to a Novell* NetWare* network and use resources such as printing and file sharing. Some configuration is required to specify the network printers and drives you want to use. Set up your networking environment using the following tools.

Tool	OS	To Get Help
NetWare User Tools	Windows**	Double-click NetWare User Tools in the NetWare Tools program group. Press F1 for help.
NETUSER	DOS	Enter "NETUSER." Help for each menu appears at the bottom of the screen.
CAPTURE	DOS	Enter "CAPTURE /?".
MAP	DOS	Enter "MAP /?".
Related Topics

Overview of Using the Client

Logging In to a NetWare Network

Using IntranetWare Client Contents

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Using Network Support Encyclopedia

The Network Support Encyclopedia Professional Volume* (NSEPro*) is a knowledge base of Novell* technical information on CD-ROM. Updated and delivered 12 times a year, this extensive collection provides you with a convenient, hands-on information source and is accessible through Windows**, DOS, and Macintosh**.

The NSEPro includes the following features:

Downloadable files, patches and drivers

Thousands of Technical Information Documents (TIDs)

Product documentation

Novell Application Notes*

GroupWare Professional’s Guide

Novell Labs* certification bulletins

Order your NSEPro annual subscription directly from Novell. The NSEPro is also available from any Novell Authorized Reseller* representative.

Related Topics

Troubleshooting Contents

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Using ODINSUP.386 with Windows for Workgroups
Using ODINSUP.386

ODINSUP.386 allows users of Windows** for Workgroups 3.11 to access Microsoft Networking’s peer clients and Novell’s network directories with the same LAN card.

Note:  At least these minimum components of IntranetWare* Client* for DOS/Windows must be installed.

NIOS.EXE

LSLC32.NLM

CMSM.NLM

A TSM such as ETHERTSM.NLM

A LAN driver with each supported frame type

Related Topics

Example STARTNET.BAT file

Installing ODINSUP.386

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Welcome to IntranetWare Client for DOS/Windows

You are about to install the IntranetWare* Client* for DOS/Windows** onto your workstation. Before you do this, we recommend that you read the release notes for important information about the IntranetWare Client that is not located elsewhere. Click View Release Notes.

Click Help or press F1 in a dialog box to display help about it. When you enter information in the dialog boxes, you can accept the defaults in most cases.

Button	Explanation
Exit Setup	Exit the SETUP.EXE program at any time.
Previous	Takes you back through previous dialog boxes to change or view the details you have already specified.
Next	Takes you to the next dialog.
Help	Gives you help about a dialog.


What Happens During Installation

The Client

Changes Made during Client Software Installation

Changes to Windows Clients

Changes to TCP/IP Clients

Changes to SNMP Clients

Changes to TSA Clients

Remote Access Dialer

DOS Configuration Files

Location Configuration Files

Windows Configuration Files

Administrator Snap-In Files

NetWare Mobile for Windows 3.x Phone Book Entries

Related Topics

Setting Up Additional Software

Uninstalling the Client

Installation Contents


What's New
What's New?

New features include the following

Updated Client Software

The most reliable and easy-to-use NetWare client available.

Remote Access Dialer

The Remote Access Dialer allows you to connect to a remote access or dial-in server using a modem connection or an ISDN bus adapter. The modem can be a Standard (analogue) or ISDN modem.

Using this connection, you can access NetWare networks, the Internet and intranets. The Remote Access Dialer provides secure dial-up networking capabilities, including NetWare/IP and NWCAP protocol support.

ISDN Support

ISDN connections are supported either via an ISDN modem or using an ISDN bus adapter card.

The ISDN shorthold feature reduces the cost of using ISDN connections by disconnecting the line when it has not been used for a specified period of time, then reconnecting again when needed. All application software using the connection remains unaware of the temporary loss of connection.

ISDN connections can support dialback at the start of a connection. If the shorthold feature is also enabled, the server will not dial back after a reconnection.

Novell IP Gateway

Novell IP Gateway is server software that enables IP and IPX-based NetWare LANs to connect to the Internet. It enables IntranetWare* Client workstations to access TCP/IP, providing access to the Internet without having an individual IP address assigned to a workstation. In addition, it allows Novell IPX clients to access TCP/IP. The gateway also acts as a barrier between the Internet and intranets because it provides protection against unauthorized intrusion into your network.

The IP Gateway Switcher allows you to change between IP to IP and IPX* to IP, setting a preferred server in each case.

The IP Gateway WinPing utility allows you to ping the IP gateway.

ATM LAN Emulation

Asynchronous Transfer Mode (ATM) LAN emulation software emulates existing LAN services which allows network protocols to run over ATM without modification. This software makes the ATM network appear connectionless. ATM networks provide a communication infrastructure capable of carrying voice, video, and data communications over networked computers.

Novell Distributed Printing Services

Novell's latest software for advanced printer configuration and management.

Novell Target Service Agent

Installs NetWare* Target Service Agent (TSA) support for Storage Management Services* (SMS*). TSA software enables SMS to back up client workstations on diverse operating systems. If you have an SMS server, you can back up information on the client workstation to the SMS server by installing the TSA for SMS support.

SNMP and Host MIB

Simple Network Management Protocol (SNMP) is a cross-protocol language that allows administrators to manage computers across diverse network platforms.

If the management console supports Management Information Base (MIB) files, you might also want to load Host Resources MIB support on the client workstation. Host Resources MIB support enables the management console to poll the client for inventory information.

Netscape Web Browser

The Netscape** Internet browser and associated software. Netscape Navigator is a World Wide Web browser which guide you through the information available on the Internet or your company network and gives you point-and-click access to text, graphics, sound and video. The installation program for Netscape is provided on the IntranetWare Client CD-ROM.

Supervisor Tools for Remote Access

These "snap-in" enhancements to NetWare Administrator allow you to set up objects on a server. These can then be copied as local dial-in services on client workstations by updating the Phone Book on each client workstation.

In this way users do not need to know any of the details of the dial-in service on the server side - they simply use a definition you have already configured.

This is also useful if a dial-in service is changed in some way affecting the connection. You can update the corporate dial-in service entry on the server and then inform all users that they need to update their Phone Books again. They do not need to be aware of the details of the upgrade.

Related Topics

Product Overview

Overview Contents

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


WinInstall DNS Address
Domain Name Server Address

The IP address of the domain name server. A domain name server is required for Internet access.


WinInstall DNS Domain Name
DNS Domain Name

The name of the domain name server. The domain name server provides access to the Internetwork.


WinInstall Default Router Address
Default Router Address

The IP address of the router that the workstation uses to connect to another network, such as a Wide Area Network (WAN) or the Internet.


WinInstall IP Address
Client IP Address

The IP address of the workstation. The IP address is a set of four numbers from 1 to 255 separated by periods. For example, 111.222.233.24.

SETUP.EXE places the IP Address in the IP_ADDRESS line in the NET.CFG file.


WinInstall Subnetwork Mask
Subnetwork Mask

The network address of the subnetwork the workstation is on. The subnetwork netmask address should be the same for most of the workstations on a common segment.


Windows Files
Client Files Copied to the Windows SYSTEM Directory by SETUP.EXE

CALWIN16.DLL	NWDRVLGO.BMP
CLNWIN16.DLL	NWGDI.DLL
CLXWIN16.DLL	NWIPXSPX.DLL
CTL3D32.DLL	NWLOCALE.DLL
CTL3DV2.DLL	NWNET.DLL
LGNW3116.DLL	NWPOPUP.EXE
LOCWIN16.DLL	NWPSRV.DLL
LOGINW31.DLL	NWUSER.EXE
NCPWIN16.DLL	PRTWIN16.DLL
NETWARE.DRV	VLANINT.386
NETWIN16.DLL	VNETWARE.386
NWCALLS.DLL

Client Files Copied to the Windows LANGUAGE Directory by SETUP.EXE

LOGIN.DAT	LOGINW31.HLP
LOGIN.MSG	NETWARE.HLP


ip_address Option

Syntax: ip_address = IP ADDRESS

Default: 000.000.000.000

Example:

[TCP/IP]

ip_address = 1.2.3.4

Related Topics

Protocol TCPIP Section (NET.CFG)


ip_netmask Option

Syntax: ip_netmask = IP_ADDRESS

Default: 255.255.255.0

Example:

ip_netmask = 11.22.33.44

Related Topics

Protocol TCPIP Section (NET.CFG)


ip_router

Syntax: ip_router = IP_ADDRESS

Default: 000.000.000.000

Example:

ip_router = 1.2.3.4

Related Topics

Protocol TCPIP Section (NET.CFG)