Novell NetWare is the most popular network operating system, having more than 60% of the worldwide market share. Therefore, chances are good that you will need to know how to connect Windows 98 workstations with NetWare servers.
This chapter will provide you with in-depth information on the following topics:
NetWare is a client/server-based network operating system. This means in order for the Windows 98 workstation to gain access to a NetWare server you need to first load some client software on the workstation. Included with Windows 98 is the Microsoft's 32-bit NetWare client, called Client for NetWare Networks. You can obtain, at no charge, Novell's 32-bit NetWare client for Windows 98 (called NetWare Client for Windows 98, previously known as IntranetWare Client 32 for Windows 95) from Novell; this client software is not included with NetWare 3.12 or IntranetWare/NetWare 4.11 because Windows 98 was released after these products started shipping. However, the NetWare Client for Windows 98 will be included with NetWare 5 and available for free download from Novell's Web sites.
NOTE: In this chapter and much of the Novell literature, you will find the terms NetWare Client and Client 32 used interchangeably.
TIP: You can download the latest NetWare Client for Windows 98 over the Internet, at no charge, from the following Novell sites (note that this is a 9+ MB download):http://www.novell.com/download ftp://ftp.novell.com/pub/updates/nwos http://support.novell.com(For the latter, use the Knowledgebase search engine.) Alternatively, if you have a subscription to the Novell Support Connection (NSC) CD-ROM, the latest clients for all platforms can be found on the latest monthly update.
Microsoft's NetWare client supports NetWare 3.x, and it supports NetWare 4.x if the server has Bindery Services enabled. However, if you need to access a NetWare 4 network using Novell Directory Services (NDS), you need to use either Novell's IntranetWare Client for Windows 98 or install the Service for NetWare Directory Services from your Windows 98 source disk (see "Setting Up Windows 98 Clients in NetWare Environments," later in this chapter.)
NOTE: Although it is possible to use Novell's 16-bit NetWare VLM clients with Windows 98, you are better off using the newer 32-bit clients because you get much better performance and more features than what is available from VLM. Windows 98 is not compatible with VLM Client Kit version 1.21 or later.
Novell's 32-bit clients have an advanced architecture that's very different from the previous NetWare DOS Requester (the VLM-based client) design and some discussion about its design is warranted.
The architecture of the IntranetWare Client, more commonly referred to as Client 32, has been completely redesigned to take full advantage of the 32-bit capabilities of the 80386 and higher microprocessors; this also means this client will not run on pre-386 workstations. Client 32 combines the best elements of Novell's previous client architectures (the NETX Shell and the NetWare DOS Requester, or VLM client) and adds some significant enhancements of its own. In particular, Client 32 for Windows 98 extends the Windows 98 desktop by fully integrating with NetWare 2.x, 3.x, and 4.x services, including Bindery Services and NDS.
The VLM drivers are a set of modules dynamically loaded into and unloaded from the workstation's memory by the VLM manager (VLM.EXE). In essence, they are a combination of terminate-and-stay-resident (TSR) modules and overlay programs. As a result, VLMs can be memory hungry.
On the other hand, the new architecture used by the 32-bit clients lets the client software run in protected mode (thus the requirement for 80386 or better workstations). This requires less than 4 KB of conventional or upper memory while providing a larger cache. The remaining portion of the client is loaded into XMS memory. The IntranetWare Client requires HIMEM.SYS or an equivalent memory manager. The XMS memory requirement for the client is about 800 KB, excluding cache memory.
Several fundamental changes were made in the design of the IntranetWare Client requester. The new requester is made up of two fundamental parts: the NetWare I/O Subsystem (NIOS) and client NetWare Loadable Modules (NLMs).
The NIOS insulates the core client modules from the host operating system by providing an OS abstraction layer (much like the Hardware Abstraction Layer (HAL) used by Windows NT) that core modules can use to access system services. Instead of making OS calls to directly access system services, IntranetWare Client core modules make NIOS calls.
In addition, NIOS provides services to manage client NLMs, using dynamic, self-configurable parameters where possible. For example, if the number of open IPX sockets is increased, IPX.NLM dynamically allocates more memory to handle the extra sockets.
WARNING: Files used by IntranetWare Clients have the extension of NLM. However, these NLMs are not compatible with those used by NetWare servers; nor are they the same. Conversely, server NLMs are not compatible with those of IntranetWare Clients'. There are some NLMs with the same name, but they are not compatible. On the other hand, the CLIENT32.NLM module used with Windows 98 is the same one used by the DOS/Windows Client 32.
NOTE: There are certain things that all the NLM modules (both server-based and client-based) have in common:
- They are dynamically loadable and unloadable.
- They both use the NLM executable format.
- They both use .NLM as the file extension.
- They run in a 32-bit flat memory model.
- They allocate memory that is guaranteed not to move or be discarded.
Similar to the Microsoft 32-bit client, IntranetWare Client uses the Windows 98 Network Device Installer (NDI) and .INF script files to ensure full integration with the Windows 98 environment. In addition, Novell's IntranetWare Client installation program incorporates Windows 98 property pages that have been created specifically for setting and changing IntranetWare Client configuration parameters (such as name of the preferred server) stored in the Windows 98 Registry. Because IntranetWare Client saves its configuration settings in the Registry, you can also manage IntranetWare Client parameters by using Windows 98's System Policies Editor.
NOTE: In order to use the Windows 98 Policy Editor, you need an ADM file specifically designed for the NetWare Client. Novell provides a CLIENT32.ADM file with their client software.
IntranetWare Client uses Microsoft's implementation of Transmission Control Protocol/Internet Protocol (TCP/IP), NetBIOS, WinSock, and Named Pipes, which are included in Windows 98. This means you can switch between Microsoft's NetWare client and Novell's IntranetWare client without having to change anything. Because IntranetWare Client uses the Microsoft protocol stack, it can coexist with Microsoft's Client for Microsoft Networks--a requirement if you have a mixture of NetWare and Microsoft networks in your networking environment.
Both Novell's IntranetWare Client and Microsoft's Client for NetWare Networks perform equally well under most circumstances. However, depending on your particular network requirements and environment, you might prefer to use IntranetWare Client because it has the following features not found in Client for NetWare Networks:
NOTE: Many Novell-supplied utilities--such as NetWare Administrator (NWAdmin)--and third-party NDS-aware applications--such as Cheyenne's ARCserve Manager--will not run with the Microsoft client. That is because the Microsoft client is missing some library files (DLLs), such as NWCALLS.DLL and NWNET.DLL, which are only included with the Novell client.
You can find detailed information about the installation and use of Novell's IntranetWare client and Microsoft's NetWare client later in this chapter.
NOTE: Install Novell's NetWare client where possible. You will find it to be a full-featured client software that is tightly integrated with the Windows 98 desktop and functions seamlessly.
Windows 98 comes with several clients, but you can also add third-party clients (such as Novell's IntranetWare Client for Windows 98, discussed earlier in this chapter). Assuming you have already installed and configured the network adapter, the next two sections will show you how to install Microsoft's NetWare client and Novell's NetWare client.
The Microsoft Client for NetWare Networks is included in your Windows 98 package. If you need to connect to a NetWare 4 network with NDS connections, you should also install the Service for NetWare Directory Services, which is also included with Windows 98. The Novell implementation of the 32-bit NetWare client for Windows 98 is called IntranetWare Client for Windows 98.
The steps for installing the Microsoft Client for NetWare Networks are very similar to those for the Client for Microsoft Networks. The only difference is that when you get to the Select Network Client dialog box, highlight Microsoft in the Manufacturers list; in the Network Clients list, highlight Client for NetWare Networks.
If you need to connect the Windows 98 workstation to NetWare 4 and use NDS connection, you need to install the Microsoft NetWare Client update to provide NDS support. The update is installed as a service rather than as a client. Here are the steps to follow:
As you will find out in this section, the installation procedure for Client 32 is slightly different and, in some respects, easier than the procedure for installing the Microsoft client.
WARNING: If Microsoft Client for NetWare Networks is already installed, Novell's installation program will remove it before installing the IntranetWare Client.
You can obtain the Novell client in two formats: one for floppy disk installation and one for server (or hard disk) installation. Because of the size of the uncompressed files (over 20 MB), using the server installation method is recommended. Alternatively, you can put the files on the local hard disk of your Windows 98 workstation and install from there. The following steps assume the software is located on your hard drive:
NOTE: If you have the latest IntranetWare Client CD-ROM, after you insert the CD-ROM into the CD-ROM drive of the Windows 98 workstation, a language selection screen is displayed. Select the desired language and product from the list, and proceed to step 4 below.
FIGURE 28.1 The components available under the Custom installation option.
Novell Distributed Print Services (NDPS). NDPS enables two-way communication in real time between your workstation and your network printer.
Novell NetWare/IP Protocol. This protocol sends and receives IPX packets in IP format. NetWare/IP enables networked applications that use only IPX to communicate over TCP/IP networks. It also provides a way for separate IPX networks to communicate across IP-based internetwork connections, such as the Internet.
Novell IP Gateway. This component enables WinSock applications to communicate with IP hosts through a Novell IP-IPX Gateway server. This enables all Internet traffic to use only one IP address on the Gateway server, significantly reducing the cost and time associated with maintaining individual workstation IP addresses.
Novell SNMP Agent. This software enables you to monitor, from an SNMP console such as ManageWise, remote connections to computers running Windows 98.
Host Resources MIB for the Novell Clients. This component is an implementation of the Host Resources Management Information Base (MIB) as defined by Request for Comment (RFC) 1514 and Novell's extensions to it. The HostMIB NLM uses the services provided by the SNMP agent. Management consoles, such as Novell's ManageWise console, can use the SNMP protocol to communicate with the HostMIB NLM to obtain information such as size of local drives and printers installed.
Network Management Responder for Windows 98. This component is an application service that returns general workstation configuration information beyond what is normally available through SNMP.
Novell Target Service Agent for Windows 98. The target service agent (TSA) allows automatic backup of selected local hard drives from a server.
Novell Remote Access Dialer. This component installs NWCAP, PhoneBook, and NWAdmin PhoneBook Snapins.
Reboot. Click this button to restart Windows 98 and log in using the new client.
Return to Windows. Click this button to shut down the installation program and return to the desktop.
Customize. Click this button to configure the client.
Note that the IntranetWare Client installation program also makes the following changes to your system:
To customize the Novell IntranetWare Client, you have three ways to get started:
Whichever method you use, you see the Novell IntranetWare Client Properties dialog box, shown in Figure 28.2.
FIGURE 28.2 This tab configures options for the general IntranetWare Client user login information.
To configure your login, use the following tabs:
FIGURE 28.3 The options in this tab cover the login connection and login script information.
NOTE: The login options you can configure here correspond to keys in the Registry database. The path is HKEY_LOCAL_ MACHINE | Network | Novell | System Config | Network Provider | Graphical Login. Below are the key names with their default values (0=OFF, 1=ON):Name Value
Connection tab 0
Script tab 0
Variables tab 0
FIGURE 28.4 This tab defines the printer capture information.
The configuration for the Microsoft NetWare client is much simpler than that of Novell's because you have only two tabs to work through, as shown in Figure 28.5. From this properties sheet, you configure options such as the Preferred server, the First network drive, whether you want the login script to be executed during login, and so on.
FIGURE 28.5 The properties sheet for the Microsoft NetWare Client.
With networking installed and enabled on a Windows 98 workstation, every time you restart the machine you will be prompted with a login dialog box. Here's how it works. Upon startup, Windows 98 checks to see whether a network client is loaded. In the case of Client 32, the workstation will have an initial attachment to a NetWare server at this point. Windows 98 then calls the corresponding network provider (NetWare's in this example) to perform its login function, which in this case is supplied by the GUI Login utility.
After you log in to NetWare, Windows 98 requires you to log in to the workstation itself. NetWare Client 32 caches the login information so that, if the user's Windows 98 name and password are the same as those for the network, the Windows 98 login will not be invoked. (If no network client is detected during the Windows 98 startup, only the Windows 98 login is displayed to log the user into the workstation.)
A Windows 98 workstation can support concurrent connection to a number of different network operating systems (such as NetWare and Microsoft Network). Each of these network operating systems (NOSs) has a different login dialog box. However, with Windows 98's password caching capability previously described, it is possible to have a single login for all your networks, including Windows 98 itself. The first time you start Windows 98, however, you will have to deal with the different login dialog boxes. The key to a single login is to assign the same password for each login.
TIP: The Windows 98 Password utility (available on the Control Panel) can be used to synchronize all your networking passwords.
Using the Microsoft Client for NetWare
When using the Microsoft NetWare client, the login prompt looks somewhat similar to the standard Windows 98 login. If you are logging in to a NetWare 3 server or to a NetWare 4 network using a bindery connection, simply enter your username and password. If you are logging in to a NetWare 4 network using an NDS connection, enter your username using the full NDS name (such as .peter.toronto.dreamlan) if a name context is not set.
When using Novell's Client 32, the GUI login prompt will look similar to the one shown in Figure 28.6. Depending on the configuration specified on the Client 32 properties sheets, as described earlier, you might have only the Login tab or up to four tabs from which you can enter login information.
FIGURE 28.6 The Novell client GUI login dialog box.
NOTE: The GUI Login utility, LOGINW95.EXE, can only be run from the workstation's local hard drive. It cannot be executed from a copy placed on a server.
Use the Login tab to enter your username and password. The Connection tab is where you can choose and specify the following (see Figure 28.7):
FIGURE 28.7 Novell GUI Login utility's Connection tab.
If you have already configured the necessary information through the Client 32 properties sheets, you will not need to access any of the other tabs (such as Connection or Login Script) while logging in, unless you wish to change the defaults.
TIP: To ensure that your users cannot bypass the login scripts, where you might have put some conditional checks, turn off the display of the Login Script tab using the Client 32 Properties sheets.
When you log in to a NetWare server or network using either the Microsoft client or the Novell client, the various login scripts are executed. With the Novell client, if the option is selected, you can see the result of the login script execution. This is very useful in troubleshooting login script problems.
For the most part, the Microsoft client processes the login script in the same manner as the Novell client. However, there are some enhancements in the Novell GUI Login that are not available in the Microsoft client. The following are some tips and tricks to be aware of when using the GUI Login utility with NetWare Client 32 for Windows 98:
NOTE: The GUI Login for NetWare Client 32 for DOS/Windows also has the capability to process the @ command. However, the LOGIN.EXE command line utility ignores the @ command in the login script.
TREE <treename>/<.full.NDS.name>
For example,
TREE WEBSITE_FOR_NETWARE/.webmaster.dreamlan
If you want a different sound to be heard, you can specify another .WAV file by specifying
the filename in the login script as follows:
FIRE FILENAME.WAV
or
FIRE PHASERS FILENAME.WAV
One word of caution about multitasking while logging in: Although Windows 98 allows you to perform other tasks while Client 32 processes a login script, you should avoid doing so because it can cause errors. For example, opening Network Neighborhood while Client 32 is processing a login script might cause the Multiple Provider Router (MPR.EXE) to produce a general protection fault (GPF).
Windows 98 allows users to access any number of different networks simultaneously. Each of these networks must have a provider--a piece of software that provides network services through the Windows 98 interface. The provider is not a standalone application with its own interface; rather, it is integrated into the Windows 98 desktop environment. When users access a Windows 98 utility such as My Computer, Explorer, or Network Neighborhood, requests for network services are routed through the Multiple Provider Router to the appropriate network provider.
The NetWare Provider establishes connections to NetWare servers, volumes, directories, and files, as well as to print queues, either through unified naming convention (UNC) paths or through map and capture functions. The following subsections begin with an overview of how to browse network resources using the three Windows 98 utilities (My Computer, Explorer, and Network Neighborhood) and the services of the NetWare Provider. Then the focus expands into the various NetWare tasks you can perform through Explorer and Network Neighborhood. Our discussion of network printing occurs in its own section later in this chapter.
In Windows 98, you can browse the resources available to your computer through three different utilities:
When you start up My Computer, it displays all of the physical devices available on your computer (floppy drives, local hard drives, network drives, and so on). It also displays the Control Panel folder and a folder for printers installed on your computer. To view lower levels within a network drive, simply double-click on the drive's icon. For example, double-clicking on the F: icon shows the contents of the drive.
You can drill down a directory tree simply by double-clicking on the appropriate icon; double-clicking on a folder shows its contents, double-clicking on a data file opens it, and double-clicking on an application runs it.
The print queue icons behave slightly differently. Double-clicking on a print queue icon shows the print queue if that printer has been previously installed on the workstation. Otherwise, Windows 98 asks whether you would like to set up the selected print queue. This is discussed further in a later section.
When you launch Explorer by selecting Start | Programs | Windows Explorer, you will see a window displaying all folders on the local and network drives. The list on the right displays the contents of the folder currently selected at the left.
Explorer operates similarly to File Manager in Windows 3.x. To browse through the directory hierarchy, double-click on a folder or drive icon. Browsing by exploring simplifies copying and moving files.
Another way to access the Explorer is to right-click on any folder or object and select the Explore option from the resulting menu. Figure 28.8 shows the result of right-clicking on a NetWare volume icon and selecting Explore.
FIGURE 28.8 Exploring a NetWare volume.
Network Neighborhood allows you to browse not only through your own computer but also through other computers in your workgroup and through your entire network. When you start up Network Neighborhood, it shows icons for the following:
To browse all network resources, click on the Entire Network icon. The network resources are categorized under Novell Directory Services and IntranetWare Servers folders, as shown in Figure 28.9.
FIGURE 28.9 Network resources as seen in Network Neighborhood.
The Novell Directory Services folder is designed for users on a NetWare 4 network, whereas the IntranetWare Servers folder is designed for NetWare 3.x and earlier. NetWare 4 users can choose either folder, depending on how they prefer to view network resources.
When you double-click on the Novell Directory Services folder, you see a list of NDS trees that exist on your network. To log into a particular tree, either double-click on the tree or right-click on the tree and select the Login to NDS Tree option. You will be prompted for a username and password. After you are authenticated, you can "walk" the tree by selecting containers one level at a time. The Provider displays the NDS Volume and Print Queue objects that exist in the current container, as shown in Figure 28.10.
FIGURE 28.10 NDS objects as seen by Network Neighborhood.
Alternatively, from Entire Network you can choose the IntranetWare Servers folder, which allows you to browse through servers, volumes, directories, files, and print queues. When you double-click on the IntranetWare Servers folder, you see a list of servers available on the network. You can view the resources on a given server by drilling down on the server icon.
You can perform a number of NetWare-related tasks from within Explorer. To access this functionality, first highlight a network drive and then select the Tools option from the menu bar at the top of the window. Three options are available:
TIP: You can also access these and additional Client 32-specific options by right-clicking a network volume.
You can also view volume information from within Explorer. These tasks are explained in the following sections, starting with mapping and unmapping drives.
Mapping and Unmapping a Network Drive
You can map a network drive in one of three ways. From the Tools menu, select the Map network drive option. The next available drive letter is displayed in the Drive entry box. You can select another drive letter by clicking on the pull-down arrow button to the right of the Drive entry box. If you want the drive to be reconnected at login, activate the Reconnect at login check box. Enter the path of the directory to which you wish to map in the Path entry box, using the UNC syntax. Click OK and the mapped drive shows up as a networked drive icon.
The second method to map a drive is to first locate the directory you want to map. Highlight this directory and then select the Map network drive option from the Tools menu. The next available drive letter is displayed in the Drive entry box. You can select another drive letter by clicking on the pull-down arrow button to the right of the Drive entry box. If you want the drive to be reconnected at login, activate the Reconnect at login check box. Click OK and the mapped drive shows up as a networked drive icon.
NOTE: All network drives connected using the above method are automatically "map rooted."
You can also map the drives using the Novell NetWare Provider extension. As before, first locate the directory you want to map. Highlight this directory and then right-click to bring up a menu similar to the one shown in Figure 28.11. In this menu, an N to the left of the option indicates it is an extension.
TIP: Depending on the color and resolution setting, you might or might not see the N easily.
Using the NetWare Provider extension, you have the capability to map network drives (with or without them being map rooted, as shown in Figure 28.12) as well as mapping search drives. The search drive mapping capability is not available with the Microsoft client.
FIGURE 28.11 NetWare Provider extensions are shown with an N on the left of the option.
FIGURE 28.12 You have the option of mapping a NetWare network drive as "map rooted."
You can undo an existing drive mapping in one of two ways. The first method is to select the Disconnect network drive option from the Tools menu. A window listing the currently mapped drives appears. Highlight the drive you want to unmap and click on OK.
The other method of unmapping a network drive is to highlight the drive letter you wish to disconnect, right-click to bring up the menu, and select the Disconnect option.
You can easily search for a file (or group of files) on the network by selecting the Find option from the Tools menu and then selecting Files or Folders. A dialog box similar to the one shown in Figure 28.13 is displayed.
NOTE: You can also use Start | Find | Files or Folders to locate a file.
FIGURE 28.13 The Find All Files dialog box.
Type the name of the file you want to locate in the Named entry box; you can use wildcard characters (* and ?) in the name. Click on the pull-down arrow button to select from a list of name options. Enter the text you wish to search for (if any) in the Containing text entry box. Specify the path you want to search in the Look in box. Clicking on the pull-down arrow button displays a list of drives (network and local) you can choose from. Check the Include subfolders box if you want to search in all subdirectories of this directory (it is checked by default).
Under the Date tab, you can specify date ranges for the search. For example, you can look only at files that were modified between September 1, 1997, and March 1, 1998. You can also specify a search for files that haven't been modified for a certain period of time. The Advanced tab lets you refine the search parameters even further, specifying that you want to search by file type or for files of a certain size.
You can easily look up information about a particular NetWare volume. Right-click on the drive icon for the volume and select Properties from the resulting menu. You will see a window of information.
There are a total of four tabs available; the default is the General tab. The IntranetWare Volume Information tab displays the volume number, the total and available space in KB, and the total and available number of directory entries. The IntranetWare Folder and IntranetWare Rights tabs can be used to assign NetWare attributes (such as Read-only) or trustee assignments.
You can perform numerous NetWare tasks from within Network Neighborhood instead of using NetWare utilities, such as NetWare Administrator or FILER. For example, you can view connection information, log in and out of servers, view properties of servers and trees, send messages, map network drives, and view information about volumes, directories, and files. You can also manage file system trustee rights and attributes using a more intuitive graphical interface than the command-line utilities previously used (RIGHTS, GRANT, REVOKE, and so on). This section shows some of the many tasks you can perform in Network Neighborhood with the services of the NetWare Provider.
The NetWare Provider allows you to change your default NDS tree and server at any time during your current session. To do this, right-click on Network Neighborhood and select IntranetWare Connections. You will see a screen similar to Figure 28.14.
FIGURE 28.14 Current connection information.
An asterisk (*) precedes the names of your default NDS tree and server. To change the current default, highlight the one you want and click on the Set Current button. Note that changing the default tree or server affects Network Neighborhood's entire view of the NetWare servers. For example, when you change to a different default NDS tree, Network Neighborhood will display only objects that exist in that tree.
Newer versions of the NetWare Provider allow you to send broadcast messages to users on the network. To do this, click on Network Neighborhood, right-click on the server that the users are connected to, and then choose the Send message option. Type the message you want to send in the Send message to the selected user(s) entry box. Select the individual users or groups to receive the message and click on Send.
You can only send messages to users who are currently connected to the server. The groups shown are those listed in the server's bindery. The maximum length of your message is 250 characters, including the "From: <Username>(##)" string placed at the beginning of the message. <Username> is your NetWare user account name and ## is your connection number.
A number of tasks related to the NDS tree, such as changing the NDS name context, can be easily performed from within Network Neighborhood. The menu options can be accessed from the list of NDS trees you see after you start Network Neighborhood and choose Entire Network and the Novell Directory Services folder. Highlight an NDS tree and right-click on the mouse. A menu of options appears.
For example, to change your NDS context in Network Neighborhood, right-click on an NDS tree and select the Change context option from the resulting menu. The resulting window shows your current context and allows you to change to a different default context. Type the new context in the entry box and click on the Change button.
Also, you can easily find out information pertaining to your connection using the WhoAmI option: Selecting the WhoAmI option after right-clicking on an NDS tree will display information concerning your username, context, and NDS tree name.
NetWare Server-Related Tasks
Logging In to and Out of a Server
To log in to a NetWare server in Network Neighborhood, double-click on the server icon or highlight the server and right-click with the mouse. Select the Authenticate option for an NDS login or the Login to server option for a Bindery-based login. The GUI login utility will be launched, asking you to enter your username and password.
To log out from a server, highlight the server you are logged into and right-click the mouse. Select Logout from the resulting menu.
WARNING: You will not be prompted to confirm whether you are sure you want to log out from the highlighted server.
Viewing Server Properties
You can look up information about a NetWare server (you do not need to be logged in to it first), such as number of licensed connections. To see the properties of a server, right-click on the server icon and choose Properties from the pull-down menu.
Viewing Volume Information and Properties
To view a server's resources (volumes and print queues), simply double-click on the server's icon. If the server is a bindery-based server and you are not already attached, the Provider will first try your Windows 98 username and password to log in. If that fails, you will be prompted for your NetWare username and password.
NOTE: As with servers and other objects, right-clicking on a volume displays a menu of options.
You can easily look up information about a particular NetWare volume. Right-click on the volume icon and select Properties from the resulting menu.
Although the volume information dialog boxes are similar between Explorer and Network Neighborhood, Explorer's has four tabs and Network Neighborhood's has only three tabs available. The default is the IntranetWare Volume Information tab; there is no General tab. The IntranetWare Volume Information tab displays the volume number, the total and available space in KB, and the total and available number of directory entries. The IntranetWare Folder and IntranetWare Rights tabs can be used to assign NetWare attributes (such as read-only) or trustee assignments.
Mapping a Network Drive
To map a drive to a volume, right-click on the volume icon and select Map Network Drive. This time the path is filled in for you, so you simply need to specify the drive you want to map it to.
To have this mapping automatically reestablished when you start Windows 98 and log into NetWare, check the Reconnect at login box. Click OK when finished.
NetWare Client 32 for Windows 98 supports "deviceless" printing. That means it is no longer necessary to associate an LPT port with a specific printer and use a print capture to redirect the output to a network printer. Instead, GUI applications send print data directly to a Windows 98 printer device (such as a NetWare print queue), which points to a network printer. When you set up a printer, Windows 98 writes all the printer configuration information to the Registry. To use the printer, simply click the printer's icon.
To provide backwards printing support for MS-DOS and Windows 3.x applications, Windows 98 still allows you to set up an LPT port capture and redirect output to the network printer specified in the capture. If you do a capture at an MS-DOS prompt, the capture exists under the GUI; if you do a capture in the GUI world, it exists for MS-DOS boxes. However, any flags you set up under a DOS capture cannot be translated into the GUI world. There's no way to associate a Windows 98 printer device with an LPT port.
Client 32 for Windows 98 also supports point-and-print to simplify printer setup for users. Point-and-print allows you to store the printer driver files for a network printer in a publicly-accessible network directory (such as SYS:PUBLIC directory on the NetWare server). When users want to use the printer, they can install it quickly without having to know the printer manufacturer/model and the location of the printer driver.
This section will cover the following topics:
Similar to installing a local printer for your Windows 98 workstation, you can also use the Add Printer Wizard to install a network printer. Use the following steps:
NOTE: The installed network printer will appear in the Printers folder along with any local printers you might have. The only difference between the two types of printers is that a cable appears underneath a network printer's icon.
There are three ways in which you can print to a network printer--from within an application, or using a printer shortcut:
FIGURE 28.15 A network printer does not show an LPT port.
Using Network Neighborhood. Highlight a shared printer and select File | Capture Printer Port, or right-click the printer and select Capture Printer Port from the pop-up menu.
Using Explorer. Highlight a shared printer and select File | Capture Printer Port, or right-click on the printer and select Capture Printer Port from the pop-up menu.
Using the printer icon. From the properties sheet of a shared printer, display the Details tab, and click the Capture Printer Port button.
Using CAPTURE.EXE. Use the Novell-supplied CAPTURE utility to redirect a printer port to a network print queue or NDS printer object.
NOTE: To create a shortcut to a printer, simply drag the appropriate printer icon from the Printers folder to the desktop.
It is easy to modify the settings of a network printer after it is installed. To configure a network printer, right-click on the printer's icon in the Printers folder; the resulting menu lists several options for the printer:
TIP: If you want to set default printer settings for all future print captures, use Control Panel | Novell NetWare Client 32 | Properties | Default Capture tab. The settings entered on that tab page will affect existing captures after you restart your computer. They do not affect captures made from a login script or from the command line.
Use the following steps to set up point-and-print for a network printer and store the printer information on a NetWare 3.x or 4.x server:
To access this print queue, you now need to add the queue to the Printers folder by using the Add Printer Wizard. Follow these steps:
Windows 98 automatically copies the printer driver files (.RV, .DLL, .HP, and so on) from the server to the Windows 98 SYSTEM directory.
The Add Printer Wizard is only one of the few methods available for installing a printer. The point-and-print feature also lets you install a remote printer by using the following techniques:
In each case, a scaled-down version of the Add Printer Wizard appears. Follow the prompts to install the printer.
© Copyright, Macmillan Computer Publishing. All rights reserved.
){kind=link}
){kind=link}
){kind=link}
){kind=link}
){kind=link}
){kind=link}
){kind=link}
){kind=link}
){kind=link}
){kind=link}
){kind=link}
){kind=link}
){kind=link}
){kind=link}
){kind=link}